
asciinema-recorder
Record Claude Code sessions with asciinema. TRIGGERS - record session, asciinema record, capture terminal, demo recording.
- Installs
- 135
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/terrylica/cc-skills --skill asciinema-recorder- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads asciinema-recorder automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
asciinema-recorder
Generate ready-to-copy commands for recording Claude Code sessions with asciinema. Dynamically creates filenames based on workspace and datetime.
Platform: macOS, Linux (requires asciinema CLI)
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.
When to Use This Skill
Use this skill when:
- Starting a new terminal recording session
- Creating demos or documentation recordings
- Capturing Claude Code sessions for review or sharing
- Generating workspace-specific recording filenames
Why This Skill?
This skill generates ready-to-copy recording commands with:
- Dynamic workspace-based filename
- Datetime stamp for uniqueness
- Saves to project's tmp/ folder (gitignored)
Requirements
| Component | Required | Installation |
|---|---|---|
| asciinema CLI | Yes | brew install asciinema |
Workflow Phases
Phase 0: Preflight Check
Purpose: Verify asciinema is installed.
# Check asciinema CLI
which asciinema && asciinema --version
If asciinema is NOT installed, use AskUserQuestion:
- question: "asciinema not found. How would you like to proceed?"
header: "Setup"
multiSelect: false
options:
- label: "Install asciinema (Recommended)" description: "Run: brew install asciinema (macOS) or apt install asciinema (Linux)"
- label: "Show manual instructions" description: "Display installation commands for all platforms"
- label: "Cancel" description: "Exit without recording"
Based on selection:
-
"Install asciinema" → Run appropriate install command based on OS:
# macOS brew install asciinema # Linux (apt) sudo apt install asciinema # Linux (pip) pip install asciinemaThen proceed to Phase 1.0.
-
"Show manual instructions" → Display the commands above, then exit skill.
-
"Cancel" → Exit skill without action.
Phase 1.0: Recording Location
Purpose: Let user choose where to save the recording.
Use AskUserQuestion:
- question: "Where should the recording be saved?"
header: "Location"
multiSelect: false
options:
- label: "$PWD/tmp/ (Recommended)" description: "Project tmp directory (gitignored)"
- label: "~/asciinema/" description: "Global recordings directory"
- label: "Custom path" description: "Specify your own directory"
Based on selection:
- "$PWD/tmp/" → Set
OUTPUT_DIR="$PWD/tmp" - "~/asciinema/" → Set
OUTPUT_DIR="$HOME/asciinema"and create if missing:mkdir -p ~/asciinema - "Custom path" → Use user's "Other" input as
OUTPUT_DIR
Phase 1.1: Recording Options
Purpose: Let user configure recording behavior.
Use AskUserQuestion:
- question: "Which recording options would you like?"
header: "Options"
multiSelect: true
options:
- label: "Add title/description" description: "Include session title in recording metadata (-t flag)"
- label: "Disable idle time limit" description: "Keep full pauses instead of 2s max (--idle-time-limit 0)"
- label: "Quiet mode" description: "Suppress asciinema status messages (-q flag)"
Based on selections, build command flags:
- "Add title" → Continue to title selection question, add
-t "title"flag - "Disable idle time limit" → Add
--idle-time-limit 0flag - "Quiet mode" → Add
-qflag
If "Add title" was selected, follow up with:
- question: "Enter a title for this recording:"
header: "Title"
multiSelect: false
options:
- label: "Use workspace name" description: "Title: ${WORKSPACE}"
- label: "Use workspace + datetime" description: "Title: ${WORKSPACE} ${DATETIME}"
- label: "Custom title" description: "Enter your own title"
Based on title selection:
- "Use workspace name" → Set
TITLE="${WORKSPACE}" - "Use workspace + datetime" → Set
TITLE="${WORKSPACE} ${DATETIME}" - "Custom title" → Use user's "Other" input as
TITLE
Phase 1.2: Detect Context & Generate Command
Purpose: Generate a copy-paste ready recording command.
Step 1.2.1: Detect Workspace
Extract workspace name from $PWD:
/usr/bin/env bash << 'SKILL_SCRIPT_EOF'
WORKSPACE=$(basename "$PWD")
echo "Workspace: $WORKSPACE"
SKILL_SCRIPT_EOF
Step 1.2.2: Generate Datetime
/usr/bin/env bash << 'SKILL_SCRIPT_EOF_2'
DATETIME=$(date +%Y-%m-%d_%H-%M)
echo "Datetime: $DATETIME"
SKILL_SCRIPT_EOF_2
Step 1.2.3: Ensure Output Directory Exists
Create the output directory selected in Phase 1.0:
mkdir -p "${OUTPUT_DIR}"
Step 1.2.4: Construct Command
Build the recording command using:
OUTPUT_DIRfrom Phase 1.0 (location selection)- Flags from Phase 1.1 (options selection)
TITLEif "Add title" was selected
# Base command
CMD="asciinema rec"
# Add flags from Phase 1.1 options
# (Claude builds this based on user selections)
# Final command format:
asciinema rec ${FLAGS} "${OUTPUT_DIR}/${WORKSPACE}_${DATETIME}.cast"
Example outputs:
# Default (no options selected):
asciinema rec /home/user/projects/my-app/tmp/my-app_2025-12-21_14-30.cast
# With title + quiet mode:
asciinema rec -t "my-app Demo" -q /home/user/projects/my-app/tmp/my-app_2025-12-21_14-30.cast
# With all options:
asciinema rec -t "my-app 2025-12-21 14:30" -q --idle-time-limit 0 ~/asciinema/my-app_2025-12-21_14-30.cast
Phase 2: User Guidance
Purpose: Explain the recording workflow step-by-step.
Present these instructions:
## Recording Instructions
1. **Exit Claude Code** - Type `exit` or press `Ctrl+D`
2. **Copy the command** shown above
3. **Paste and run** in your terminal (starts a recorded shell)
4. **Run `claude`** to start Claude Code inside the recording
5. Work normally - everything is captured
6. **Exit Claude Code** - Type `exit` or press `Ctrl+D`
7. **Exit the recording shell** - Type `exit` or press `Ctrl+D` again
Your recording will be saved to:
`$PWD/tmp/{workspace}_{datetime}.cast`
Phase 3: Additional Info
Purpose: Provide helpful tips for after recording.
## Tips
- **Environment variable**: `ASCIINEMA_REC=1` is set during recording
- **Playback**: Use `asciinema-player` skill or `asciinema play file.cast`
- **Upload (optional)**: `asciinema upload file.cast` (requires account)
- **Markers**: Add `asciinema marker` during recording for navigation points
TodoWrite Task Templates
Template: Record Claude Code Session
1. [Preflight] Check asciinema CLI installed
2. [Preflight] Offer installation if missing
3. [Context] Detect current workspace from $PWD
4. [Context] Generate datetime slug
5. [Context] Ensure tmp/ directory exists
6. [Command] Construct full recording command
7. [Guidance] Display step-by-step instructions
8. [Guidance] Show additional tips (playback, upload)
9. Verify against Skill Quality Checklist
Post-Change Checklist
After modifying this skill:
- Command generation still uses
$PWD(no hardcoded paths) - Guidance steps remain clear and platform-agnostic
- TodoWrite template matches actual workflow
- README.md entry remains accurate
- Validate with quick_validate.py
CLI Options Reference
| Option | Flag | Description |
|---|---|---|
| Title | -t | Recording title (for asciinema.org) |
| Quiet | -q | Suppress status messages |
| Append | -a | Append to existing recording |
Troubleshooting
"Cannot record from within Claude Code"
Cause: asciinema must wrap the program, not be started from inside.
Fix: Exit Claude Code first, then run the generated command.
"Recording file too large"
Cause: Long sessions produce large files.
Fix:
- Use
asciinema uploadto store online instead of locally - Split long sessions into smaller recordings
"Playback shows garbled output"
Cause: Terminal size mismatch.
Fix: Use -r flag during playback to resize terminal.
Reference Documentation
Post-Execution Reflection
After this skill completes, reflect before closing the task:
- Locate yourself. — Find this SKILL.md's canonical path before editing.
- What failed? — Fix the instruction that caused it.
- What worked better than expected? — Promote to recommended practice.
- What drifted? — Fix any script, reference, or dependency that no longer matches reality.
- Log it. — Evolution-log entry with trigger, fix, and evidence.
Do NOT defer. The next invocation inherits whatever you leave behind.
FAQ
What does the asciinema-recorder skill do?
Record Claude Code sessions with asciinema. TRIGGERS - record session, asciinema record, capture terminal, demo recording.
How do I install asciinema-recorder?
Run npx skills add https://github.com/terrylica/cc-skills --skill asciinema-recorder in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/asciinema-recorder/ (personal) or .claude/skills/asciinema-recorder/ (project).
Which AI agents can use asciinema-recorder?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is asciinema-recorder safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains asciinema-recorder?
It is published by terrylica in terrylica/cc-skills. It has 135 recorded installs.
More from terrylica/cc-skills
mise-tasks
terrylica/cc-skills
Orchestrate multi-step project workflows using mise task definitions with dependency management and argument handling. Use whenever the user.
pandoc-pdf-generation
terrylica/cc-skills
PDF generation from markdown via Pandoc/XeLaTeX. TRIGGERS - markdown for PDF, print document, pandoc
mql5-indicator-patterns
terrylica/cc-skills
MQL5 indicator development patterns. TRIGGERS - MQL5 indicator, OnCalculate, indicator buffers, MetaTrader 5.
python-logging-best-practices
terrylica/cc-skills
Python logging with loguru, structlog, and orjson. TRIGGERS - loguru, structlog, structured logging
gdrive-access
terrylica/cc-skills
Access Google Drive via CLI with 1Password OAuth: list files, download, and sync folders. TRIGGERS - google drive, gdrive, drive folder, download drive, sync drive.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.