CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cc-skill-security-review

This skill ensures all code follows security best practices and identifies potential vulnerabilities. Use when implementing authentication or authorization, handling user input or file uploads, or creating new API endpoints.

Quality

65%

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 ./.agents/skills/cc-skill-security-review/SKILL.md

The canonical home for this skill is cc-skill-security-review in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

50%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 highly actionable, with concrete code and commands for each security topic, but it is a monolithic 500-line checklist that re-teaches security fundamentals Claude already knows and duplicates its checklists. There is no sequenced review workflow and no progressive disclosure — everything, including niche content like Solana wallet verification, is inlined in SKILL.md.

Suggestions

Cut the body to a lean core checklist and move per-topic deep dives (SQL/XSS/CSRF examples, Solana section, security tests) into references/ files linked one level deep, e.g., '**XSS**: See [references/xss.md]'.

Define an ordered review workflow with validation checkpoints (e.g., 1. grep for hardcoded secrets, 2. npm audit, 3. review auth paths, 4. run the pre-deployment checklist) instead of ten unordered topic sections.

Remove the duplicated per-topic verification checklists (kept only in the master pre-deployment list), the boilerplate closing 'When to Use'/'Limitations' filler, and fix non-executable examples like the '@solana/web3.js' verify import and the undefined '@/lib/csrf'.

DimensionReasoningScore

Conciseness

The ~500-line body inlines large amounts of standard security knowledge Claude already has (parameterized queries, httpOnly cookies, DOMPurify, express-rate-limit, npm audit), duplicates every per-topic checklist again in the 'Pre-Deployment Security Checklist', and ends with pure filler ('This skill is applicable to execute the workflow or actions described in the overview'). This matches 'noticeably verbose; several unnecessary explanations or padded sections'; it avoids a 1 because it is organized as code and checklists rather than tutorial prose.

2 / 5

Actionability

Concrete, mostly copy-paste-ready guidance throughout: zod schemas, file-upload validation, parameterized queries, RLS SQL policies, CSP headers, CSRF checks, and bash commands (npm audit, npm ci). It stops short of 5 because several examples have gaps or inconsistencies — `import { verify } from '@solana/web3.js'` is not a real export, express-rate-limit's `app.use` is mixed into a Next.js-oriented skill, and the CSRF example depends on an undefined `@/lib/csrf`.

4 / 5

Workflow Clarity

The content is organized as ten parallel topic sections plus checklists, but there is no sequenced process for conducting a review — no ordering of steps, no 'run this, then check that' flow, and the per-topic 'Verification Steps' are static checkboxes rather than validation checkpoints in a workflow. This fits 'steps listed but validation gaps; sequence present but checkpoints missing or implicit'; it is not a 2 because the checklists do provide implicit verification structure.

3 / 5

Progressive Disclosure

Section headers are clear and consistent (When to Use, ten numbered topics, testing, pre-deployment checklist, resources), but the file is monolithic: ~500 lines with no references/ or scripts/ bundle, and deep per-topic content (e.g., the Solana blockchain section, full CSP and RLS examples) that belongs in separate reference files is inlined. This sits between the 2 anchor ('content that clearly belongs in separate files is inlined') and the 3 anchor — the good structure keeps it at 3, but there is zero progressive disclosure to any external material.

3 / 5

Total

12

/

20

Passed

Description

66%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.

The description follows the good pattern of pairing a capability statement with an explicit 'Use when...' clause containing natural trigger phrases. Its main weaknesses are a vague, generic 'what' (ensures best practices / identifies vulnerabilities) and a broad security scope that invites overlap with code-review and deployment skills.

Suggestions

Replace the abstract 'ensures all code follows security best practices' with concrete actions, e.g., 'Reviews code for hardcoded secrets, injection risks, missing authorization checks, and unsafe token handling'.

Broaden trigger coverage with natural synonyms users actually say: 'security review', 'vulnerability', 'audit code', 'secrets or credentials', 'XSS', 'SQL injection'.

Sharpen distinctiveness by naming the deliverable (e.g., 'runs a pre-deployment security checklist') so it does not compete with generic code-review skills.

DimensionReasoningScore

Specificity

Quotes: "ensures all code follows security best practices and identifies potential vulnerabilities" — the security domain is named with two actions, but "ensures... best practices" is generic phrasing rather than a concrete action like "reviews code for hardcoded secrets" or "sanitizes user input". It matches the anchor for naming a domain with 1-2 actions that are not comprehensive, and is below the 4 anchor because it does not list several specific concrete actions.

3 / 5

Completeness

It answers both parts: what ("ensures all code follows security best practices and identifies potential vulnerabilities") and when (an explicit "Use when..." clause with concrete triggers). It does not reach 5 because the 'what' is abstract — no concrete deliverable or action list — while the 5 anchor requires both what and when stated with equal concreteness; it is above the 4 anchor's lower bar only marginally, so 4 fits 'both present, when is explicit but what could be more specific'.

4 / 5

Trigger Term Quality

Quotes: "implementing authentication or authorization, handling user input or file uploads, or creating new API endpoints" — these are natural phrases users would say, giving good keyword coverage. It falls short of the 5 anchor because common synonyms and specific terms users would mention are missing (e.g., "security review", "vulnerability", "secrets", "XSS", "SQL injection"), yet it is clearly above the 3 anchor's "missing common variations".

4 / 5

Distinctiveness Conflict Risk

Quotes: "implementing authentication or authorization... creating new API endpoints" — the triggers are somewhat specific, but the description covers the entire security domain, which overlaps heavily with general code-review, security-testing, and deployment-review skills. It fits the 'somewhat specific but could still overlap with similar skills' anchor; it is not mostly-distinct (4) because no niche trigger (e.g., 'security checklist', 'pre-deployment audit') distinguishes it.

3 / 5

Total

14

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (505 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

BigSimmo/Communication

Path

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