CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

security-review

Review a change, module, or surface for exploitable defects — trust boundaries, authn/authz, injection, secret exposure, filesystem and network reach, dependency risk. Use when the user asks for a security review, audit, or vulnerability check of concrete code. Not for general code review, lint, or compliance paperwork.

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 tight, well-structured procedural skill body: lean prose, a clearly sequenced procedure with built-in verification and honesty constraints, and an effective completion checklist. The single weakness is the absence of concrete pattern examples and a sample finding that would make the guidance copy-paste ready.

Suggestions

Add one or two concrete rg patterns for step 1/step 4 (e.g. `rg -n 'exec|spawn|system\(' --type py` and a token/secret regex) so the tool guidance is copy-paste ready.

Include a one-line example finding in the Findings format section (severity, file:line, reachable path, fix) so the required output shape is unambiguous.

Consider a brief example of the 'checked and clean' list format to anchor the honesty convention the scope statement relies on.

DimensionReasoningScore

Conciseness

The ~64-line body is lean and imperative throughout with zero padding — it never explains concepts Claude already knows (no 'what is SQL injection' prose) and every line adds review-specific guidance. Matches the 'every token earns its place' anchor.

5 / 5

Actionability

Concrete tool commands are given (`rg`, `git log -p`, `cargo audit`, `npm audit`, `osv-scanner`) and the findings format is precisely specified, but there are no example invocations (e.g. an `rg` pattern for token/key/secret) or a sample finding, so it falls short of the anchor-5 'specific examples cover the common cases'.

4 / 5

Workflow Clarity

Clear sequence (scope → 7-step procedure → findings format → limits → completion criteria) with an explicit validation checkpoint (step 7: 'Trace the real call path or write a minimal proof'), a feedback loop ('If you cannot prove reachability, downgrade the claim'), and a completion checklist. The read-only review has no destructive operation, so the validation cap does not apply.

5 / 5

Progressive Disclosure

The skill is fully self-contained with no bundle files and no external references, organized into clean sections (Scope, Procedure, Findings format, Recovery and limits, Completion criteria). Per the rubric's simple-skill guidance, well-organized sections with no need for external references warrant the top score.

5 / 5

Total

19

/

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: concrete capability enumeration, explicit use/non-use triggers, and explicit disambiguation from general code review. The only gap is modest synonym coverage for trigger terms.

DimensionReasoningScore

Specificity

The description names the domain ('exploitable defects') and comprehensively enumerates concrete defect classes — 'trust boundaries, authn/authz, injection, secret exposure, filesystem and network reach, dependency risk' — leaving no evident gaps in the security-review surface. Anchor 4 ('minor gaps in coverage') fits worse than the comprehensive anchor 5.

5 / 5

Completeness

It explicitly answers both what ('Review a change, module, or surface for exploitable defects — ...') and when ('Use when the user asks for a security review, audit, or vulnerability check of concrete code'), with concrete trigger phrases plus an explicit exclusion clause. This matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

'security review', 'audit', and 'vulnerability check' are natural phrases a user would say, giving good keyword coverage. Common synonyms like 'pentest', 'threat model', or 'CVE' are missing, so it falls just below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

'Not for general code review, lint, or compliance paperwork' explicitly disambiguates it from its nearest sibling skill, and the security-specific triggers create a clear niche with minimal conflict risk.

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

Hmbown/Codewhale

Path

crates/tui/assets/skills/security-review/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.