How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/terrylica/cc-skills --skill custom-soundsBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
custom-sounds
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.
Enumerate/validate sounds via the TS core pushover_core.ts sounds.
env -u HTTPS_PROXY -u HTTP_PROXY bun "$(cc-plugin-root pushover-commander)/skills/_lib/pushover_core.ts" sounds list # name<TAB>label
env -u HTTPS_PROXY -u HTTP_PROXY bun "$(cc-plugin-root pushover-commander)/skills/_lib/pushover_core.ts" sounds has piano # exit 0 if present
env -u HTTPS_PROXY -u HTTP_PROXY bun "$(cc-plugin-root pushover-commander)/skills/_lib/pushover_core.ts" sounds resolve piano pianobar # echo first that existsNotes (verified 2026-05-30)
- Pushover silently accepts invalid sound names (no API error) — so always
resolve/hasbefore relying on a custom sound; a typo would just fall back to the user's default silently. pianois a custom sound on this account;pianobaris built-in. Custom sounds are per application token, so pass--app main|testto query the right app.
Post-Execution Reflection
After this skill completes, check before closing:
- Did the sound upload succeed AND become selectable in a real notification? A reported success with a missing sound means the validation is wrong.
- Were loudness/format constraints honoured? If the device rejected the sound, fix the sourcing pipeline.
Only update if the issue is real and reproducible — not speculative.

