From chappie
Check the Chappie audio daemon status — whether the binary is installed, the daemon is running, sounds are cached, and how the binary was obtained.
How this skill is triggered — by the user, by Claude, or both
Slash command
/chappie:statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Check the status of the Chappie audio daemon:
Check the status of the Chappie audio daemon:
Binary: Check whether the compiled daemon exists:
${CLAUDE_PLUGIN_ROOT}/target/release/chappie-daemon${CLAUDE_PLUGIN_ROOT}/target/release/chappie-daemon.exeBootstrap log: Show the last 10 lines of
~/.claude/.chappie_state/bootstrap.log if it exists — this reveals whether
the binary was downloaded as a prebuilt release or built from source, and
any failures.
Daemon process: Check if the daemon is running by reading
~/.claude/.chappie_state/daemon.pid and verifying the process.
Sound cache: List files in ~/.claude/sounds/ to verify all 6 sound
assets are downloaded (click1.wav through click4.wav, spacebar.wav,
alert.wav).
Signal state: Read ~/.claude/.chappie_state/signal to see the current
signal.
Daemon log: Show the last 20 lines of
~/.claude/.chappie_state/daemon.log if it exists.
Report findings concisely.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub mic-360/chappie --plugin chappie