CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/zap-baseline

Configures and runs OWASP ZAP baseline scanning: `zap-baseline.py` Docker-packaged spider + passive scan suitable for CI gating; supports `-t target_url` + `-r html_report` + `-c config_file` rule customization (INFO/IGNORE/FAIL warnings) and Ajax spider via `-j` for JS-heavy SPAs; `zap-full-scan.py` active companion for staging. Covers authenticated scans end to end as a reference - ZAP Context, auth methods (form/JSON/script/browser), session management, verification strategy, OAuth/bearer injection, context XML export for `-n` - plus DAST cadence planning (PR-blocking passive baseline, nightly ZAP full + nuclei active layer, baseline-finding ratchet for legacy apps). Use when the user runs OWASP ZAP for pre-prod web app DAST, needs coverage of routes behind a login wall, or is designing a team's DAST rollout cadence.

73

Quality

92%

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

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

An actionable, well-sequenced skill body with strong validation checkpoints and good file structure, lightly held back by mild verbosity and a second level of reference nesting off auth.md.

Suggestions

Tighten the Overview blockquote and Limitations prose to drop redundant explanation Claude already knows about passive scanning.

Flatten auth.md's sub-reference chain (script-based-auth, oauth-bearer-injection, verification-strategy) into a single consolidated reference file or index to keep references one level deep.

DimensionReasoningScore

Conciseness

Dense, command/table-driven body that assumes DAST competence; minor over-explanation in the Overview blockquote and Limitations prose could be trimmed, keeping it just below the lean anchor.

4 / 5

Actionability

Copy-paste-ready docker commands, a complete flag table, CI workflow YAML, and a worked config TSV example cover the common cases fully.

5 / 5

Workflow Clarity

A clear Step 1-8 sequence with explicit validation emphasis (MANDATORY triage in Step 6, full-scan production-safety warnings, anti-patterns table) provides feedback loops and checkpoints throughout.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview pointing one level deep to real files (auth.md, cadence.md), but auth.md itself chains to three further sub-references (script-based-auth, oauth-bearer-injection, verification-strategy), introducing a second nesting level.

4 / 5

Total

18

/

20

Passed

Description

92%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 highly specific, well-triggered description that comprehensively states capabilities and explicit use-when conditions with minimal conflict risk. Only slightly deducted for trigger-term naturalness, as some phrasing is flag/technical-heavy rather than user-speech.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - spider + passive scan, `-t`/`-r`/`-c` flag customization with INFO/IGNORE/FAIL warnings, Ajax spider via `-j`, authenticated scans with context/auth methods, and DAST cadence planning - giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' ('Configures and runs OWASP ZAP baseline scanning...') and 'when' via a concrete 'Use when the user runs OWASP ZAP...' trigger clause.

5 / 5

Trigger Term Quality

Strong natural terms ('OWASP ZAP', 'baseline scanning', 'DAST', 'login wall', 'DAST rollout cadence') that users would say, though a few common variations/synonyms are absent and some phrasing leans technical.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (OWASP ZAP pre-prod DAST) with distinct triggers that would not collide with other skills.

5 / 5

Total

19

/

20

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