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".

71

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted, highly actionable skill that provides clear multi-phase workflows with explicit validation checkpoints and concrete decision tables. Its main weakness is length — at ~250 lines with some redundancy, it could benefit from splitting detailed reference tables (interview patterns, audit checklist) into separate files. The dual-mode operation (generate vs audit) is well-designed with automatic detection logic and clear output formats for each mode.

Suggestions

Consider extracting the detailed interview pattern table and audit checklist into separate reference files (e.g., `references/interview-patterns.md` and `references/audit-checklist.md`) to reduce the main SKILL.md length and improve progressive disclosure.

Remove or consolidate the 'Quando Usar/Quando Nao Usar' sections — some items are obvious (e.g., 'em scaffolds vazios sem codigo') and Claude can infer these constraints from context.

DimensionReasoningScore

Conciseness

The skill is fairly long (~250 lines) with some redundancy between sections (e.g., the section listing table appears twice in slightly different forms, and the 'Quando Usar/Nao Usar' sections contain some obvious statements). However, most content is specific and non-trivial — the audit checklist, interview patterns, and mode detection logic all earn their tokens. Some tightening is possible but it's not egregiously verbose.

2 / 3

Actionability

The skill provides highly concrete, actionable guidance: specific file paths to read, exact classification categories (inferida/parcial/desconhecida), a detailed interview pattern table with exact question templates per section and state, a concrete audit checklist with specific checks and actions, mode detection rules with age thresholds, and a clear output template. Commands and paths are specific and copy-paste ready.

3 / 3

Workflow Clarity

The 5-phase workflow (Ingestão → Entrevista → Geração → Review → Escrita) is clearly sequenced with explicit validation checkpoints: prerequisite fallback if audit is missing, dev approval loop in Phase 4, diff confirmation before overwriting existing files, and the audit mode has its own structured checklist with pass/fail actions. The feedback loop (iterate until dev approves) is explicit.

3 / 3

Progressive Disclosure

The skill references several external files (GLOBAL.md, policies/*, templates/claude-md-output.md, docs/repo-audit/current.md) which is good progressive disclosure design. However, no bundle files were provided, so we can't verify these references resolve. The SKILL.md itself is monolithic — the audit mode content, interview patterns, and generation rules could potentially be split into separate reference files given the length. The content is well-structured with clear headers but everything is inline.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly communicates its purpose, workflow dependencies, and trigger conditions. It specifies concrete actions (consume audit output, interview dev, produce CLAUDE.md), explicitly states when to use it (after Repo Auditor), and provides a comprehensive list of natural trigger terms. The only minor note is that it's written in Portuguese, which is appropriate if the skill ecosystem targets Portuguese-speaking users.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: consumes Repo Auditor output, conducts guided developer interview, and produces a specific/concise/actionable CLAUDE.md file. These are clear, distinct steps.

3 / 3

Completeness

Clearly answers both 'what' (generates intelligent CLAUDE.md by consuming Repo Auditor output and conducting guided interviews) and 'when' (explicit 'Use após o Repo Auditor' clause plus a dedicated 'Trigger em:' section with specific phrases).

3 / 3

Trigger Term Quality

Explicitly lists natural trigger terms users would say: 'gerar claude.md', 'criar claude.md', 'onboarding', 'setup claude md', 'contexto do projeto', 'documentar projeto para agente'. Good coverage of variations including Portuguese natural language terms.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche: specifically generates CLAUDE.md files for consumer projects, depends on a specific upstream skill (Repo Auditor #18), and has unique trigger terms like 'claude.md' and 'documentar projeto para agente' that are unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

9

/

11

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.