mindmap-generator
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 weak across all dimensions. It reads like auto-generated boilerplate with no substantive information about what the skill does, how it works, or when it should be selected. The duplicate trigger term and lack of any concrete capability description make it nearly useless for skill selection among multiple options.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates hierarchical mindmaps from topics or text, creates visual node-branch diagrams, exports mindmaps as SVG or markdown outlines.'
Add an explicit 'Use when...' clause with natural trigger terms: 'Use when the user asks to create a mind map, brainstorm diagram, concept map, visual outline, or organize ideas visually.'
Remove the duplicate trigger term and expand with natural variations users would say, such as 'mind map', 'brainstorm', 'concept map', 'idea tree', 'visual hierarchy'.
| 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, etc. It is extremely vague about what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is limited to a redundant trigger term. There is no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'mindmap generator' repeated twice. It misses natural variations users would say like 'mind map', 'brainstorm diagram', 'concept map', 'create a mindmap', or 'visual outline'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'mindmap' is somewhat distinctive and unlikely to conflict with many other skills, but the vague 'Visual Content' category label could overlap with other visual/diagram skills. The lack of specificity about what distinguishes this from other diagramming tools reduces distinctiveness. | 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 shell with no actual content. It consists entirely of generic boilerplate that could apply to any skill topic, with the phrase 'mindmap generator' substituted in. There is no actionable guidance, no code examples, no tool recommendations (e.g., Mermaid, Markmap, D3), and no workflow for actually generating mindmaps.
Suggestions
Add concrete, executable examples of mindmap generation using specific tools (e.g., Mermaid mindmap syntax, Markmap markdown-to-mindmap conversion, or PlantUML mindmap diagrams).
Define a clear workflow: e.g., 1) Gather topic/subtopics from user, 2) Generate mindmap in chosen format, 3) Validate syntax, 4) Render or output the result.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that contain no actionable information and replace with actual guidance on mindmap structure, syntax, and best practices.
Include at least one complete, copy-paste-ready code/markup example showing a mindmap from input to rendered output.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and boilerplate. It explains what the skill does in vague, repetitive terms without providing any actual instructions, code, or concrete guidance. Every section restates the same information in slightly different ways. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no concrete examples, no specific tools or libraries mentioned. The 'Example Triggers' are just rephrased versions of the skill name, and 'Capabilities' are generic claims with no substance. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to external files, and no bundle files. The sections are just repetitive boilerplate headers with no real information hierarchy. | 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 | |
- Commit
3a2d27d
- 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.