CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-security

Use when reviewing a branch diff for security concerns — auth, tokens and sessions, injection, secrets, cookies, CSP and third-party content — and reporting findings with S-C/H/M/L IDs in the four-field format.

Quality

89%

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

85%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 exceptionally actionable, well-sequenced review workflow with genuine progressive disclosure and validation feedback loops. The one weakness is redundancy: the report-shape discipline is explained and re-justified across three separate passages, inflating token cost without adding guidance beyond the first statement.

Suggestions

Consolidate the report-shape rules into a single authoritative section (Step 0 or Report shape) and reduce the other two mentions to the bare grep check plus a one-line pointer, cutting the repeated rationale ('the file is the deliverable', 'however good the analysis') to one statement.

Trim the justificatory prose in Step 0 and the bolded warnings (e.g. the full enumeration of invented headings like '## Summary, ## Verified strengths, ## Scope and method') to the rule plus one example, since the grep -c '^## ' check already catches every instance mechanically.

State each rule once at the point of use instead of previewing and recapping it — e.g. the 'comment is a claim, not a control' rule appears at the top of Step 2 and is re-invoked inside the JWT subsection; a back-reference would serve the same purpose in fewer tokens.

DimensionReasoningScore

Conciseness

The body is dense and repo-specific with no explanations of concepts Claude already knows, but the report-shape rules are argued three times — Step 0's rationale, the Step 2 mid-run check, and the Report shape / final-check sections — with repeated justificatory prose ("however good the analysis is" appears twice) and multiple restatements of the no-fifth-heading rule. It is mostly efficient but could be tightened to one authoritative shape section plus the two checks, which fits the 'could be tightened' anchor rather than the 'minor trim instances' anchor of 4.

3 / 5

Actionability

Fully executable throughout: copy-paste bash for the report skeleton, base-branch resolution and routing greps with exact patterns, a concrete grep/group/compare procedure for sibling-verb checks, a tabulate-then-apply procedure for JWT verification options, and an exact per-finding template. Every instruction names the command, the file, or the code construct to look for.

5 / 5

Workflow Clarity

Clear multi-step sequence (skeleton → route the diff → work mandatory sections → report shape) with explicit validation checkpoints — the `grep -c` heading-count check run once after the first finding and again at the end, both with defined recovery actions (restore the four headings, re-place the finding, edit rather than rewrite). Routing rules and per-section recording order make the sequence self-pacing.

5 / 5

Progressive Disclosure

Both referenced files (references/checklists.md, references/compliance.md) exist, are exactly one level deep, and each is opened by an explicit condition — the Step 1 routing table for the nine checklist sections, and named diff shapes (new column, endpoint, moderation action) for compliance. The split is justified in-place (sections the eval suite does not exercise moved out; the two always-checked compliance classes kept inline), and no content that belongs in a reference is inlined bulk.

5 / 5

Total

18

/

20

Passed

Description

87%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: it states a concrete task, an explicit trigger, and a distinctive output format in one lean sentence. Its only real gap is that the body's compliance-review half (C- findings, GDPR/CCPA) is invisible in the description, which slightly undersells coverage and could cause under-triggering on compliance-focused asks.

DimensionReasoningScore

Specificity

Names the domain and concrete actions — "reviewing a branch diff for security concerns" and "reporting findings with S-C/H/M/L IDs in the four-field format" — across an enumerated list (auth, tokens and sessions, injection, secrets, cookies, CSP, third-party content). Not 5 because it omits the compliance/GDPR review that the body treats as a co-equal deliverable with its own C- prefix.

4 / 5

Completeness

Explicitly answers both questions: what ("reviewing a branch diff for security concerns … and reporting findings with S-C/H/M/L IDs in the four-field format") and when ("Use when reviewing a branch diff for security concerns") with concrete trigger phrases. It clearly matches the both-answered-with-concrete-triggers anchor rather than the 4 anchor, whose 'when' is weaker or less specific.

5 / 5

Trigger Term Quality

Good natural keyword coverage — "security concerns", "branch diff", "auth", "injection", "secrets", "cookies" — under an explicit "Use when" clause. A few natural synonyms users might say ("vulnerability", "security audit", "threat model") are missing, which keeps it below the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche — security review of a branch diff — with distinct triggers and a unique output convention (S-C/H/M/L IDs, four-field format) that no generic skill would claim. Minimal conflict risk with adjacent skills since the security scope and report format are unmistakable.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

englishstreetventures/osn

Path

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