Convert

/asciinema-tools:convert

Convert asciinema .cast recordings to clean .txt files. Supports single file and batch directory modes.

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

Single File Mode

Batch Mode

Note: --batch and positional file are mutually exclusive.

Execution

Invoke the asciinema-converter skill with user-selected options.

Single File Skip Logic

• If file provided → skip Phase 1 (file selection)
• If options provided → skip Phase 2 (options)
• If -o provided → skip Phase 3 (output location)
• If --analyze provided → skip Phase 6 and auto-run analyze

Batch Mode Skip Logic

• If --batch provided → skip Phases 1-3, enter batch phases (7-10)
• If --source provided → skip Phase 7 (source selection)
• If --output-dir provided → skip Phase 8 (output organization)

Single File Workflow

1. Preflight: Check asciinema convert command 2. Discovery: Find .cast files 3. Selection: AskUserQuestion for file 4. Options: AskUserQuestion for conversion options 5. Location: AskUserQuestion for output location 6. Execute: Run asciinema convert 7. Report: Display compression ratio 8. Next: AskUserQuestion for follow-up action

Batch Workflow

1. Preflight: Check asciinema convert command 2. Source: AskUserQuestion for source directory 3. Output: AskUserQuestion for output directory 4. Execute: Batch convert with progress reporting 5. Report: Display aggregate compression stats 6. Next: AskUserQuestion for follow-up action

Examples

# Single file conversion
/asciinema-tools:convert ~/Downloads/session.cast

# Batch mode with defaults
/asciinema-tools:convert --batch

# Batch mode with custom paths
/asciinema-tools:convert --batch --source ~/Downloads --output-dir ~/cast-txt/

# Batch mode, force re-convert existing
/asciinema-tools:convert --batch --skip-existing=false

Troubleshooting

Post-Execution Reflection

After this skill completes, check before closing:

1. Did the command succeed? — If not, fix the instruction or error table that caused the failure. 2. Did parameters or output change? — If the underlying tool's interface drifted, update Usage examples and Parameters table to match. 3. 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.

Evolution Log

Convention: Reverse chronological order (newest on top, oldest at bottom). Prepend new entries.

---

2026-02-26: Initial Evolution Log

Status: Skill is in use and maintained. Track improvements here.

Purpose

This evolution log tracks updates to the skill. Each entry should note:

• What changed (content, structure, tooling)
• Why it changed (bug fix, feature request, best practice)
• Files affected

How to Use

1. When updating SKILL.md or references, add an entry here with the date 2. Keep entries reverse-chronological (newest first) 3. Link to ADRs or GitHub issues when relevant 4. Reference specific line changes when helpful

---