CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/dast-scan-cadence-author

Designs an end-to-end DAST cadence for teams adopting dynamic scanning: ZAP passive baseline (PR-blocking) then ZAP full active scan (nightly on staging) then optional Burp Pro deep scan (per-release). Handles the baseline-finding ratchet for legacy apps so pre-existing findings do not immediately block PRs, plus per-tool per-run deduplication and CI workflow YAML. Use when the team is setting up DAST from scratch or restructuring scan cadence, not when tools are already running and you need to merge their output (cross-tool aggregation of existing independent runs is a separate concern).

70

Quality

88%

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

Overview
Quality
Evals
Security
Files

Quality

Content

78%

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

A well-organized, actionable DAST cadence playbook with clean progressive disclosure into a real CI-workflows reference. The main weaknesses are a stubbed aggregation step and slightly weaker validation feedback loops relative to the rubric's ideal.

Suggestions

Replace the Step 7 aggregation stub with executable code or an explicit pointer to a reference file that contains the real aggregation logic.

Add an explicit validate->fix->retry feedback loop (e.g., re-run baseline diff after a suppression/baseline change and re-check coverage) to strengthen workflow clarity.

Trim motivational framing sentences (e.g., 'if they all block PRs, the team disables DAST') that restate consequences Claude can already infer.

DimensionReasoningScore

Conciseness

Mostly lean and table/step-driven with no 'what is DAST' preamble, but a few motivation sentences ('if they all block PRs, the team disables DAST') pad slightly beyond what Claude needs.

2.5 / 3

Actionability

Provides executable pr-gate.py, dedupe_findings, jq coverage commands, and real workflow YAML in the reference; however Step 7 aggregation is a stub ('curl ...' and a '# Aggregate all three + emit unified verdict' comment) rather than executable code.

2.5 / 3

Workflow Clarity

Steps 1-9 are clearly sequenced with cross-references and an end-to-end checklist (Step 9), but explicit validate->fix->retry feedback loops are lighter than the coverage threshold and triage gating suggest.

2.5 / 3

Progressive Disclosure

Well-signaled one-level-deep reference ('Full workflow YAML for all three: references/ci-workflows.md') to a real bundle file, with bulky YAML appropriately split out and clearly organized sections.

3 / 3

Total

10.5

/

12

Passed

Description

92%

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, specific description that answers both what and when with an explicit (and negative) trigger and a clear boundary against a sibling aggregation skill. The only soft spot is trigger-term breadth, which leans on domain jargon.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Designs an end-to-end DAST cadence', 'ZAP passive baseline (PR-blocking)', 'baseline-finding ratchet', 'per-tool per-run deduplication and CI workflow YAML' — going well beyond naming a domain.

3 / 3

Completeness

Explicitly answers what ('Designs an end-to-end DAST cadence...') and when ('Use when the team is setting up DAST from scratch or restructuring scan cadence, not when...'), including a negative-trigger disambiguator.

3 / 3

Trigger Term Quality

Natural for the target audience ('setting up DAST from scratch', 'restructuring scan cadence', 'dynamic scanning') but leans on domain-internal terms and omits broader phrasings like 'vulnerability scanning' that a user might also say.

2.5 / 3

Distinctiveness Conflict Risk

Carves out a distinct build-a-cadence niche and explicitly excludes the aggregation case ('cross-tool aggregation of existing independent runs is a separate concern'), making conflict with sibling skills unlikely.

3 / 3

Total

11.5

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents