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 ./.github/skills/common/common-dast-tooling/SKILL.md
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, efficient overview that appropriately pushes executable commands to a single, clearly signaled reference file. The main gap is process rather than content: it catalogs tools and rules by platform but never sequences them into a scan workflow with finding-verification checkpoints, which matters for risky batch scanning.

Suggestions

Add a sequenced workflow (authorize → passive recon → active scan → verify findings → apply the Scoring Impact table) with an explicit verification step, e.g. manually confirming a suspected SQLi with a controlled payload before scoring it, so the batch/risky nature of scanning has a feedback loop.

Consolidate duplicated rules: the ffuf-vs-fuzz-testing distinction (section 1 and Anti-Patterns) and the self-authorization rule ([DAST-AUTH-01] and Anti-Patterns) each appear twice — state each once and cross-reference it.

Inline one minimal runnable example (e.g. `nuclei -u http://localhost:3000 -severity critical,high`) so the most common case is executable without opening the reference.

DimensionReasoningScore

Conciseness

Mostly lean tool bullets ("**Nuclei**: Fast, template-based CVE/misconfiguration scanning.") that assume Claude's tool knowledge and defer setup to the reference, but there is minor redundancy: the ffuf/fuzz-testing distinction appears in both section 1 ("does not replace structured robustness/fuzz testing") and Anti-Patterns, and "No self-authorization" restates the [DAST-AUTH-01] rule.

4 / 5

Actionability

Concrete, specific guidance (probe "/metrics", "/health", ".git", "/.env", "/api-docs"; "grpcurl for service enumeration"; JWT expiry/claim manipulation) with complete commands one level deep in references/implementation.md; the gaps are minor — no runnable example is inline in the body and there is no authenticated-scan example at point of use.

4 / 5

Workflow Clarity

No sequenced scan workflow exists — sections are organized by platform rather than process (authorize → recon → scan → verify → report), and there is no finding-verification step before applying the Scoring Impact table; the authorization gate ("status: BLOCKED") is the only explicit checkpoint. Active scanning is a batch/risky operation, so the missing validation loop caps this dimension at 3 despite the otherwise solid gating rules.

3 / 5

Progressive Disclosure

A clear overview with well-signaled one-level-deep references: "See [implementation guide](references/implementation.md) for setup commands" appears at point of need, a consolidated References section lists it again, the referenced file actually exists in the bundle and carries the command detail, and nothing in the bundle nests further.

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 with explicit what and when clauses, specific named tools, and a clear DAST niche. The weaknesses are minor: a few missing natural synonyms ("DAST", "pentest", "vulnerability scan") and slight overlap risk with fuzz-testing and browser-automation skills.

DimensionReasoningScore

Specificity

"Covers ZAP, Nuclei, Nikto, sqlmap, ffuf, browser automation, mobile proxy interception, and AI-driven curl probes" names concrete tools and capability areas across backend, frontend, and mobile, but the lead verb "Standardize dynamic application security testing" is abstract and downstream capabilities (finding remediation, scoring) go unmentioned — several specific items with minor gaps rather than comprehensive coverage.

4 / 5

Completeness

It explicitly answers both what ("Standardize dynamic application security testing for backend APIs, frontend web apps, and mobile clients. Covers ZAP, Nuclei...") and when ("Use when advising on or running dynamic security scans on local/staging environments") with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Tool names (ZAP, Nuclei, sqlmap, ffuf) are terms users naturally say when they need this skill, and "advising on or running dynamic security scans" adds a natural phrase; however, common synonyms like "DAST", "pentest", and "vulnerability scan" are absent from the description itself, so coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The named tools and the dynamic-scanning niche make it mostly distinct, but "ffuf" overlaps with the closely related API fuzz-testing skill (which the body itself has to disambiguate) and "browser automation" is generic enough to collide with general browser-testing skills — minor overlap risk rather than minimal.

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

.github/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.