CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

detective-spec

Reconstrói especificacoes e regras de sistemas existentes. Trigger em: "legado", "engenharia reversa", "extrair spec", "documentar codigo existente", "vibe coding sem doc", "detective", "reverse spec", "o que esse codigo faz", "spec a partir do codigo".

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

88%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 operational skill: the 5-phase pipeline is fully sequenced with per-phase checkpoints, resume support, and unusually rigorous validation loops (evidence requirements, confidence scoring, anti-hallucination checks, git write verification). Its weaknesses are mild — some trimmable prose sections and heavy inline templating that keeps SKILL.md long rather than splitting detail into reference files.

DimensionReasoningScore

Conciseness

The 5-phase pipeline, output templates, and state.json schema are dense and operational, but sections like "Filosofia" (crime-scene metaphor prose), "Codigo Limpo", and the 5-skill catalog in "Integracao com Pipeline" add tokens that could be trimmed. This is minor over-explanation, matching anchor 4 rather than 3, since the bulk of the body is instruction Claude cannot infer on its own.

4 / 5

Actionability

Concrete, copy-paste-ready guidance throughout: grep patterns ("throw new", "raise", "const [A-Z_]+ = "), exact output directory structure, fill-in templates for every artifact type, an exact state.json schema, and verifiable commands ("git status --porcelain", "git diff --name-only --diff-filter=MDARCT HEAD"). Specific examples cover the common cases per anchor 5; the one soft spot ("pip install graphifyy") sits in an optional suggestion path, not the core flow.

5 / 5

Workflow Clarity

Five clearly sequenced phases each with explicit actions, outputs, and state.json checkpoints, plus a resume procedure. Validation and feedback loops are explicit: the anti-hallucination second-occurrence check (grep again, else "confidence: low" with "1 ocorrencia apenas"), confidence scoring rules, evidence requirements, and git-based write verification at completion match anchor 5's explicit validation steps and error-recovery loops.

5 / 5

Progressive Disclosure

References are one level deep and clearly signaled ("consultar docs/skill-guides/detective-spec.md apenas quando necessario", dedicated governance section listing policies/*), but no bundle files exist and the SKILL.md itself carries all four artifact templates and the full state schema inline at ~345 lines — good structure with minor organization gaps, matching anchor 4 rather than the lean-overview ideal of anchor 5.

4 / 5

Total

18

/

20

Passed

Description

86%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 clear, third-person what-statement with an explicit, well-chosen trigger list whose natural phrasings and synonyms make discovery reliable. Its only real weakness is the thin what-clause: two generic actions where naming the concrete outputs (module contracts, business rules, ADRs) would sharpen it and further reduce overlap with a plain documentation skill.

Suggestions

Expand the what-clause to name concrete outputs, e.g. "Reconstrói especificacoes de sistemas legados: contratos de modulo, regras de negocio, fluxos end-to-end e ADRs retroativos, com evidencia file:line" — this would lift specificity from 3 toward 5.

Disambiguate the "documentar codigo existente" trigger (e.g. "documentar codigo existente SEM spec" or redirect pure-documentation requests) to cut overlap risk with the Documenter skill.

DimensionReasoningScore

Specificity

The what-clause "Reconstrói especificacoes e regras de sistemas existentes" names the domain plus exactly two actions (reconstruct specs, extract rules), matching anchor 3 ("names domain and 1-2 concrete actions, but not comprehensive"). It is not anchor 4 because it omits several concrete actions the skill performs (module contracts, ADRs, traceability maps, end-to-end flows).

3 / 5

Completeness

Explicitly answers both what ("Reconstrói especificacoes e regras de sistemas existentes") and when ("Trigger em: ..." with concrete trigger phrases), matching anchor 5. The 'Use when' cap at 3 does not apply since explicit trigger guidance is present, and the when-clause is more specific than anchor 4's example.

5 / 5

Trigger Term Quality

Nine natural trigger phrases with genuine synonym and register coverage — "engenharia reversa"/"reverse spec", "extrair spec"/"spec a partir do codigo", colloquial "o que esse codigo faz", "vibe coding sem doc", "legado" — matching anchor 5's comprehensive natural-term coverage better than anchor 4's "a few natural terms missing".

5 / 5

Distinctiveness Conflict Risk

A clear niche (reverse-spec extraction from legacy code) with distinct triggers ("detective", "reverse spec", "engenharia reversa"), but "documentar codigo existente" could also fire a general documentation skill the body itself references ("Documenter (skill 10)") — minor overlap risk with a closely related skill, matching anchor 4 rather than anchor 5's minimal conflict risk.

4 / 5

Total

17

/

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

allowed_tools_field

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

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/33-detective-spec/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.