CtrlK
BlogDocsLog inGet started
Tessl Logo

reviewer

Skill do Reviewer Final para validação completa antes do deploy. Use quando precisar validar que todos os passos do pipeline foram executados, checar qualidade de código, confirmar segurança, confirmar QA, confirmar documentação, ou gerar relatório de aprovação/rejeição. Trigger em: "review final", "reviewer", "aprovação", "rejeição", "validação final", "gate de deploy", "checklist final", "aprovar deploy", "pode deployar", "pronto pra produção", "validar entrega", "review completo", "última verificação".

72

Quality

88%

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-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable review-gate playbook with clear workflow sequencing, validation checkpoints, and good progressive disclosure. The main flaw is a duplicated section that hurts token efficiency.

Suggestions

Remove the duplicated 'Constituicao como rubric primario' block (lines 44-51 are a verbatim repeat of 35-42) to recover token budget.

Sharpen distinctiveness by narrowing the 'reviewer'/'review final' triggers or scoping them to the final-deploy-gate context to avoid collision with the code-reviewer subagent.

Consider moving the full anti-rationalization table to a referenced policy file and keeping only a one-line pointer, since policies/anti-rationalization.md is already cited.

DimensionReasoningScore

Conciseness

The checklists are mostly efficient, but the entire 'Constituicao como rubric primario' section is duplicated verbatim (appearing twice), which is unnecessary padding that could be tightened.

2 / 3

Actionability

Concrete, specific guidance throughout — checklists with exact thresholds ('npm audit sem HIGH/CRITICAL', 'Cobertura >= 80%', 'Nenhum any no TypeScript') and a rejection workflow that mandates skill, file/line, and problem classification.

3 / 3

Workflow Clarity

The numbered Fluxo de Review has an explicit OK/FAIL approval gate, a rejection feedback loop (rejeita → Orquestrador → skill corrige → volta), a 3-cycle cap, and pre-approval risk-banding scrutiny — clear sequence with validation checkpoints and feedback loops.

3 / 3

Progressive Disclosure

An overview playbook that points to well-signaled, one-level-deep references (templates/review.md, templates/rejection.md, policies/*.md, personas/code-reviewer.md) with no nested reference chains; inline checklists are the operational core that belongs in SKILL.md.

3 / 3

Total

11

/

12

Passed

Description

92%Weight 40%Scale 1-3

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 that explicitly states capabilities and trigger conditions in third person with rich natural-language triggers. Its only weakness is mild distinctiveness: the generic 'reviewer'/'review final' triggers risk overlap with the separate code-reviewer subagent.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'validar que todos os passos do pipeline foram executados, checar qualidade de código, confirmar segurança, confirmar QA, confirmar documentação, ou gerar relatório de aprovação/rejeição' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly answers both what (the validation actions) and when via explicit 'Use quando precisar validar...' and 'Trigger em:...' clauses, satisfying the explicit-triggers anchor.

3 / 3

Trigger Term Quality

Good coverage of natural terms a user would say via 'Trigger em: "review final", "reviewer", "aprovação", "rejeição", "gate de deploy", "checklist final", "aprovar deploy", "pode deployar", "pronto pra produção", "validar entrega", "review completo", "última verificação".'

3 / 3

Distinctiveness Conflict Risk

The final-deploy-gate niche is clear, but generic triggers like 'reviewer' and 'review final' overlap with a code-reviewer skill — the body itself warns of this confusion — so it could still trigger the wrong skill.

2 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
felvieira/claude-skills-fv
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.