CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

building-vulnerability-scanning-workflow

Builds a structured vulnerability scanning workflow using tools like Nessus, Qualys, and OpenVAS to discover, prioritize, and track remediation of security vulnerabilities across infrastructure. Use when SOC teams need to establish recurring vulnerability assessment processes, integrate scan results with SIEM alerting, and build remediation tracking dashboards.

Quality

79%

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 ./skills/building-vulnerability-scanning-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body delivers concrete, tool-specific guidance across a well-sequenced six-step workflow, but it is undermined by three systematic issues: no validation in the batch ticketing and scan-processing steps, background-concept padding (Key Concepts, Tools & Systems), and a complete failure to reference the existing bundle — the fully implemented scripts/agent.py and references/api-reference.md are orphaned while their content is re-inlined. Fixing the bundle linkage alone would both improve navigation and cut the body's token cost.

Suggestions

Link the existing bundle files from the body — e.g., under Workflow add 'Full implementation: scripts/agent.py; API details: references/api-reference.md' — so the executable agent is discoverable, and trim the inline illustrative code that duplicates them.

Add validation checkpoints to the batch operations: dedup checks before creating ServiceNow tickets, error handling on the requests.post response, and a post-scan verification step (Step 5 mentions post-patch rescanning only as a scenario, not a workflow step).

Delete or drastically shrink the 'Key Concepts' and 'Tools & Systems' sections — CVSS, KEV, credentialed scans, and the scanner products are things Claude already knows — and remove the duplicated SKIP_TLS_VERIFY comment.

DimensionReasoningScore

Conciseness

The code blocks and SLA table earn their place, but the 'Key Concepts' table defines things Claude already knows (CVSS, Credentialed Scan, CISA KEV, EPSS) and the 'Tools & Systems' section adds promotional blurbs ('200,000+ plugin checks'); the duplicated 'Set SKIP_TLS_VERIFY=true...' comment appears twice. This is more than minor trimming, so it sits below the score-4 'efficient' anchor.

3 / 5

Actionability

Concrete, mostly executable guidance throughout — Nessus/Qualys API calls, CISA KEV fetch, Splunk SPL queries, ServiceNow ticket payloads — but the examples have gaps: undefined helpers (get_asset_criticality, asset_criticality_multiplier, cisa_kev_list) and use of os.environ without importing os, keeping them from copy-paste ready (score 5).

4 / 5

Workflow Clarity

The six steps are clearly sequenced (scope → prioritize → SLA → SIEM → dashboard → ticketing), but no validation checkpoints exist anywhere: the batch ServiceNow ticket loop in Step 6 creates tickets with no dedup check, error handling, or success verification, and scan exports are never validated. Per the batch-operations cap, this cannot score above 3 even though the sequence itself is clear.

3 / 5

Progressive Disclosure

The body itself is well-sectioned with clear step headers, but scored against the actual bundle: references/api-reference.md and scripts/agent.py (the complete executable implementation) are never referenced or linked from SKILL.md, so the bundle is undiscoverable and its content is duplicated inline as illustrative code. References are entirely un-signaled, which is worse than the score-4 'references mostly clear' anchor but the body structure keeps it above the score-2 'minimal structure' anchor.

3 / 5

Total

13

/

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 strong description: third-person voice, concrete lifecycle actions, named tools, and an explicit 'Use when' clause with three specific trigger scenarios. The only weakness is modest keyword synonym coverage (e.g., 'CVE', 'patch management') beyond the tool names.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the full lifecycle — 'discover, prioritize, and track remediation of security vulnerabilities' plus 'establish recurring vulnerability assessment processes, integrate scan results with SIEM alerting, and build remediation tracking dashboards' — which matches the comprehensive-coverage anchor; it is not score 4 because no meaningful action in the workflow is missing.

5 / 5

Completeness

It explicitly answers both 'what' ('Builds a structured vulnerability scanning workflow... to discover, prioritize, and track remediation') and 'when' with three concrete trigger scenarios ('Use when SOC teams need to establish recurring vulnerability assessment processes, integrate scan results with SIEM alerting, and build remediation tracking dashboards'), matching the top anchor; the 'when' clause is explicit and specific, so it is above the score-4 anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage including tool names users actually say ('Nessus, Qualys, and OpenVAS', 'SIEM', 'remediation tracking', 'vulnerability assessment'), but common variations like 'CVE', 'patch management', or 'vuln scanning' are absent, fitting the 'good coverage, a few natural terms missing' anchor rather than the comprehensive one.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — SOC recurring vulnerability management with named scanners (Nessus/Qualys/OpenVAS) and SIEM/dashboard integration — with minimal overlap risk against adjacent skills like penetration testing or incident response; it is not score 4 because the tool names and SOC-specific triggers make confusion with related skills unlikely.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

mukul975/Anthropic-Cybersecurity-Skills

Path

skills/building-vulnerability-scanning-workflow/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.