Mermaid Gantt Chart Generator - Auto-activating skill for Visual Content. Triggers on: mermaid gantt chart generator, mermaid gantt chart generator Part of the Visual Content skill category.
41
11%
Does it follow best practices?
Impact
97%
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/mermaid-gantt-chart-generator/SKILL.mdQuality
Discovery
22%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 essentially a title repeated with boilerplate metadata rather than a functional skill description. It lacks concrete actions, explicit trigger guidance, and natural keyword variations. It would be very difficult for Claude to confidently select this skill over others based on this description alone.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates Mermaid Gantt chart syntax with tasks, milestones, dependencies, and date ranges from project requirements.'
Add an explicit 'Use when...' clause with natural trigger terms like 'project timeline', 'task schedule', 'Gantt diagram', 'project plan', 'milestone chart', or 'Mermaid Gantt'.
Remove the duplicated trigger term ('mermaid gantt chart generator' is listed twice) and replace with diverse keyword variations users might naturally use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Mermaid Gantt Chart Generator') but does not describe any concrete actions like creating timelines, defining tasks, setting dependencies, or formatting chart elements. It is essentially just a label repeated. | 1 / 3 |
Completeness | The description barely answers 'what does this do' beyond the name itself, and there is no explicit 'when to use' clause with trigger guidance. The 'Triggers on' line just repeats the skill name rather than describing usage scenarios. | 1 / 3 |
Trigger Term Quality | It includes 'mermaid', 'gantt chart', and 'generator' which are relevant keywords a user might say. However, the trigger terms are duplicated verbatim and miss common variations like 'project timeline', 'task schedule', 'Gantt diagram', or 'project plan'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Mermaid Gantt Chart' is fairly specific and narrows the domain, but the vague 'Visual Content' category and lack of concrete actions could cause overlap with other Mermaid diagram skills or general charting skills. | 2 / 3 |
Total | 6 / 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/placeholder with no actual instructional content about Mermaid Gantt charts. It contains only generic boilerplate that repeats the skill name without providing any syntax, examples, code, or actionable guidance. It fails on every dimension of the rubric.
Suggestions
Add concrete Mermaid Gantt chart syntax with a complete, copy-paste-ready example (e.g., a `gantt` block with sections, tasks, dates, and dependencies).
Include specific guidance on Gantt chart features: date formats, task types (done, active, crit), milestones, section grouping, and date axis configuration.
Provide a workflow for generating Gantt charts: gather requirements → define sections/tasks → write Mermaid syntax → validate rendering → iterate on formatting.
Remove all boilerplate meta-sections ('When to Use', 'Example Triggers', 'Capabilities' descriptions) and replace with actual technical content that teaches Mermaid Gantt chart creation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the skill name excessively, and contains no actual technical content about Mermaid Gantt chart syntax or generation. | 1 / 3 |
Actionability | There is zero concrete guidance—no Mermaid syntax, no code examples, no commands, no executable content whatsoever. Every section is vague meta-description rather than instruction. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is described. The 'Capabilities' section claims step-by-step guidance but provides none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of boilerplate with no references to external files, no structured navigation, and no bundle files to support it. There is no meaningful content to organize. | 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 | |
3a2d27d
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.