CtrlK
BlogDocsLog inGet started
Tessl Logo

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

76%

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.

A well-sequenced, actionable process skill with strong workflow clarity (explicit checkpoints, feedback loops, destructive-write guard) and concrete interview/audit templates. It loses points on conciseness due to duplicated section listings and on progressive disclosure due to buried policy references and absent bundle files like the referenced output template.

Suggestions

Remove duplication: present the 11 CLAUDE.md sections once (e.g., keep the Phase 1 classification table and have Phase 3 reference it by order number instead of re-listing all sections).

Convert the 'Governanca Global' comma-list of eight policy files into a short, clearly signaled navigation block (e.g., a bulleted 'See also' list) so the references are discoverable rather than buried.

Provide the referenced templates/claude-md-output.md as a bundle file under references/ (or remove the reference) so the output template the skill depends on actually exists.

DimensionReasoningScore

Conciseness

Mostly efficient with tables and structured lists and no basic-concept preamble, but it duplicates the 11-section listing (Phase 1 classification table and Phase 3 order list) and repeats 'especifico, conciso e acionavel' multiple times, so it could be tightened.

3 / 5

Actionability

Concrete actionable guidance throughout (audit checklist with Check/Acao se falhar, per-section interview question templates with example phrasing, quality principles with concrete in/out examples, command-validation checkpoint), with a minor gap being the reference to templates/claude-md-output.md which is not present in the bundle.

4 / 5

Workflow Clarity

Five clearly sequenced phases with an explicit validation checkpoint before Phase 4 (validate commands against package.json), a feedback loop (iterate until dev approval), a destructive-write guard (diff and confirm before overwriting), and checklists for the complex process.

5 / 5

Progressive Disclosure

Single self-contained file with decent headers, but no bundle files exist, the eight policy files in 'Governanca Global' are listed as a buried comma-separated reference rather than clear navigation, and large tables (interview patterns, 11-section classification) are inlined rather than split out.

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, concrete description that explicitly covers both what the skill does and when to use it, with natural trigger synonyms. Minor fluff ('inteligente') and a couple of generic trigger terms keep specificity, trigger quality, and distinctiveness at 4 rather than 5.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete actions ('Gera CLAUDE.md', 'Consome output do Repo Auditor', 'faz entrevista guiada com o dev'), but 'inteligente' is fluff and 'gera'/'produz' overlap, so it stops short of comprehensive coverage at 5.

4 / 5

Completeness

Explicitly answers both what (generate CLAUDE.md via audit consumption + guided interview) and when ('Use apos o Repo Auditor (18) ter mapeado o repositorio' plus a concrete 'Trigger em:' list), matching the anchor for clear what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-keyword coverage with synonyms ('gerar claude.md', 'criar claude.md', 'setup claude md') plus 'onboarding'; a few terms like 'contexto do projeto' and 'documentar projeto para agente' are slightly generic, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear niche (CLAUDE.md generation from repo-audit output) with distinct triggers, but 'onboarding' and 'contexto do projeto' create minor overlap risk with general onboarding/documentation skills rather than 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.

Validation14 / 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
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.