CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

security-review

Revisa seguranca de codigo, configuracao e aplicacoes. Trigger em: "segurança", "security review", "vulnerabilidade", "OWASP", "XSS", "CSRF", "CORS", "injection", "HttpOnly", "cookie seguro", "DRY", "code review", "boas práticas", "audit", "pentest", "sanitização".

Quality

70%

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

This is a strong operational playbook: concrete checklists with measurable thresholds, executable configuration code, an explicit fix→reverify feedback loop, and a hard release gate. The main weaknesses are re-explained basics (DRY/SOLID, prompt-injection theory) that pad the token budget, and a progressive-disclosure structure whose referenced files do not exist in the bundle. Tightening the conceptual prose and actually shipping the referenced policy/persona files would lift both.

Suggestions

Cut the SOLID/DRY principle definitions (the letter-by-letter S/O/L/I/D explanation) down to the project-specific checklist items, or move the whole code-quality section to a reference file — Claude already knows these principles.

Compress section 11's conceptual prose (lethal trifecta explanation, sidecar-pattern discussion) into the checklist items plus one-sentence pointers, keeping only the project-specific rules.

Actually include the referenced files (policies/anti-rationalization.md, personas/security-auditor.md, docs/skill-guides/security-review.md) in the bundle, or move their essential content inline, so navigation works as described.

Present the review process as an explicit numbered workflow (1. run OWASP checklists → 2. classify findings → 3. fix→reverify loop until zero críticos → 4. emit report → 5. apply release gate) at the top of the skill so execution order doesn't have to be inferred from section layout.

DimensionReasoningScore

Conciseness

The OWASP checklists and code blocks are dense and operational, but the 'Code Review - DRY Checklist' section re-teaches concepts Claude already knows ("S — Cada módulo/função faz UMA coisa", "O — Extensível sem modificar código existente") and section 11 spends ~25 lines of conceptual prose explaining the lethal trifecta and sidecar pattern. This lands on 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than level 4, where only minor trimming would be needed.

3 / 5

Actionability

The body provides copy-paste-ready TypeScript for security headers, CORS, and CSRF protection, plus concrete thresholds (bcrypt cost >= 12, JWT 15 min max, rate limit 5 tentativas/min), a quick IDOR test ('Trocar ID no request... deve retornar 403'), and a full report template. It falls short of 5 because the XSS section is a fragment (a sanitizer call and isValidUrl helper with no usage context) and the detailed output structure/persona is deferred to personas/security-auditor.md.

4 / 5

Workflow Clarity

A clear implicit sequence exists (run checklists → classify findings → emit report → apply release gate → handoff) with an explicit corrective feedback loop ('Repetir corrigir→reverificar até zero críticos, então emitir o relatório' and re-running the full checklist against the new diff) plus a six-condition release gate. It stays below 5 because the process is organized by topic rather than as an explicitly ordered procedure — a reviewer must infer the execution order from section layout.

4 / 5

Progressive Disclosure

Section structure is clear and references are signaled ('consultar docs/skill-guides/security-review.md apenas quando necessario', 'ver personas/security-auditor.md'), but the actual bundle contains only SKILL.md — every referenced path (policies/*.md, personas/security-auditor.md, docs/skill-guides/) is absent, so the described split is unverifiable. Additionally ~150 lines of checklists and code (full CSP config, two header implementations, DRY/SOLID checklist) are inlined where a reference file could carry the bulk, matching 'content that should be separate is inline' rather than level 4's 'most content is appropriately placed'.

3 / 5

Total

14

/

20

Passed

Description

65%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 pairs a minimal capability statement with an explicit, well-chosen bilingual trigger list, which is its main strength. Its weakness is the under-specified 'what' — one generic verb covering three domains — which limits specificity and completeness. Broad triggers like "code review" and "DRY" introduce mild conflict risk with general code-review skills.

Suggestions

Expand the capability clause into 2-4 concrete actions, e.g. 'Revisa código, configuração e aplicações contra o OWASP Top 10, valida headers de segurança e cookies, audita dependências com npm audit e gera relatório de findings priorizados.'

Add missing natural trigger synonyms such as 'CVE', 'vulnerabilidade crítica', 'hardening', 'autenticação', 'headers de segurança', and 'npm audit' to improve trigger coverage.

Narrow the overlapping triggers 'code review' and 'DRY' (e.g. to 'security code review') so the description does not compete with a general code-review skill.

DimensionReasoningScore

Specificity

The description offers a single generic action ("Revisa seguranca de codigo, configuracao e aplicacoes") across three domains without enumerating concrete capabilities like the OWASP checklist, dependency auditing, or header validation. This matches the anchor 'names the domain but actions are minimal or generic' rather than level 3, which requires 1-2 concrete named actions beyond the domain.

2 / 5

Completeness

Both parts are present: a 'what' ("Revisa seguranca de codigo, configuracao e aplicacoes") and an explicit 'when' ("Trigger em: ..." with concrete trigger phrases). It does not reach 5 because the 'what' is a thin single clause that omits the skill's concrete activities (checklists, dependency audit, reporting), while exceeding level 3 where 'when' is missing or only implied.

4 / 5

Trigger Term Quality

The trigger list has good bilingual coverage of natural terms ("segurança", "security review", "vulnerabilidade", "XSS", "CSRF", "pentest", "audit", "sanitização") that users would plausibly say. It falls short of level 5 because common variations like "CVE", "hardening", "autenticação", or "headers de segurança" are missing.

4 / 5

Distinctiveness Conflict Risk

The security niche is well marked by distinct triggers ("OWASP", "XSS", "CSRF", "pentest", "injection") giving minimal conflict risk with unrelated skills. Minor overlap remains with a generic code-review skill via "code review", "DRY", and "boas práticas", keeping it below 5.

4 / 5

Total

14

/

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

felvieira/claude-skills-fv

Path

skills/06-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.