How do I install the Custom Sounds skill?

Run npx skillmds add terrylica/custom-sounds in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Custom Sounds safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Custom Sounds?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Custom Sounds free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Custom Sounds?

terrylica (@terrylica) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Custom Sounds by terrylica — Agent Skill

Name: Custom Sounds
Rating: 4.666666666666667 (3 reviews)
Author: terrylica

Custom Sounds

List or validate Pushover notification sounds (built-in plus this account's custom uploaded sounds) via the /1/sounds.json API. Use when choosing a notification sound, checking whether a custom sound exists, or picking a safe fallback before sending. TRIGGERS - pushover sounds, list sounds, validate sound, custom sound, which sounds.

terrylica 45ccc7a 1.9 KB Updated Sep 9, 2026

File contents

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 exists

Notes (verified 2026-05-30)

Pushover silently accepts invalid sound names (no API error) — so always resolve/has before relying on a custom sound; a typo would just fall back to the user's default silently.
piano is a custom sound on this account; pianobar is built-in. Custom sounds are per application token, so pass --app main|test to 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.

---name: custom-soundsdescription: List or validate Pushover notification sounds (built-in plus this account's custom uploaded sounds) via the /1/sounds.json API. Use when choosing a notification sound, checking whether a custom sound exists, or picking a safe fallback before sending. TRIGGERS - pushover sounds, list sounds, validate sound, custom sound, which sounds.--- # 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`. ```bash 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 exists ``` ## Notes (verified 2026-05-30) - Pushover **silently accepts invalid sound names** (no API error) — so always `resolve`/`has` before relying on a custom sound; a typo would just fall back to the user's default silently. - `piano` is a **custom** sound on this account; `pianobar` is built-in. Custom sounds are per application token, so pass `--app main|test` to query the right app. ## Post-Execution Reflection After this skill completes, check before closing: 1. **Did the sound upload succeed AND become selectable in a real notification?** A reported success with a missing sound means the validation is wrong. 2. **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.

Frequently asked questions