Source profileQuality 95/100

terrylica/cc-skills/plugins/tts-tg-sync/skills/clean-component-removal/SKILL.md

clean-component-removal

Remove TTS and Telegram sync components cleanly. TRIGGERS - uninstall tts, remove telegram bot, uninstall kokoro

Source repository stars
62
Declared platforms
0
Static risk flags
0
Last source update
2026-08-24
Source checked
2026-08-25

Decision brief

What it does: where it fits

Orderly teardown of TTS and Telegram bot components with proper sequencing to avoid orphaned processes and stale state.

Best for

  • User wants to uninstall the Kokoro TTS engine
  • User wants to remove the Telegram bot
  • User wants to clean up all TTS-related files

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/terrylica/cc-skills --skill "plugins/tts-tg-sync/skills/clean-component-removal"
Safe inspection promptEditorial

Inspect the Agent Skill "clean-component-removal" from https://github.com/terrylica/cc-skills/blob/a5f847b22ee5afa35677e446973a903d098cd1d4/plugins/tts-tg-sync/skills/clean-component-removal/SKILL.md at commit a5f847b22ee5afa35677e446973a903d098cd1d4. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow Phases

    Use AskUserQuestion to confirm which components to remove. Present options:

    Full teardown -- Remove everything (steps 1-4, ask about secrets)TTS only -- Remove Kokoro venv + symlinks + temp files (steps 2-4)Bot only -- Stop bot process (step 1 only)
  2. 02

    Phase 1: Confirmation

    Use AskUserQuestion to confirm which components to remove. Present options:

    Full teardown -- Remove everything (steps 1-4, ask about secrets)TTS only -- Remove Kokoro venv + symlinks + temp files (steps 2-4)Bot only -- Stop bot process (step 1 only)
  3. 03

    Phase 2: Stop Bot Process

    Review the “Phase 2: Stop Bot Process” section in the pinned source before continuing.

    Review and apply the “Phase 2: Stop Bot Process” source section.
  4. 04

    Phase 3: Remove Kokoro Venv

    Review the “Phase 3: Remove Kokoro Venv” section in the pinned source before continuing.

    Review and apply the “Phase 3: Remove Kokoro Venv” source section.
  5. 05

    Phase 4: Remove Symlinks

    Review the “Phase 4: Remove Symlinks” section in the pinned source before continuing.

    Review and apply the “Phase 4: Remove Symlinks” source section.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score95/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars62SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
terrylica/cc-skills
Skill path
plugins/tts-tg-sync/skills/clean-component-removal/SKILL.md
Commit
a5f847b22ee5afa35677e446973a903d098cd1d4
License
MIT
Collected
2026-08-25
Default branch
main
View the original SKILL.md

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.

StepComponentCommandReversible?
1Bot processpkill -f 'bun.*src/main.ts'Yes (restart bot)
2Kokoro venvkokoro-install.sh --uninstallYes (reinstall)
3Shell symlinksrm -f ~/.local/bin/tts_*.shYes (re-symlink)
4Temp filesrm -f /tmp/kokoro-tts-*.wav /tmp/kokoro-tts.lockN/A
5Secrets (optional)rm -f ~/.claude/.secrets/ccterrybot-telegramRequires re-creation

What Is NOT Removed (Unless Explicitly Asked)

These are preserved by default to allow easy reinstallation:

ResourcePathWhy 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.tomlConfiguration 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

# 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

# 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

# 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

rm -f /tmp/kokoro-tts-*.wav
rm -f /tmp/kokoro-tts.lock

Phase 6: Optional Secret Removal

Only with explicit user confirmation:

# 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

ProblemLikely CauseFix
Symlinks still exist after removalGlob mismatch or permissionls -la ~/.local/bin/tts_* then rm -f each one
Stale lock after removalProcess died without cleanuprm -f /tmp/kokoro-tts.lock
Model cache taking space~400MB in HuggingFace cacherm -rf ~/.cache/huggingface/hub/models--hexgrad--Kokoro-82M
Bot respawns after killLaunched with --watch from launchdCheck launchctl list for relevant agents
Audio still playing after teardownafplay process outlives botpkill -x afplay

Reference Documentation

Post-Execution Reflection

After this skill completes, reflect before closing the task:

  1. 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.
  2. What failed? — Fix the instruction that caused it. If it could recur, add it as an anti-pattern.
  3. What worked better than expected? — Promote it to recommended practice. Document why.
  4. What drifted? — Any script, reference, or external dependency that no longer matches reality gets fixed now.
  5. 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.



Frequently asked questions

What to verify before installation and use

What does the clean-component-removal source document cover?

Orderly teardown of TTS and Telegram bot components with proper sequencing to avoid orphaned processes and stale state.

How do I install clean-component-removal?

The source record exposes this install command: npx skills add https://github.com/terrylica/cc-skills --skill "plugins/tts-tg-sync/skills/clean-component-removal". Inspect the command and pinned source before running it.

Alternatives

Compare before choosing

Computed 10029,034

garrytan/gbrain

bulk-ingestion

End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.

Computed 10024,921

alirezarezvani/claude-skills

app-store-optimization

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

Computed 10015,122

wanshuiyin/Auto-claude-code-research-in-sleep

citation-audit

Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.

Computed 10014,671

prowler-cloud/prowler

postgresql-indexing

PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance