CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reviewer

Revisa a entrega e valida criterios antes de liberar. 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".

Quality

82%

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

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

A strong instruction-only playbook: exhaustive, quantified checklists, an explicit decision workflow with real feedback loops and escalation, and disciplined structure. Weaknesses are minor — some redundancy between the checklist, rules, and flow sections, and heavy reliance on kit-external files (templates, policies, personas) that are not part of this bundle and cannot be verified. Overall an efficient, highly actionable skill body.

DimensionReasoningScore

Conciseness

The body is checklist-driven with no explanation of concepts Claude already knows, but there is redundancy: checklist items are restated in "Regras" (e.g. rules 2-3 restate the testes/documentação checklist items), "Fluxo de Review" step 2 repeats the checklist instruction, and the risk-banding paragraph is wordy. Matches 'efficient; minor instances of over-explanation that could be trimmed'; not 5 because of the repetition between sections.

4 / 5

Actionability

Concrete, verifiable guidance throughout: quantified thresholds ("Cobertura >= 80%", "npm audit sem HIGH/CRITICAL"), mandatory rejection-report fields (arquivo, linha, problema, classificação), a named routing flow, and a deterministic OK/FAIL → APPROVED/REJECTED decision rule. Not 5 because the actual report format and several referenced files (templates/review.md, personas/code-reviewer.md) are deferred to files outside this bundle, and several checklist items (e.g. "Bundle size verificado", "Queries otimizadas") give no verification method; not 3 because the guidance is specific and executable, not high-level hints.

4 / 5

Workflow Clarity

"Fluxo de Review" is a clear 7-step sequence with per-item OK/FAIL validation, an explicit decision gate, and genuine feedback loops: re-review must re-run the complete checklist ("rodar o checklist completo de novo, não só os itens que falharam antes"), a rejection workflow routes fixes to the responsible skill, and a 3-cycle cap escalates to the Orchestrator. This matches the top anchor: clear sequence, explicit validation, error-recovery loops, checklists.

5 / 5

Progressive Disclosure

Sections are well-organized (Governança, Quando Usar/Não Usar, Entradas/Saídas, per-domain checklists, Fluxo, Regras, Handoff) and external references are one level deep and purpose-annotated (e.g. "policies/verification-before-completion.md ← gate antes de aprovar PR"). No references/, scripts/, or assets/ directories exist in this bundle, so the ~12 referenced paths (policies/, templates/, personas/, skills/53, skills/91) cannot be verified here. Matches 'good structure; most content appropriately placed; references mostly clear; minor organization gaps'; not 5 because several references point outside the bundle unverifiably and the inline Anti-Rationalization table and Commit Trailers detail could live in reference files.

4 / 5

Total

17

/

20

Passed

Description

73%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 has excellent trigger-term coverage with natural, colloquial Portuguese phrases and a clear deploy-gate niche, but the capability statement is only two generic actions and gives no indication of what the validation actually covers. Overlap risk with general code-review skills is real and even acknowledged in the body. The 'what' side needs one more sentence of concrete scope to reach the top anchors.

Suggestions

Expand the capability sentence to name what is validated, e.g. 'Revisa a entrega e valida pipeline, código, testes, segurança, performance e documentação contra um checklist antes de liberar deploy' — this would lift specificity and completeness simultaneously.

Sharpen distinctiveness by scoping the triggers to final-gate moments (e.g. drop the bare "reviewer" or qualify it as "review final de entrega") to avoid firing on ordinary code-review requests.

State the output the skill produces (relatório de APPROVED/REJECTED com findings classificados) so users know what invoking it yields.

DimensionReasoningScore

Specificity

"Revisa a entrega e valida criterios antes de liberar" names the domain and two concrete actions (review the delivery, validate criteria), but does not enumerate what is validated (code, tests, security, docs) or how. Matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; not 4 because several specific actions are not listed, and not 2 because the actions are concrete rather than generic.

3 / 5

Completeness

Both 'what' ("Revisa a entrega e valida criterios antes de liberar") and 'when' (explicit "Trigger em:" clause with concrete phrases) are present. Not 5 because the 'what' is thin — "valida criterios" never says which criteria — while the anchor for 5 requires clearly and explicitly answering both; not 3 because the when-clause is explicit, not merely implied.

4 / 5

Trigger Term Quality

Thirteen natural trigger phrases including colloquial variations users would actually say: "review final", "reviewer", "aprovação", "gate de deploy", "aprovar deploy", "pode deployar", "pronto pra produção", "validar entrega", "última verificação". Coverage is comprehensive with synonyms and informal phrasings; no natural terms are obviously missing.

5 / 5

Distinctiveness Conflict Risk

The niche (final pre-deploy gate) is somewhat specific, but broad triggers like "reviewer" and "review completo" would plausibly fire a general code-review skill — the skill body itself warns "Não confundir com o subagent dev-team-kit-fv:code-reviewer". Matches 'somewhat specific but could still overlap with similar skills'; not 4 given the acknowledged overlap with closely related review skills.

3 / 5

Total

15

/

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

felvieira/claude-skills-fv

Path

skills/11-reviewer/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.