CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

common-dast-tooling

Standardize dynamic application security testing for backend APIs, frontend web apps, and mobile clients. Covers ZAP, Nuclei, Nikto, sqlmap, ffuf, browser automation, mobile proxy interception, and AI-driven curl probes. Use when advising on or running dynamic security scans on local/staging environments.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/common/common-dast-tooling/SKILL.md

The canonical home for this skill is common-dast-tooling in HoangNguyen0403/agent-skills-standard

SKILL.md
Quality
Evals
Security

Quality

Content

72%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.

A well-organized tooling standard with excellent progressive disclosure (commands properly split into a verified one-level reference file) and mostly actionable, concrete guidance. Its weakest area is workflow clarity: the skill catalogs tools and rules but never sequences the scanning process or embeds the authorization gate into an ordered workflow with validation checkpoints.

Suggestions

Add an ordered scan workflow (e.g., 1. Confirm authorization and target scope, 2. Set max-depth/max-duration bounds, 3. Run passive then active scans, 4. Triage findings against the Scoring Impact table) with the DAST-AUTH-01 gate as an explicit first validation step.

Trim tool one-liners that restate common knowledge (e.g., what Nikto or Nuclei do) and replace the bare '## **Priority: P1 (HIGH)**' heading with a one-line purpose statement.

Include one or two inline example commands for the highest-frequency case (e.g., a nuclei or ffuf invocation) so the body is immediately executable without opening the reference, while keeping the bulk in references/implementation.md.

DimensionReasoningScore

Conciseness

Sections are tight and table-driven, but tool one-liners ('Nikto: Server configuration audit (version disclosure, headers)') restate what Claude already knows and the '## **Priority: P1 (HIGH)**' heading is padding — minor over-explanation that could be trimmed, matching anchor 4 rather than the lean 5.

4 / 5

Actionability

Gives concrete specifics — probe paths ('/metrics', '/health', '.git', '/.env'), headers ('X-Forwarded-For'), and bounds rules ('max-depth', 'max-duration') — but no inline executable commands; all commands live in references/implementation.md, leaving minor gaps versus the fully copy-paste 5 anchor.

4 / 5

Workflow Clarity

No sequenced scan workflow (authorize → scope → scan → triage → report); the '[DAST-AUTH-01]' gate and BLOCKED rule are the only checkpoint and are presented as rules rather than ordered steps with validation loops, and the batch/destructive cap limits workflow clarity to 3 for risky active scanning without an explicit validation cycle.

3 / 5

Progressive Disclosure

The body is a well-sectioned overview with all executable commands split into the real, one-level-deep references/implementation.md, clearly signaled in three places ('See [implementation guide](references/implementation.md)') with no nested references — matching the clear-overview 5 anchor against the actual bundle structure.

5 / 5

Total

16

/

20

Passed

Description

83%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.

A strong description: it names a specific domain, enumerates concrete tools and capabilities, and includes an explicit, scoped 'Use when' trigger clause. Main gaps are a slightly abstract lead verb ('Standardize'), missing common synonyms like 'penetration testing', and unstated boundaries against adjacent security skills.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ('mobile proxy interception', 'AI-driven curl probes', 'browser automation') and named tools (ZAP, Nuclei, Nikto, sqlmap, ffuf), but the leading verb 'Standardize' is abstract and per-tool actions are not enumerated — matching 'several specific actions; minor gaps' rather than the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers both: what ('Standardize dynamic application security testing... Covers ZAP, Nuclei...') and when ('Use when advising on or running dynamic security scans on local/staging environments'), with a concrete, scoped trigger clause matching the 5 anchor.

5 / 5

Trigger Term Quality

Includes natural terms users would say — tool names (ZAP, Nuclei, sqlmap), 'dynamic security scans' — but misses common synonyms like 'penetration testing', 'vulnerability scanning', or 'Burp', so coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Dynamic application security testing' carves a clear niche with distinct tool triggers, but broad terms like 'pentest'/'security testing' overlap with general security skills and the static/dynamic boundary is not stated — mostly distinct with minor overlap risk.

4 / 5

Total

17

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

.agents/skills/common/common-dast-tooling/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.