mcpField
C
convert

convert

github.com/terrylicaDocuments192 installsUpdated 1d ago
Repository

About convert

A skill for converting asciinema .cast recordings into clean .txt files, either individually or in batches. It helps users choose conversion options, organize outputs, and review conversion statistics.

Key features

  1. 01Single-file conversion
  2. 02Batch directory conversion
  3. 03Timestamp indexing and pause-based chunking
  4. 04Terminal dimension preservation
  5. 05Compression and aggregate statistics

Use cases

  1. 01Converting one terminal recording to text
  2. 02Processing a directory of recordings
  3. 03Splitting recordings at long idle pauses
  4. 04Organizing converted files in a chosen output directory

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/terrylica/cc-skills --skill convert

After installing, type/convertin Claude Code to confirm it loaded.

Bundled filesreferences/evolution-log.md

Details

From the project README

/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
ArgumentDescription
filePath to .cast file
-o, --outputOutput path (default: same dir)
--indexCreate timestamp indexed version
--chunksSplit at 30s+ idle pauses
--dimsPreserve terminal dimensions
--analyzeAuto-run /analyze after conversion
Batch Mode
ArgumentDescription
--batchEnable batch mode for directory conversion
--sourceSource directory (default: ~/asciinemalogs)
--output-dirOutput directory (default: ~/Downloads/cast-txt/)
--skip-existingSkip files that already have .txt output (default: true)

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

IssueCauseSolution
asciinema not foundasciinema not installedbrew install asciinema
Convert command failedCorrupted .cast fileTry asciinema cat file.cast first
No .cast files foundWrong directoryCheck --source path
Output not createdPermission deniedCheck write permissions on output
File too largeLong recording sessionUse --chunks to split at pauses

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.

Comments

Markdown supported