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.
Install with Tessl CLI
npx tessl i github:daymade/claude-code-skills --skill cli-demo-generatorOverall
score
85%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
90%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 well-structured description with explicit 'Use when' guidance and good trigger term coverage for CLI demo creation. The main weakness is that the specific capabilities could be more concrete - it mentions 'tape file creation' and 'automated demo generation' but doesn't detail what specific actions or outputs are supported.
Suggestions
Add more specific concrete actions like 'configure typing speed', 'add pauses between commands', 'export to GIF/MP4', or 'customize terminal appearance' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CLI demos, terminal recordings) and mentions some actions (tape file creation, automated demo generation), but lacks specific concrete actions like 'record keystrokes', 'export to GIF', or 'edit timing'. | 2 / 3 |
Completeness | Clearly answers both what (create animated CLI demos, terminal recordings, GIFs, manual tape file creation, automated demo generation) and when (explicit 'Use when users mention creating demos, recording terminal sessions, or generating animated GIFs'). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'animated CLI demos', 'terminal recordings', 'command-line demonstration GIFs', 'demos', 'recording terminal sessions', 'animated GIFs', 'CLI workflows'. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on CLI/terminal demo creation and GIF generation. The combination of 'tape file', 'terminal recordings', and 'CLI demos' creates a distinct trigger profile unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent executable examples and clear workflow guidance for multiple use cases. The main weaknesses are moderate verbosity (explanatory phrases, redundant trigger examples) and some content duplication that could be offloaded to reference files. The skill successfully covers automated, batch, and interactive approaches with concrete commands.
Suggestions
Remove the 'When to Use This Skill' trigger examples section - Claude can infer these from the skill description
Move the detailed 'Best Practices' content to the referenced best_practices.md file and keep only a brief summary with link
Trim explanatory phrases like 'This is the easiest and most common approach' and 'For maximum control' that don't add actionable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., 'When to Use This Skill' section lists triggers Claude can infer, and some explanations like 'This is the easiest and most common approach' are unnecessary). The content could be tightened by ~20-30%. | 2 / 3 |
Actionability | Excellent actionability with fully executable bash commands, complete script parameters, YAML configuration examples, and copy-paste ready code blocks throughout. Every section provides concrete, runnable examples. | 3 / 3 |
Workflow Clarity | Clear workflow guidance section with explicit decision trees for different use cases (simple demos, batch, interactive, custom). The interactive recording process includes numbered steps with clear completion signal (Ctrl+D). Troubleshooting section provides validation/recovery paths. | 3 / 3 |
Progressive Disclosure | References external files appropriately (vhs_syntax.md, best_practices.md, templates) but the main document is quite long with content that could be moved to reference files. The 'Best Practices' section duplicates what's presumably in references/best_practices.md. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
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.