roadmap-generator
Roadmap Generator - Auto-activating skill for Enterprise Workflows. Triggers on: roadmap generator, roadmap generator Part of the Enterprise Workflows skill category.
34
0%
Does it follow best practices?
Impact
99%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/roadmap-generator/SKILL.mdQuality
Discovery
0%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 severely lacking across all dimensions. It reads as a boilerplate template with no substantive content—no concrete actions, no meaningful trigger terms, no 'Use when' clause, and no distinguishing details. It would be nearly impossible for Claude to reliably select this skill from a pool of alternatives.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates product roadmaps with timelines, milestones, dependencies, and priority rankings from project requirements or feature lists.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a roadmap, project timeline, release plan, milestone chart, or strategic plan for a product or initiative.'
Remove the duplicate trigger term and expand with natural variations users would say, such as 'roadmap', 'product roadmap', 'project plan', 'release schedule', 'quarterly plan', 'feature timeline'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Roadmap Generator') and its category ('Enterprise Workflows') but provides no concrete actions. There is no mention of what the skill actually does—no verbs describing capabilities like 'creates timelines', 'organizes milestones', or 'generates Gantt charts'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is limited to a redundant trigger phrase with no explicit 'Use when...' clause or meaningful context for activation. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'roadmap generator' repeated twice. It misses natural variations users would say such as 'roadmap', 'project plan', 'timeline', 'milestones', 'product roadmap', 'strategic plan', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Enterprise Workflows' could overlap with many other skills, and 'roadmap generator' alone doesn't carve out a clear niche. Without specific capabilities or file types, it could easily conflict with project management, planning, or strategy skills. | 1 / 3 |
Total | 4 / 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 substantive content. It consists entirely of generic boilerplate that could apply to any topic — simply substituting 'roadmap generator' into template sentences. It provides zero actionable guidance on how to actually create roadmaps, what formats to use, what tools or structures to employ, or any domain-specific knowledge.
Suggestions
Add concrete, executable content: define what a roadmap output looks like (e.g., a Markdown template, Gantt chart structure, or JSON schema) with a complete example.
Include a step-by-step workflow for generating a roadmap: gathering inputs (goals, timelines, dependencies), structuring phases/milestones, producing the output artifact, and validating completeness.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) that describe the skill meta-information rather than teaching Claude how to perform the task.
Add at least one concrete example showing input requirements and expected roadmap output format so Claude knows exactly what to produce.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'roadmap generator' excessively, and provides zero substantive information about how to actually generate roadmaps. | 1 / 3 |
Actionability | There are no concrete steps, code examples, commands, templates, or executable guidance of any kind. Every section is vague and abstract — 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints — just generic claims about capabilities without any actual process described. | 1 / 3 |
Progressive Disclosure | The content is a flat, shallow document with no references to detailed materials, no linked resources, and no meaningful structure beyond boilerplate headings that contain no real content. | 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
4dee593
- 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.