/asciinema-tools:backup

Configure and manage streaming backup to GitHub orphan branch.

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
install	Configure and start backup automation
status	Show active backups and last sync
stop	Disable backup for current session
history	View recent backup commits
-r, --repo	GitHub repository (e.g., owner/repo)
-i, --interval	Sync interval (e.g., 30s, 5m)
--chunk	Split at idle time
--meta	Include session metadata

Execution

Invoke the asciinema-streaming-backup skill with user-selected options.

Skip Logic

• If action provided -> skip Phase 1 (action selection)
• If -r and -i provided -> skip Phase 2-3 (config and repo)

Workflow

1. Preflight: Check gh CLI and fswatch
2. Action: AskUserQuestion for action type
3. Config: AskUserQuestion for backup settings
4. Repo: AskUserQuestion for repository selection
5. Execute: Run selected action

Examples

# Check current backup status
/asciinema-tools:backup status

# Configure and start backup automation
/asciinema-tools:backup install

# View recent backup history
/asciinema-tools:backup history

# Stop backup for current session
/asciinema-tools:backup stop

Troubleshooting

Issue	Cause	Solution
gh not found	gh CLI not installed	brew install gh
fswatch not found	fswatch not installed	brew install fswatch
Auth error	GitHub token invalid/expired	Run gh auth login
Orphan branch error	Branch not initialized	Run /asciinema-tools:daemon-setup
No recordings found	No active .cast files	Start a recording first

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.