CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

claude-md-generator

Gera CLAUDE.md inteligente para projetos consumidores. Consome output do Repo Auditor, faz entrevista guiada com o dev e produz um CLAUDE.md especifico, conciso e acionavel. Use apos o Repo Auditor (18) ter mapeado o repositorio. Trigger em: "gerar claude.md", "criar claude.md", "onboarding", "setup claude md", "contexto do projeto", "documentar projeto para agente".

64

Quality

80%

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/28-claude-md-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 skill body delivers a well-sequenced, highly actionable five-phase workflow with strong validation checkpoints and a genuinely useful question-bank table. Its weaknesses are repetition of the section taxonomy across three tables and a monolithic single-file structure whose referenced templates and policy files do not exist in the skill's own bundle.

Suggestions

Consolidate the three overlapping section lists (Secoes do CLAUDE.md table, Ordem das Secoes, Padroes de Pergunta por Secao) into one canonical table referenced by each phase.

Move the audit-mode checklist, audit-report output template, and per-section question bank into reference files (e.g. references/audit-mode.md, references/interview-patterns.md) and link them one level deep from SKILL.md.

Ship or inline the referenced artifacts — templates/claude-md-output.md, GLOBAL.md, and the policies/ files are cited as required inputs but are absent from the skill bundle, leaving Phase 3 and the governance sections unactionable as written.

DimensionReasoningScore

Conciseness

The body is instruction-dense with no filler explaining known concepts, but the 11 section names are repeated three times ("Secoes do CLAUDE.md" table, "Ordem das Secoes" list, "Padroes de Pergunta por Secao" table) and "Quando Usar" re-states the description's triggers. Fits anchor 3 (mostly efficient but could be tightened) rather than 4, where only minor trimming would be needed.

3 / 5

Actionability

Concrete, executable guidance throughout: exact paths ("docs/repo-audit/current.md"), numeric decision rules ("idade < 30d", "> 90d"), verbatim question templates ("Encontrei X comandos. Outros fora dos scripts?"), and a copy-paste output template for the audit report. Not 5 because key referenced artifacts ("templates/claude-md-output.md", "policies/handoffs.md", "GLOBAL.md") are not present in the skill bundle, leaving parts of the guidance unresolvable.

4 / 5

Workflow Clarity

Five explicitly numbered phases with a prerequisite fallback (auto-run Repo Auditor), automatic mode detection rules, a command-validation checkpoint ("confirmar que existe no package.json... nao inventar comando plausivel"), a dev-approval feedback loop ("Iterar ate aprovacao"), and a diff-before-overwrite guard for the destructive case. Matches anchor 5: clear sequence, explicit validation, feedback loops, and a checklist for the audit mode.

5 / 5

Progressive Disclosure

Section headers are clear, but the ~255-line body inlines material that belongs in separate files (the full audit-report template, the per-section question bank, audit-mode details), and references to "templates/claude-md-output.md" and the "policies/" set are not resolvable within the skill's bundle. Fits anchor 3 (content that should be separate is inline; references not clearly backed) better than anchor 4.

3 / 5

Total

15

/

20

Passed

Description

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

A strong description that clearly states the pipeline (consume Repo Auditor output, interview the dev, generate the file) and gives an explicit trigger list with natural phrasing and synonym variation. The main gaps are the absence of the audit-mode capability and Portuguese-only trigger coverage with a couple of overly broad terms.

DimensionReasoningScore

Specificity

"Consome output do Repo Auditor", "faz entrevista guiada com o dev" and "produz um CLAUDE.md especifico, conciso e acionavel" name the domain plus several concrete actions. Not 5 because coverage is incomplete (no mention of the audit/refactor mode or what the 11 sections cover); not 3 because it goes beyond 1-2 generic actions with a concrete pipeline of behaviors.

4 / 5

Completeness

Explicitly answers what ("Gera CLAUDE.md inteligente... produz um CLAUDE.md especifico, conciso e acionavel") and when ("Use apos o Repo Auditor (18) ter mapeado o repositorio" plus an explicit "Trigger em:" clause with concrete phrases). Matches the anchor-5 pattern of a clear what-and-when with concrete trigger phrases; neither component is missing or weak.

5 / 5

Trigger Term Quality

Trigger list includes natural phrases and synonyms users would say: "gerar claude.md", "criar claude.md", "setup claude md", "documentar projeto para agente". Not 5 because coverage is Portuguese-only, missing common English variants ("generate claude.md", "create claude.md") and any file-extension form; clearly above anchor 3 since multiple natural phrasings with gerar/criar synonym variation are present.

4 / 5

Distinctiveness Conflict Risk

The CLAUDE.md-generation niche is clear and anchored to the Repo Auditor pipeline, with dedicated triggers like "gerar claude.md". Not 5 because broader triggers such as "onboarding" and "contexto do projeto" create minor overlap risk with generic onboarding/documentation skills; well above anchor 3 since the core triggers are highly specific.

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/28-claude-md-generator/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.