본문으로 건너뛰기
cccskills
무료GitHub에 공개

asciinema-recorder

Record Claude Code sessions with asciinema. TRIGGERS - record session, asciinema record, capture terminal, demo recording.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(2)

  • SKILL.md9.1 KB
  • references/evolution-log.md704 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

ComponentRequiredInstallation
asciinema CLIYesbrew 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 asciinema
    

    Then 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 0 flag
  • "Quiet mode" → Add -q flag

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_DIR from Phase 1.0 (location selection)
  • Flags from Phase 1.1 (options selection)
  • TITLE if "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:

  1. Command generation still uses $PWD (no hardcoded paths)
  2. Guidance steps remain clear and platform-agnostic
  3. TodoWrite template matches actual workflow
  4. README.md entry remains accurate
  5. Validate with quick_validate.py

CLI Options Reference

OptionFlagDescription
Title-tRecording title (for asciinema.org)
Quiet-qSuppress status messages
Append-aAppend 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 upload to 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:

  1. Locate yourself. — Find this SKILL.md's canonical path before editing.
  2. What failed? — Fix the instruction that caused it.
  3. What worked better than expected? — Promote to recommended practice.
  4. What drifted? — Fix any script, reference, or dependency that no longer matches reality.
  5. Log it. — Evolution-log entry with trigger, fix, and evidence.

Do NOT defer. The next invocation inherits whatever you leave behind.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

sergiocarracedo/skill-organizer152026년 6월 16일 업데이트

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

sergiocarracedo/skill-organizer152026년 6월 16일 업데이트

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

sergiocarracedo/skill-organizer152026년 6월 16일 업데이트

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

sergiocarracedo/skill-organizer152026년 6월 16일 업데이트

sergiocarracedo의 스킬 모두 보기

이 스킬의 문제 신고