CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

security-review

Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.

1.11x
Quality

80%

Does it follow best practices?

Impact

97%

1.11x

Average score across 3 eval scenarios

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/cloud-profile/skills/security-review/SKILL.md

The canonical home for this skill is security-review in joe-bell/cva

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 is a highly actionable, well-structured review playbook with concrete vulnerable/safe pattern pairs and a clear confidence-gated workflow. Its two weaknesses are redundancy (the attacker-vs-server-controlled guidance is repeated three times) and a progressive-disclosure defect: the language and infrastructure guides it tells the agent to load are missing from the bundle entirely.

Suggestions

Ship the referenced languages/*.md and infrastructure/*.md files, or remove the "Load Language Guide" and "Load Infrastructure Guide" steps and fold any essential guidance into the existing references.

Consolidate the three repetitions of the attacker-controlled vs. server-controlled material (Server-Controlled Values table, Verify Exploitability table, and the overlapping Quick Patterns examples) into a single section.

Add an explicit loop-back rule when research downgrades confidence (e.g. "if research reveals server control or upstream validation, move the finding to Needs Verification or drop it").

DimensionReasoningScore

Conciseness

Mostly dense, high-signal tables, but there is noticeable duplication: the attacker-controlled vs. server-controlled distinction appears three times (the "Server-Controlled Values" table, the "Verify Exploitability" table, and the SSRF/path-traversal examples in "Quick Patterns"), and "Research Before Flagging" repeats the same bullets already stated in "Scope: Research vs. Reporting". This matches anchor 3 (mostly efficient but could be tightened) rather than anchor 4, where only minor trimming would be needed.

3 / 5

Actionability

Guidance is fully concrete and executable for a review skill: exact vulnerable and safe code patterns (e.g. "requests.get(request.GET['url'])" vs "requests.get(settings.API_URL)"), specific framework-mitigation rules ("{{ var|safe }}", "dangerouslySetInnerHTML", ".raw()"), a severity table, and a copy-paste-ready output template. It matches anchor 5 — specific examples cover the common cases; not anchor 4, which allows minor gaps.

5 / 5

Workflow Clarity

A clear six-step sequence (Detect Context → Load guides → Research → Verify Exploitability → Report) with confidence-level gating that functions as a checkpoint (only HIGH is reported, MEDIUM goes to "Needs Verification"). It falls short of anchor 5 because there is no explicit loop-back instruction when research downgrades a finding, and steps 2-3 direct loading files that are not in the bundle — a real gap, though not the missing-validation scenario that would cap at 3.

4 / 5

Progressive Disclosure

The overview-plus-references structure is well designed: context-triggered load tables and a Reference Files index with 17 real, clearly-signaled one-level-deep files. However, the Review Process instructs loading 10 files that do not exist in the bundle (all of languages/*.md and infrastructure/*.md), so a major navigation path is broken. This is more than the "minor organization gaps" of anchor 4 and fits anchor 3 (structure present but organization undermined); it does not drop to anchor 2 because the SKILL.md itself is not monolithic and existing references are clearly signaled, not buried.

3 / 5

Total

15

/

20

Passed

Description

82%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 with an explicit "Use when..." clause, natural quoted trigger phrases, and a distinct security niche. The only weakness is that the capability statement stays at the level of "systematic review with confidence-based reporting" rather than enumerating several concrete actions.

Suggestions

Replace the generic "Provides systematic review with confidence-based reporting" with 2-3 concrete actions, e.g. "Traces attacker-controlled inputs, checks framework mitigations, and reports only high-confidence findings with severity ratings."

Add missing natural trigger synonyms such as "penetration test", "secure code review", or "threat model this code" to the Use-when clause.

DimensionReasoningScore

Specificity

The description names the domain ("Security code review for vulnerabilities") and lists review areas ("injection, XSS, authentication, authorization, cryptography"), but the stated actions are generic — "systematic review" and "confidence-based reporting" — rather than several concrete, distinct actions. It fits anchor 3 (domain plus 1-2 actions, not comprehensive) better than anchor 4, which expects a list of several specific actions; the vulnerability-type list describes what gets reviewed, not what the skill does.

3 / 5

Completeness

Both halves are explicit: what it does ("Security code review for vulnerabilities... Provides systematic review with confidence-based reporting") and when to use it, via a concrete "Use when asked to..." clause listing five quoted trigger phrases. This matches anchor 5 (clear what AND when with concrete trigger phrases); anchor 4's weaker 'when' does not apply.

5 / 5

Trigger Term Quality

Natural trigger phrases are well covered — "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review" — all phrasings a user would plausibly say. It falls short of anchor 5's comprehensive synonym coverage: common variations like "penetration test", "pentest", "secure code review", or "is this code secure" are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is clear and all triggers are security-specific ("OWASP review", "find vulnerabilities"), so it is unlikely to fire for a general code-review or refactoring skill. It matches anchor 5 (clear niche, distinct triggers, minimal conflict risk) rather than anchor 4, which implies residual overlap with closely related skills.

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.claude/cloud-profile/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.