Stats
Actions
Tags
From codetalker
Set the live-mode cadence (periodic | per_tool_call | per_cluster | significant_only | hybrid)
How this command is triggered — by the user, by Claude, or both
Slash command
/codetalker:cadence [periodic | per_tool_call | per_cluster | significant_only | hybrid]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
The user wants to change codetalker's live-mode cadence. `$ARGUMENTS` is the requested cadence (may be empty).
If `$ARGUMENTS` is empty:
1. Call `mcp__codetalker__tts_status`.
2. List the five cadences (periodic, per_tool_call, per_cluster, significant_only, hybrid) and ask which to use. Do not call set yet.
If `$ARGUMENTS` is one of those five:
- Call `mcp__codetalker__tts_set_cadence` with `{"cadence": "$ARGUMENTS"}` and reply with one short confirmation.
Otherwise:
- Reply with the five valid cadence names, no tool call.The user wants to change codetalker's live-mode cadence. $ARGUMENTS is the requested cadence (may be empty).
If $ARGUMENTS is empty:
mcp__codetalker__tts_status.If $ARGUMENTS is one of those five:
mcp__codetalker__tts_set_cadence with {"cadence": "$ARGUMENTS"} and reply with one short confirmation.Otherwise:
npx claudepluginhub opencircuitdev/codetalker --plugin codetalker