Content
37%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The SKILL.md body is a single generic persona sentence that provides no actionable guidance: it neither defines what a "structured topic analysis" looks like (sections, format, output schema) nor gives any workflow, examples, or persona detail beyond "expert analyst". The description promises structured analyses the body never equips Claude to deliver.
Suggestions
Specify the output structure for a topic analysis (e.g., required sections like overview, key entities, sub-topics, open questions, and citations) so the 'structured' claim in the description is backed by a concrete template.
Add the persona substance the skill claims: the analytical lens to apply, depth/tone expectations, and how to handle sparse or ambiguous source material.
If fuller guidance exists elsewhere (prompt templates, example analyses), move it into a reference file and link it from SKILL.md so the body serves as a real overview rather than a placeholder.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a single sentence ("You are an expert analyst.") with zero padding and zero over-explanation of concepts Claude already knows. It fully matches the "lean and efficient; assumes Claude's competence" anchor — though the missing substance is captured under actionability, not here. | 5 / 5 |
Actionability | The entire body is "You are an expert analyst." — no concrete guidance, no code or commands, no specification of the analysis structure, format, or steps. This matches the lowest anchor ("entirely vague or abstract ... only describes rather than instructs") and is arguably weaker since it barely even describes. | 1 / 5 |
Workflow Clarity | No sequence of steps exists for producing a "structured topic analysis"; there is no workflow at all to evaluate. The simple-skill exception does not apply because the single action is ambiguous — nothing defines what steps or checkpoints the analysis involves. | 1 / 5 |
Progressive Disclosure | No bundle files exist (no references/, scripts/, or assets/) and nothing is inlined that belongs elsewhere, so there are no nesting or navigation failures. However, the body has no sections or organization at all, and an MCP tool this thin provides no pointer to where a fuller persona or analysis template would live, so it sits between "no structure issues" and "minimal structure". | 3 / 5 |
Total | 10 / 20 Passed |