14
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill terrylica/cc-skills --skill settings-and-tuning- SKILL.md6.1 KB
Overview
This skill centralizes configuration and tuning for the TTS engine, Telegram bot, and related infrastructure using a single source of truth (mise.toml). It provides a guided workflow to inspect, edit, validate, and apply changes to voices, speeds, timeouts, queue depth, rate limits, and other bot settings. The goal is safe, auditable changes with clear restart and verification steps to make settings take effect.
How this skill works
The skill reads the mise.toml SSoT to show active env settings and groups them for user selection. It guides edits to specific env keys (voice names, TTS_SPEED, timeouts, queue limits, rate limiting, prompt executor, session picker, audit retention). After edits it validates ranges, instructs a controlled bot restart if required, and recommends verifying changes by checking logs or running a functional test.
When to use it
- Change the TTS voice for English, Chinese, or macOS 'say' voices
- Adjust speech rate for clearer or faster playback
- Increase or decrease TTS queue depth and stale TTL to match load
- Tune generation or playback timeouts to accommodate model warmup
- Modify notification rate limits, circuit breaker, or prompt throttling
- Update audit log retention or session picker limits
Best practices
- Always read the current mise.toml before making changes to avoid race conditions
- Validate numeric values against documented ranges (e.g., TTS_SPEED 0.5–2.0)
- Make minimal, single-purpose edits and restart the bot only when needed
- Use versioned commits or a short change log entry for each configuration change
- Test changes in a low-traffic window and verify by checking logs or feature behavior
Example use cases
- Switch the English TTS voice to a different macOS 'say' voice for better clarity
- Lower TTS_MAX_QUEUE_DEPTH to prevent large backlogs during spikes
- Increase TTS_GENERATE_TIMEOUT_MS during model warmup to avoid early failures
- Enable or disable the TTS signal sound by setting TTS_SIGNAL_SOUND path
- Raise NOTIFICATION_MIN_INTERVAL_MS to reduce notification spam during bursts
FAQ
Most changes require a bot restart to take effect, especially TTS, queue, and rate-limiting settings. Restart instructions are provided.
What range should I use for TTS_SPEED?
Use 0.5 to 2.0 as a safe range; values outside that range can make speech unintelligible or too slow.