CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

octopus-security-audit

OWASP compliance, vulnerability scanning, and adversarial red team testing — use for security reviews

Quality

76%

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 ./.claude/skills/skill-security-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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-structured, command-rich body that gives Claude concrete executable guidance for both quick scans and adversarial testing, with a clearly sequenced workflow that includes a validation phase. Its weaknesses are token efficiency — it restates known concepts (STRIDE, OWASP Top 10) and inlines dense model-routing detail — and references that are neither clearly signaled nor separated from the inline content.

Suggestions

Replace the Fable 5.1 section's inline paragraph with a one-line pointer to the already-referenced `skills/blocks/fable5-prompting.md` (e.g. 'Model routing exceptions: see skills/blocks/fable5-prompting.md'), keeping only the default fallback model inline.

Drop the STRIDE table and the OWASP Top 10 category list — Claude knows both — and replace them with single-line instructions like 'Enumerate threats across all 6 STRIDE categories' and 'Cover the OWASP Top 10 for the target component'.

Convert bare path references (e.g. `agents/personas/security-auditor.md`) into clearly signaled links in a dedicated References section so navigation to detail files is unambiguous.

DimensionReasoningScore

Conciseness

The body is mostly efficient — command blocks, tables, and tight lists — but includes unnecessary material: the STRIDE table restates the six threat categories Claude already knows, the OWASP Top 10 list is a bare enumeration of a well-known standard, and the Fable 5.1 section is a dense paragraph of version- and model-specific routing detail. This matches the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor rather than anchor 4, which requires only minor trimming.

3 / 5

Actionability

Concrete, executable commands dominate: orchestrate.sh invocations for spawn/squeeze/auto, copy-paste git pickaxe searches for secrets (e.g. `git log --all -p -S 'AKIA' --pickaxe-regex`), and find/grep commands for CI/CD and plugin auditing. It falls short of fully executable (5) because the CI/CD 'dangerous patterns' checks are described rather than given as commands, and the adversarial phases are characterized abstractly.

4 / 5

Workflow Clarity

Sequencing is clear: the squeeze workflow is an explicit 4-phase cycle that ends in a Validation phase ('Antigravity re-tests, confirms fixes or fails'), and mode auto-escalation criteria are enumerated concretely. It is below anchor 5 because there is no explicit error-recovery/feedback loop for the quick-scan path and no verification step for reported findings beyond the confidence-gate note.

4 / 5

Progressive Disclosure

The body has reasonable section structure, but the Fable 5.1 caveat inlines a full dense paragraph while simultaneously pointing to `skills/blocks/fable5-prompting.md` — content that belongs in the referenced file is duplicated inline — and the references (`skills/blocks/fable5-prompting.md`, `agents/personas/security-auditor.md`) are bare paths rather than clearly signaled links. This matches anchor 3: 'references present but not clearly signaled; content that should be separate is inline', and the skill is well over the 50-line simple-skill exception.

3 / 5

Total

14

/

20

Passed

Description

78%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 concise, third-person description that clearly states what the skill does and when to use it, with distinct security-specific trigger terms. Its main limitation is that the 'when' clause is generic and a few natural synonyms (pentest, security audit) are absent.

DimensionReasoningScore

Specificity

The description lists three concrete capability areas — "OWASP compliance", "vulnerability scanning", and "adversarial red team testing" — matching the anchor for several specific actions with minor gaps. It is not a 5 because coverage is incomplete relative to the skill's actual scope (secrets detection, CI/CD auditing, dependency assessment are absent), and not a 3 because it goes beyond naming a domain with 1-2 generic actions.

4 / 5

Completeness

It explicitly answers both questions: the "what" is the three named capabilities, and the "when" is the explicit clause "use for security reviews". The "when" is present but generic — it could name concrete trigger situations — which matches anchor 4 rather than the fully explicit anchor 5, and the presence of a 'use for' clause means the cap of 3 does not apply.

4 / 5

Trigger Term Quality

Good natural keyword coverage: users would plausibly say "vulnerability scanning", "red team testing", and "security reviews". It falls short of the comprehensive anchor (5) because common synonyms like "pentest", "penetration testing", and "security audit" are missing.

4 / 5

Distinctiveness Conflict Risk

Terms like "OWASP" and "adversarial red team testing" carve out a clear security-audit niche with distinct triggers and minimal conflict risk with other skills. It is above anchor 4 because the niche is unambiguous rather than merely 'mostly distinct'.

5 / 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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

nyldn/claude-octopus

Path

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