component-version-upgrade
Upgrade Kokoro model, bot dependencies, or TTS components. TRIGGERS - upgrade kokoro, update model, upgrade bot, update dependencies, version bump, component update.
Best use case
component-version-upgrade is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Upgrade Kokoro model, bot dependencies, or TTS components. TRIGGERS - upgrade kokoro, update model, upgrade bot, update dependencies, version bump, component update.
Teams using component-version-upgrade 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/component-version-upgrade/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How component-version-upgrade Compares
| Feature / Agent | component-version-upgrade | 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?
Upgrade Kokoro model, bot dependencies, or TTS components. TRIGGERS - upgrade kokoro, update model, upgrade bot, update dependencies, version bump, component update.
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
# Component Version Upgrade Upgrade individual components of the TTS + Telegram bot stack without rebuilding the entire system. > **Platform**: macOS (Apple Silicon) --- > **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 - User wants to upgrade Kokoro TTS engine, Python dependencies, or the model - User wants to update bot dependencies (Bun packages) - User wants to refresh `tts_generate.py` from the plugin bundle - User wants to bump the Bun runtime version --- ## Requirements - `uv` installed (`brew install uv`) - `mise` installed and configured - Internet connectivity for package downloads - Existing installation (run `full-stack-bootstrap` first if not installed) --- ## Upgradeable Components | Component | Command | What It Does | | ----------------- | ------------------------------------------------------------ | -------------------------------------------------------------- | | Kokoro TTS engine | `kokoro-install.sh --upgrade` | Upgrades Python deps, re-downloads model, updates version.json | | Bot dependencies | `cd ~/.claude/automation/claude-telegram-sync && bun update` | Updates Bun packages per package.json | | tts_generate.py | Re-copy from plugin `scripts/` to `~/.local/share/kokoro/` | Updates the TTS generation script | | Bun runtime | `mise use bun@latest` | Updates the Bun version in mise.toml | --- ## Workflow Phases ### Phase 1: Component Selection Ask the user which component to upgrade using AskUserQuestion. Present the four options above. ### Phase 2: Pre-Upgrade Health Check ```bash # Run health check to establish baseline ~/.local/share/kokoro/../../eon/cc-skills/plugins/tts-tg-sync/scripts/kokoro-install.sh --health # Record current versions cat ~/.local/share/kokoro/version.json ``` ### Phase 3: Execute Upgrade Run the appropriate upgrade command for the selected component. ### Phase 4: Post-Upgrade Verification ```bash # Health check again kokoro-install.sh --health # Generate test audio to verify TTS still works ~/.local/share/kokoro/.venv/bin/python ~/.local/share/kokoro/tts_generate.py \ --text "Upgrade verification test" --voice af_heart --lang en-us --speed 1.0 \ --output /tmp/kokoro-tts-upgrade-test.wav ``` ### Phase 5: Bot Restart (if needed) If bot dependencies or Bun runtime were upgraded, restart the bot: ```bash pkill -f 'bun.*src/main.ts' || true cd ~/.claude/automation/claude-telegram-sync && bun --watch run src/main.ts ``` --- ## TodoWrite Task Templates ``` 1. [Identify] Present upgradeable components via AskUserQuestion 2. [Preflight] Run health check on target component 3. [Backup] Note current versions (version.json, package.json) 4. [Upgrade] Execute upgrade command 5. [Verify] Run post-upgrade health check 6. [Test] Generate test audio to verify TTS still works 7. [Restart] Restart bot if needed 8. [Report] Show before/after versions ``` --- ## Post-Change Checklist - [ ] Health check passes (all 6 checks OK) - [ ] version.json updated with new versions - [ ] Test audio generates and plays correctly - [ ] Bot is running if it was restarted ## Troubleshooting | Problem | Likely Cause | Fix | | ----------------------------- | ------------------------------------ | ---------------------------------------------------------------- | | Upgrade fails | No internet or PyPI issue | Check connectivity, retry | | Model download slow | First-time ~400MB, subsequent cached | Wait for download to complete | | Version mismatch | Stale version.json | Re-run `kokoro-install.sh --health` to check, `--upgrade` to fix | | MLX-Audio import fails | mlx-audio version incompatibility | `kokoro-install.sh --upgrade` reinstalls mlx-audio | | Bot won't start after upgrade | Dependency conflict | `cd ~/.claude/automation/claude-telegram-sync && bun install` | --- ## Reference Documentation - [Upgrade Procedures](./references/upgrade-procedures.md) -- Step-by-step upgrade instructions with rollback for each component - [Evolution Log](./references/evolution-log.md) -- Change history for this skill ## Post-Execution Reflection After this skill completes, reflect before closing the task: 0. **Locate yourself.** — Find this SKILL.md's canonical path (Glob for this skill's name) before editing. All corrections target THIS file and its sibling references/ — never other documentation. 1. **What failed?** — Fix the instruction that caused it. If it could recur, add it as an anti-pattern. 2. **What worked better than expected?** — Promote it to recommended practice. Document why. 3. **What drifted?** — Any script, reference, or external dependency that no longer matches reality gets fixed now. 4. **Log it.** — Every change gets an evolution-log entry with trigger, fix, and evidence. Do NOT defer. The next invocation inherits whatever you leave behind. --- ---
Related Skills
clean-component-removal
Remove TTS and Telegram sync components cleanly. TRIGGERS - uninstall tts, remove telegram bot, uninstall kokoro, clean tts, teardown, component removal.
upgrade
Upgrade Kokoro TTS engine dependencies and model. TRIGGERS - upgrade kokoro, update tts, kokoro update, update mlx-audio.
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.
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.
manage-members
Use when user wants to manage Telegram group or channel members, including inviting users, kicking or banning someone, listing members, or filtering admins.