documenter

Skill de Documentação por nível de decisão. Use quando precisar documentar features, APIs, arquitetura, setup, operação, ou manter documentação existente atualizada. Trigger em: "documentar", "documentação", "docs", "ADR", "architecture decision record", "README", "feature doc", "api doc", "setup doc", "runbook", "troubleshooting", "doc de operação", "registrar decisão", "atualizar docs", "documentar repositório", "repo wiki", "mapa de arquitetura", "C4", "documentação completa do código", "regras de negócio", "RPA", "automação", "segurança do app", "melhorias do repositório", "site da documentação", "HTML offline", "buscar na documentação".

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%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 well-structured and highly actionable with strong validation checkpoints and feedback loops. The main weakness is progressive disclosure: the extensive Repo-Wiki section is inlined rather than kept as a brief pointer to the dedicated repository-intelligence guide.

Suggestions

Move the bulk of the Repo-Wiki section into docs/skill-guides/documenter-repository-intelligence.md and keep only a short summary plus the pointer in SKILL.md to improve progressive disclosure.

Add one concrete inline example (e.g. a minimal ADR or feature rules.md body) to close the small actionability gap.

Tighten the evidence-contract prose in the Repo-Wiki section to reduce repeated constraint statements.

Dimension	Reasoning	Score
Conciseness	Largely efficient — actionable rules, directory trees, tables, and exact commands rather than padded concept explanations — but the dense Repo-Wiki prose and evidence-contract sections repeat some constraints and could be tightened further.	4 / 5
Actionability	Provides concrete directory structures, exact runnable commands (e.g. "node scripts/run-repo-wiki-runtime.mjs --repo . --output ..."), per-level content checklists, and specific rules; minor gaps such as no inline example ADR file body.	4 / 5
Workflow Clarity	Multi-step workflows are clearly sequenced with explicit validation checkpoints — the grep-based "Checkpoint antes de finalizar" feedback loop, the conclusion gate (Markdown válido, links resolvidos, external_requests: 0), and the geometry verification checklist — matching the anchor for clear sequences with feedback loops and checklists.	5 / 5
Progressive Disclosure	References are clearly signaled and one level deep (policies/*, docs/skill-guides/documenter-templates.md, documenter-repository-intelligence.md), but the large inline Repo-Wiki section duplicates content that belongs in the referenced repository-intelligence guide, leaving content that should be separate inline.	3 / 5
	Total	16 / 20 Passed

Description

96%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 is strong: it clearly states the skill's purpose, gives concrete documentation actions, and provides a comprehensive bilingual trigger list. The only weakness is a few overly broad trigger terms that risk overlap with security or automation skills.

Suggestions

Narrow broad trigger terms like "automação", "segurança do app", and "regras de negócio" to documentation-specific phrasings (e.g. "documentar regras de negócio") to reduce conflict with adjacent skills.

Consider trimming the trigger list slightly — the sheer length may dilute the most decisive triggers (ADR, runbook, repo wiki, C4).

Dimension	Reasoning	Score
Specificity	Lists multiple concrete documentation actions across domains — "documentar features, APIs, arquitetura, setup, operação, ou manter documentação existente atualizada" — giving comprehensive coverage of the skill's scope.	5 / 5
Completeness	Explicitly answers both "what" ("Skill de Documentação por nível de decisão") and "when" ("Use quando precisar documentar..." plus a concrete "Trigger em:" list), matching the anchor for clear what-and-when with concrete triggers.	5 / 5
Trigger Term Quality	Extensive natural trigger terms in Portuguese and English with synonyms and variations ("documentar", "docs", "ADR", "architecture decision record", "README", "runbook", "troubleshooting", "repo wiki", "C4"), matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Mostly distinct niche (documentation by decision level) with specific triggers like ADR, runbook, repo wiki, C4; minor overlap risk from broad terms such as "automação", "segurança do app", and "regras de negócio" that could match adjacent skills.	4 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	15 / 16 Passed

Repository: felvieira/claude-skills-fv
Path: skills/10-documenter/SKILL.md
Commit: 74aa7c1

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.