CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

web-pentest

Authorized web pentest: recon, proof-based exploits, report.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/security/web-pentest/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong operational skill body: a clearly phased workflow with genuine validation checkpoints, feedback loops, and safety gates, expressed in concrete commands rather than abstraction. The main defects are packaging-level — three referenced template files do not exist in the bundle, and the delegation tool syntax is assumed rather than shown.

Suggestions

Ship the missing templates/ files (authorization.md, pentest-report.md, exploitation-queue.json) or remove the references and inline their schemas — Phases 0, 3, and 5 currently point at files that do not exist in the bundle.

Include one concrete delegate_task invocation example (arguments, expected subagent output) so the Phase 3 delegation is copy-paste ready.

Trim meta-commentary such as the "Adapted from Shannon's pipeline" attribution and tool-rationale asides into a single short credits/notes line to tighten token budget.

DimensionReasoningScore

Conciseness

The body is dense and operational — it assumes Claude's competence (never defines SQLi, XSS, or nmap) and every section carries procedure rather than background. Minor trim opportunities exist (the "Adapted from Shannon's pipeline" attribution line and rationale sentences like the `-T3` IDS/IPS justification), keeping it below anchor 5's "every token earns its place".

4 / 5

Actionability

It provides concrete executable commands ("nmap -sT -T3 --top-ports 100 -oN evidence/nmap.txt $TARGET", the whatweb/curl lines, the browser_exec JS snippet) and specific witness payloads ("' AND 1=1--", "<svg/onload=console.log(\"HERMES-PENTEST-XSS\")>") with exact output paths. Not anchor 5 because delegate_task/browser_exec call syntax is assumed rather than shown, and three referenced templates/ files are absent from the bundle, leaving the Phase 0/3/5 artifacts under-specified.

4 / 5

Workflow Clarity

Phases 0-5 are explicitly sequenced with validation checkpoints throughout: the authorization gate ("Wait for explicit `authorized` response"), pre-send checks, witness-payload verification, and bypass exhaustion before any false-positive verdict. Feedback loops for error recovery (STOP on off-scope redirects, back off on 503/429 storms) and stop-condition checklists are present, and destructive operations have approval gates, so the destructive/batch cap at 3 does not apply.

5 / 5

Progressive Disclosure

The overview body stays lean and pushes per-class detail to four real one-level-deep references (scope-enforcement.md, vuln-taxonomy.md, exploitation-techniques.md, bypass-techniques.md) plus scripts/recon-scan.sh, each clearly mapped in the "Further Reading" section. Not anchor 5 because three referenced paths (templates/authorization.md, templates/pentest-report.md, templates/exploitation-queue.json) are missing from the bundle entirely, leaving dangling navigation — though their content is partially inlined, so the damage is bounded.

4 / 5

Total

17

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is admirably concise and names a distinctive niche, but it is too terse to do full triggering work: it lacks any "when to use" guidance and omits common natural phrasings like "penetration test" or "find vulnerabilities". It functions, but a slightly expanded version would materially improve activation reliability.

Suggestions

Add a "Use when..." clause, e.g. "Use when the user asks to pentest, penetration-test, or security-test a web application they own or are authorized to test."

Include natural trigger synonyms in the description itself: "penetration testing", "vulnerability assessment", "find vulnerabilities", "web app security".

Expand the action labels into concrete verb phrases, e.g. "Runs scoped recon, verifies each finding with witness payloads, and produces a proof-based report."

DimensionReasoningScore

Specificity

"Authorized web pentest: recon, proof-based exploits, report" names the domain plus three concrete but heavily compressed action labels ("recon", "proof-based exploits", "report"). It does not reach anchor 4 because each action is a one-word label rather than an elaborated action and coverage is thin relative to the skill's six phases, but it exceeds anchor 2 by listing multiple concrete actions beyond just naming the domain.

3 / 5

Completeness

It has a clear "what" ("recon, proof-based exploits, report") but no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Anchor 4 is ruled out because it requires both a "what" and a "when".

3 / 5

Trigger Term Quality

The description contains some relevant natural keywords — "web pentest" and "recon" are phrases users actually say — but misses common variations like "penetration test", "vulnerability", "security test", and "web app". Not anchor 4 because keyword coverage is too thin, and not anchor 2 because "pentest" is a genuine domain-natural term rather than generic language.

3 / 5

Distinctiveness Conflict Risk

"Authorized web pentest" carves a clear niche with minimal overlap against typical skill inventories, and "proof-based exploits" further distinguishes it. Not anchor 5 because the description itself carries no explicit trigger phrases, and "recon... report" brushes against adjacent recon/security-testing skills.

4 / 5

Total

13

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/security/web-pentest/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.