| name | analyze |
| description | Semantic analysis of converted recordings. TRIGGERS - analyze cast, keyword extraction, find patterns. |
| allowed-tools | Bash, Grep, AskUserQuestion, Read |
| argument-hint | [file] [-d domains] [-t type] [--json] [--md] [--density] [--jump] |
/asciinema-tools:analyze
Run semantic analysis on converted .txt recordings.
Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
Arguments
| Argument | Description |
|---|
file | Path to .txt file |
-d, --domains | Domains: trading,ml,dev,claude |
-t, --type | Type: curated, auto, full, density |
--json | Output in JSON format |
--md | Save as markdown report |
--density | Include density analysis |
--jump | Jump to peak section after analysis |
Execution
Invoke the asciinema-analyzer skill with user-selected options.
Skip Logic
- If
file provided -> skip Phase 1 (file selection)
- If
-t provided -> skip Phase 2 (analysis type)
- If
-d provided -> skip Phase 3 (domain selection)
- If
--json/--md provided -> skip Phase 6 (report format)
- If
--jump provided -> auto-execute jump after analysis
Workflow
- Preflight: Check for .txt file
- Discovery: Find .txt files
- Selection: AskUserQuestion for file
- Type: AskUserQuestion for analysis type
- Domain: AskUserQuestion for domains (multi-select)
- Curated: Run ripgrep searches
- Auto: Run YAKE if selected
- Density: Calculate density windows if selected
- Format: AskUserQuestion for report format
- Next: AskUserQuestion for follow-up action
Examples
/asciinema-tools:analyze session.txt -d trading -t curated
/asciinema-tools:analyze session.txt -t full --density --json
/asciinema-tools:analyze session.txt -t auto --md
Troubleshooting
| Issue | Cause | Solution |
|---|
| ripgrep not found | Not installed | brew install ripgrep |
| YAKE not available | Python package missing | uv pip install yake |
| No keywords found | Wrong domain or sparse content | Try -t auto for discovery |
Post-Execution Reflection
After this skill completes, check before closing:
- Did the command succeed? — If not, fix the instruction or error table that caused the failure.
- Did parameters or output change? — If the underlying tool's interface drifted, update Usage examples and Parameters table to match.
- Was a workaround needed? — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.
Only update if the issue is real and reproducible — not speculative.