cli-demo-generator
This skill should be used when users want to create animated CLI demos, terminal recordings, or command-line demonstration GIFs. It supports both manual tape file creation and automated demo generation from command descriptions. Use when users mention creating demos, recording terminal sessions, or generating animated GIFs of CLI workflows.
79
70%
Does it follow best practices?
Impact
95%
2.63xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./cli-demo-generator/SKILL.mdQuality
Discovery
89%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 is a solid skill description that clearly communicates its purpose and when to use it. It has strong trigger terms and explicit 'Use when' guidance, making it easy for Claude to select appropriately. The main weakness is that the specific capabilities could be more granular—listing concrete actions like tape file editing, timing configuration, or export format options would strengthen it further.
Suggestions
Add more specific concrete actions such as 'edit tape files, configure typing speed and timing, apply themes, export to GIF/MP4/WebM' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (CLI demos, terminal recordings) and some actions (tape file creation, automated demo generation), but doesn't list multiple concrete specific actions like editing tape files, configuring timing, adding themes, or exporting formats. | 2 / 3 |
Completeness | Clearly answers both what ('create animated CLI demos, terminal recordings, or command-line demonstration GIFs' with 'manual tape file creation and automated demo generation') and when ('Use when users mention creating demos, recording terminal sessions, or generating animated GIFs of CLI workflows'). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'animated CLI demos', 'terminal recordings', 'command-line demonstration GIFs', 'creating demos', 'recording terminal sessions', 'animated GIFs', 'CLI workflows'. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused on CLI demo recording and animated GIF generation from terminal sessions. The specific mention of 'tape files', 'terminal recordings', and 'CLI demonstration GIFs' makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with concrete, executable commands and clear examples, but suffers significantly from verbosity—content is repeated across multiple sections and includes information Claude doesn't need (installation instructions, format explanations). Workflow clarity would benefit from explicit validation steps, especially for batch operations. The progressive disclosure structure exists but isn't leveraged enough, with too much detail kept inline.
Suggestions
Cut the file by ~50%: remove the 'When to Use' trigger list, the Summary section, and deduplicate content between 'Core Capabilities', 'Workflow Guidance', and 'Examples'—pick one place for each approach's example.
Move troubleshooting, best practices details, and output format information to reference files, keeping only brief pointers in the main skill.
Add validation checkpoints to batch generation workflow (e.g., 'Verify all GIFs were created: ls ./output/*.gif') and error recovery guidance for failed VHS executions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300 lines. It repeats the same commands across 'Workflow Guidance', 'Examples', and 'Core Capabilities' sections. Best practices like timing/sizing tables, troubleshooting for installing VHS/asciinema, and the summary section all add tokens without teaching Claude anything new. The 'When to Use' trigger phrases are unnecessary padding. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready commands throughout. Script parameters are clearly documented, YAML config examples are complete, and every approach includes concrete command-line invocations with specific flags and values. | 3 / 3 |
Workflow Clarity | Workflows are listed with steps but lack validation checkpoints. For batch generation (a batch operation), there's no verification step to check outputs. The interactive recording workflow mentions Ctrl+D but doesn't address what happens if conversion fails. No feedback loops for error recovery are present. | 2 / 3 |
Progressive Disclosure | References to external files exist (vhs_syntax.md, best_practices.md, templates) which is good, but the main file inlines too much content that could be in those reference files—the full best practices section, troubleshooting, output formats, and repeated examples all bloat the overview rather than being delegated to supporting files. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- fernandezbaptiste/claude-code-skills
- Commit
4f0eae8
- 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.