CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

security-audit

Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 expertly structured orchestration skill with exceptional workflow sequencing, validation gates, and operational safety rules, all written for a capable agent without padding. Its main weaknesses are sheer inline bulk — the write-isolation promotion procedure and budget-ordering rules belong in companion files — and reliance on referenced companion files that are not present in this bundle.

Suggestions

Move the 11-step scratch-to-artifacts promotion procedure out of SKILL.md into a single companion file and reference it from both hunter and verifier prompts, removing the duplicated fenced block.

Condense the cost-budget section to its gate rule and spend order summary, delegating the step-by-step reservation arithmetic to a planning reference file.

Ship the referenced companions (HUNTING.md, RECONNAISSANCE.md, VALIDATION-AND-REPORTING.md, ATTACK-CLASSES.md, report-schema.json, validators) with the skill, or inline minimal stand-ins, since the body's phase instructions depend on them.

DimensionReasoningScore

Conciseness

The body avoids explaining known concepts and every rule is non-obvious operational policy, but at ~470 lines it inlines substantial detail (the 11-step scratch-to-artifacts promotion procedure, multi-paragraph budget spend ordering) that could be tightened or delegated to companion files, and it explicitly duplicates the promotion block across two referenced files.

3 / 5

Actionability

Highly concrete instruction-only guidance — exact file names, JSON fields, regex for agent IDs, validator scripts, status strings, and two exact terminal states — with only minor gaps such as the abstract 'use equivalent platform capabilities' and hunting methodology delegated to companion files.

4 / 5

Workflow Clarity

Six phases are clearly numbered in order with explicit validation checkpoints (schema validation, validate-findings.cjs, validate-coverage-ledger.cjs, fresh-agent verification), feedback loops (coverage-critic waves, budget gates with exact incomplete_reason values), and a hard 'never stop mid-phase' terminal-state rule.

5 / 5

Progressive Disclosure

References are well-signaled and one level deep (RECONNAISSANCE.md, HUNTING.md, VALIDATION-AND-REPORTING.md, ATTACK-CLASSES.md, validators), but none of these companion files exist in the provided bundle, and a large amount of procedural detail remains inline in SKILL.md rather than split out.

4 / 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 that clearly states capabilities, targets, and explicit 'Use for' triggers, including a useful mode gate that keeps the heavy workflow from firing on casual security questions. Minor improvements would come from adding synonyms like 'security review' and making 'guidance' more concrete.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('vulnerability review', 'pen tests', 'security guidance') plus a comprehensive target list ('codebases, APIs, services, CLI tools, libraries, and daemons'), but 'guidance' is somewhat abstract, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what ('Security guidance and vulnerability review for...') and when ('Use for security questions, focused reviews, vulnerability research, security audits, or pen tests'), with concrete trigger phrases and an explicit mode gate for the complete workflow.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('security questions', 'security audits', 'pen tests', 'vulnerability research', 'full/comprehensive/end-to-end reviews'), though common variants like 'security review' or 'secure code review' are absent.

4 / 5

Distinctiveness Conflict Risk

A clear security-audit niche with distinct pen-test/audit triggers, but it could overlap with generic code-review or lighter security-review skills given phrases like 'focused reviews'.

4 / 5

Total

17

/

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

relative_links

Relative link issues: 8 missing

Warning

Total

15

/

16

Passed

Repository

joshmanders/dotfiles

Path

claude/skills/security-audit/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.