backup
Stream-backup active recordings to GitHub. TRIGGERS - backup recording, sync cast, streaming backup.
Best use case
backup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Stream-backup active recordings to GitHub. TRIGGERS - backup recording, sync cast, streaming backup.
Teams using backup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/backup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How backup Compares
| Feature / Agent | backup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Stream-backup active recordings to GitHub. TRIGGERS - backup recording, sync cast, streaming backup.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# /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 ```bash # 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.
Related Skills
asciinema-streaming-backup
Real-time asciinema backup to GitHub orphan branch. TRIGGERS - streaming backup, asciinema backup, session backup, recording backup.
voice-quality-audition
Audition Kokoro TTS voices to compare quality and grade. TRIGGERS - audition voices, kokoro voices, voice comparison, tts voice, voice quality, compare voices.
settings-and-tuning
Configure TTS voices, speed, timeouts, queue depth, and bot settings. TRIGGERS - configure tts, change voice, tts speed, queue depth, tts timeout, bot config, tune settings, adjust parameters.
full-stack-bootstrap
One-time bootstrap for Kokoro TTS engine, Telegram bot, and BotFather setup. TRIGGERS - setup tts, install kokoro, botfather, bootstrap tts-tg-sync, configure telegram bot, full stack setup.
diagnostic-issue-resolver
Diagnose and resolve TTS and Telegram bot issues. TRIGGERS - tts not working, bot not responding, kokoro error, audio not playing, lock stuck, telegram bot troubleshoot, diagnose issue.
component-version-upgrade
Upgrade Kokoro model, bot dependencies, or TTS components. TRIGGERS - upgrade kokoro, update model, upgrade bot, update dependencies, version bump, component update.
clean-component-removal
Remove TTS and Telegram sync components cleanly. TRIGGERS - uninstall tts, remove telegram bot, uninstall kokoro, clean tts, teardown, component removal.
send-message
Use when user wants to send a text message on Telegram as their personal account via MTProto, text someone, or message a contact by username, phone, or chat ID.
send-media
Use when user wants to send or upload a file, photo, video, voice note, or document on Telegram via their personal account.
search-messages
Use when user wants to search for messages across all Telegram chats or within a specific chat, find old messages by text, or look up Telegram message history filtered by sender.
pin-message
Use when user wants to pin or unpin a message in a Telegram chat, group, or channel, or manage pinned messages.
mark-read
Use when user wants to mark Telegram chats as read, clear unread badges and mentions, dismiss notifications, or acknowledge messages to remove the unread counter.