Mindmap Generator - Auto-activating skill for Visual Content. Triggers on: mindmap generator, mindmap generator Part of the Visual Content skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/mindmap-generator/SKILL.mdQuality
Discovery
7%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 description is extremely thin and auto-generated, providing essentially no useful information beyond the skill name. It lacks concrete actions, meaningful trigger terms, and any explicit guidance on when Claude should select this skill. It reads like a template placeholder rather than a functional skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates hierarchical mindmaps from topics, organizes ideas into branches and sub-branches, exports as text-based or visual diagrams.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a mind map, brainstorm visually, organize ideas hierarchically, or mentions concept maps, idea trees, or visual outlines.'
Remove the duplicate trigger term 'mindmap generator' and expand with natural variations users would actually say, such as 'mind map', 'brainstorm diagram', 'concept map', 'idea map', 'visual brainstorm'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Mindmap Generator' and 'Visual Content' without describing any concrete actions like creating nodes, organizing hierarchies, exporting formats, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no specific actions described) and 'when should Claude use it' (no explicit 'Use when...' clause or meaningful trigger guidance beyond the skill name itself). | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'mindmap generator' repeated twice. Missing natural variations users would say like 'mind map', 'brainstorm diagram', 'concept map', 'visual outline', or 'create a mindmap'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'mindmap' is a somewhat specific domain, the description is so vague that it could overlap with any visual/diagramming skill. The 'Visual Content' category label adds ambiguity rather than clarity. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual content. It contains only generic boilerplate text that describes what the skill would do without providing any actionable instructions, code examples, or concrete guidance for generating mindmaps. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples of mindmap generation using a specific tool like Mermaid mindmap syntax (e.g., ```mermaid\nmindmap\n root((Central Topic))\n Branch 1\n Sub-topic\n```)
Define a clear workflow: 1) Identify the central topic and hierarchy, 2) Choose output format (Mermaid, Markmap, etc.), 3) Generate the mindmap code, 4) Validate the syntax renders correctly
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe meta-information about the skill rather than teaching how to generate mindmaps
Add specific guidance on structuring mindmap hierarchies, handling different complexity levels, and best practices for visual clarity (e.g., max depth, node naming conventions)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'mindmap generator' excessively, and provides zero actual technical content or instructions. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no examples of mindmap syntax (e.g., Mermaid mindmap syntax), no specific tools or formats. Every section is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed resources, no linked files, and no meaningful structure beyond generic boilerplate headings. | 1 / 3 |
Total | 4 / 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.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | |
b8a3b3e
Table of Contents
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.