clean-component-removal
Remove TTS and Telegram sync components cleanly. TRIGGERS - uninstall tts, remove telegram bot, uninstall kokoro
What this skill does
# Clean Component Removal Orderly teardown of TTS and Telegram bot components with proper sequencing to avoid orphaned processes and stale state. > **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 uninstall the Kokoro TTS engine - User wants to remove the Telegram bot - User wants to clean up all TTS-related files - User wants to do a full teardown before reinstallation - User wants to remove specific components selectively --- ## Requirements - No special tools needed (removal uses only `rm`, `pkill`, and the install script) - User confirmation before destructive operations --- ## Removal Order The removal sequence matters. Components must be torn down in this order to avoid orphaned processes or lock contention. | Step | Component | Command | Reversible? | | ---- | ------------------ | -------------------------------------------------- | -------------------- | | 1 | Bot process | `pkill -f 'bun.*src/main.ts'` | Yes (restart bot) | | 2 | Kokoro venv | `kokoro-install.sh --uninstall` | Yes (reinstall) | | 3 | Shell symlinks | `rm -f ~/.local/bin/tts_*.sh` | Yes (re-symlink) | | 4 | Temp files | `rm -f /tmp/kokoro-tts-*.wav /tmp/kokoro-tts.lock` | N/A | | 5 | Secrets (optional) | `rm -f ~/.claude/.secrets/ccterrybot-telegram` | Requires re-creation | --- ## What Is NOT Removed (Unless Explicitly Asked) These are preserved by default to allow easy reinstallation: | Resource | Path | Why Preserved | | ---------------- | ------------------------------------------------------- | -------------------------- | | Model cache | `~/.cache/huggingface/hub/models--hexgrad--Kokoro-82M` | ~400MB download, reusable | | Bot source code | `~/.claude/automation/claude-telegram-sync/` | Git-tracked, not ephemeral | | mise.toml config | `~/.claude/automation/claude-telegram-sync/mise.toml` | Configuration SSoT | | Launchd logs | `~/.local/state/launchd-logs/telegram-bot/` | Rotated by log-rotation | | NDJSON audit | `~/.claude/automation/claude-telegram-sync/logs/audit/` | Self-rotating 14d | --- ## Workflow Phases ### Phase 1: Confirmation Use AskUserQuestion to confirm which components to remove. Present options: 1. **Full teardown** -- Remove everything (steps 1-4, ask about secrets) 2. **TTS only** -- Remove Kokoro venv + symlinks + temp files (steps 2-4) 3. **Bot only** -- Stop bot process (step 1 only) 4. **Selective** -- Let user pick individual steps ### Phase 2: Stop Bot Process ```bash # Check if bot is running pgrep -la 'bun.*src/main.ts' # Stop it pkill -f 'bun.*src/main.ts' || echo "Bot was not running" ``` ### Phase 3: Remove Kokoro Venv ```bash # Uses kokoro-install.sh --uninstall (removes venv, keeps model cache) ~/eon/cc-skills/plugins/tts-tg-sync/scripts/kokoro-install.sh --uninstall ``` ### Phase 4: Remove Symlinks ```bash # List existing symlinks first ls -la ~/.local/bin/tts_*.sh 2>/dev/null # Remove them rm -f ~/.local/bin/tts_*.sh ``` ### Phase 5: Clean Temp Files ```bash rm -f /tmp/kokoro-tts-*.wav rm -f /tmp/kokoro-tts.lock ``` ### Phase 6: Optional Secret Removal Only with explicit user confirmation: ```bash # Show what would be removed ls -la ~/.claude/.secrets/ccterrybot-telegram # Remove (requires confirmation) rm -f ~/.claude/.secrets/ccterrybot-telegram ``` --- ## TodoWrite Task Templates ``` 1. [Confirm] Ask user which components to remove via AskUserQuestion 2. [Stop] Stop bot process 3. [Venv] Run kokoro-install.sh --uninstall 4. [Symlinks] Remove ~/.local/bin/ symlinks 5. [Temp] Clean /tmp/ TTS files 6. [Secrets] Optionally remove secrets (with confirmation) 7. [Verify] Confirm all selected components removed ``` --- ## Post-Change Checklist - [ ] Bot process is not running (`pgrep -la 'bun.*src/main.ts'` returns nothing) - [ ] Kokoro venv removed (`ls ~/.local/share/kokoro/.venv` returns "No such file") - [ ] Symlinks removed (`ls ~/.local/bin/tts_*.sh` returns "No such file") - [ ] No stale lock file (`ls /tmp/kokoro-tts.lock` returns "No such file") - [ ] No orphan audio processes (`pgrep -x afplay` returns nothing) ## Troubleshooting | Problem | Likely Cause | Fix | | ---------------------------------- | ------------------------------------ | ------------------------------------------------------------- | | Symlinks still exist after removal | Glob mismatch or permission | `ls -la ~/.local/bin/tts_*` then `rm -f` each one | | Stale lock after removal | Process died without cleanup | `rm -f /tmp/kokoro-tts.lock` | | Model cache taking space | ~400MB in HuggingFace cache | `rm -rf ~/.cache/huggingface/hub/models--hexgrad--Kokoro-82M` | | Bot respawns after kill | Launched with `--watch` from launchd | Check `launchctl list` for relevant agents | | Audio still playing after teardown | `afplay` process outlives bot | `pkill -x afplay` | --- ## Reference Documentation - [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 in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.