full-workflow
Full workflow - record + backup + convert + analyze. TRIGGERS - full workflow, complete recording, end-to-end.
Best use case
full-workflow is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Full workflow - record + backup + convert + analyze. TRIGGERS - full workflow, complete recording, end-to-end.
Teams using full-workflow 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/full-workflow/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How full-workflow Compares
| Feature / Agent | full-workflow | 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?
Full workflow - record + backup + convert + analyze. TRIGGERS - full workflow, complete recording, end-to-end.
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:full-workflow Complete end-to-end workflow: record, backup, convert, and analyze. > **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 | | --------------- | ------------------------------------- | | `-t, --title` | Recording title | | `-q, --quick` | Quick analysis after recording | | `-f, --full` | Full analysis after recording | | `-d, --domains` | Domains for analysis | | `--no-backup` | Skip streaming backup | | `--no-analyze` | Skip analysis (just record + convert) | ## Execution Chains multiple skills: record -> backup -> convert -> analyze ### Skip Logic - If `-t` provided -> use title directly - If `-q` or `-f` provided -> skip workflow configuration - If `--no-backup` -> skip backup step - If `--no-analyze` -> skip analysis step ### Workflow 1. **Config**: AskUserQuestion for workflow options 2. **Record**: Invoke asciinema-recorder 3. **Backup**: Invoke asciinema-streaming-backup (if enabled) 4. **Convert**: Invoke asciinema-converter 5. **Analyze**: Invoke asciinema-analyzer (if enabled) 6. **Report**: Display summary ## Example Usage ```bash # Quick workflow with title /asciinema-tools:full-workflow -t "Feature dev" -q # Full analysis on trading domain /asciinema-tools:full-workflow -f -d trading,ml # Record only, analyze later /asciinema-tools:full-workflow --no-analyze ``` ## Troubleshooting | Issue | Cause | Solution | | ------------------- | --------------------------- | ------------------------------------------- | | Recording not found | No active asciinema session | Run `/asciinema-tools:record` first | | Backup skipped | Daemon not running | Run `/asciinema-tools:daemon-start` | | Convert fails | Invalid .cast format | Check asciinema version with `asciinema -V` | | Analysis times out | Large recording file | Use `--no-analyze` and run separately | | Permission denied | Output dir not writable | Check directory permissions | ## 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
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.
run-full-release
Run the current repo's mise release pipeline, or bootstrap one if missing. Use when user wants to release, version bump, publish a package, or set up release automation for a new repo. Detects ecosystem (Python/Rust/Node/mixed) and scaffolds individualized mise release tasks.
issues-workflow
Plan and track work using a GitHub Issues-first workflow with sub-issue hierarchies, issue-branch-PR lifecycle, and auto-close on merge. Use whenever the user needs to organize issues into parent-child hierarchies, manage sub-issues, use closing keywords (Closes/Fixes/Resolves), create branches from issues (gh issue develop), coordinate cross-repo issue workflows, or asks about issue tracking strategy. Do NOT use for creating individual issues (use issue-create instead) or for GitHub Projects board management.
chezmoi-workflows
Dotfile backup and sync with chezmoi. TRIGGERS - chezmoi, dotfiles, sync dotfiles, backup configs, cross-machine sync.
doppler-workflows
Manage credentials and secrets through Doppler for publishing and deployment workflows. Use whenever the user needs to publish Python packages to PyPI, rotate AWS credentials, manage Doppler secrets, or configure credential pipelines for CI/CD. Do NOT use for 1Password vault operations or for secrets that are not managed through Doppler.
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.
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.