Magic Mouth
Bind a message to a trigger so the system speaks exactly when it should.
Overview
Magic Mouth is interpreted here as a metaphorical spell with a shipping-now execution model.
Canonical source: Magic Mouth (spell)
Provider target: OpenClaw
When To Use
- Use this spell when the user describes an event-driven message automation: a specific trigger condition (X) should cause a specific message or notification (Y) to be sent without manual intervention.
- Look for these patterns in the request:
- "When [condition], send/post/notify [message/recipient]"
- "Set up an autoresponder for [scenario]"
- "Create an alert rule for [metric/event]"
- "Design a webhook handler that posts to [channel] when [event]"
- Mentions of triggers, fire conditions, suppression rules, rate limits, or escalation stages
- Explicit no-fire cases ("don't fire if...", "suppress duplicates for...", "only once per...")
Workflow
- Extract the trigger: Identify the exact condition that fires the message (metric threshold, event type, time window, keyword match). Note any compound conditions or timing delays ("wait 5 minutes before firing").
- Specify the payload: List every variable in the message (who, what, where, severity, links). Write the response template with placeholders.
- Define boundaries: Document no-fire cases, rate limits, suppression windows, and escalation stages. Explicitly state what happens on repeated triggers.
- Return the spec: Produce a trigger-response specification with test cases covering: nominal fire, no-fire, repeated-trigger suppression, and escalation progression. If Slack or a messaging API is available, include the concrete API call or workflow configuration.
Deliverables
- A trigger-response specification or message template.
- Example payloads covering nominal and edge-case inputs.
- Notes on rate limits, suppression, escalation, and logging.
Guardrails
- Do not automate messages requiring human judgment, empathy, or legal review
- Protect against loops, spam, and easily-spoofed trigger conditions
- Always include a suppression mechanism for repeated triggers
Default Invocation
Use $magic-mouth to turn this trigger into a reliable automated response and show me the exact fire conditions.
1---2name: magic-mouth3description: Magic Mouth is trigger → message. The entire craft is specifying the trigger boundary, the message payload, and the suppression/escalation rules. It is NOT: - One-time messages: "Send a Slack message now saying X" (no trigger, no automation) - Full chatbots: "Build a conversational AI that understands context and handles open-ended questions" (requires NLU, dialogue management) - Monitoring dashboards: "Set up Grafana with real-time graphs and trend analysis" (visualization, not message routing) - Silent traps/wards: "Revert changes silently and log who tried" (defensive code manipulation, not messaging) - Encryption: "Encrypt a message so only the recipient can read it" (cryptography, not event-driven delivery) - Multimedia presentations: "Play a 20-slide deck with animations and narration" (media playback, not conditional messaging)4---56# Magic Mouth78Bind a message to a trigger so the system speaks exactly when it should.910## Overview1112Magic Mouth is interpreted here as a metaphorical spell with a shipping-now execution model.1314Canonical source: Magic Mouth (spell)1516Provider target: OpenClaw1718## When To Use1920- Use this spell when the user describes an event-driven message automation: a specific trigger condition (X) should cause a specific message or notification (Y) to be sent without manual intervention.21- Look for these patterns in the request:22- "When [condition], send/post/notify [message/recipient]"23- "Set up an autoresponder for [scenario]"24- "Create an alert rule for [metric/event]"25- "Design a webhook handler that posts to [channel] when [event]"26- Mentions of triggers, fire conditions, suppression rules, rate limits, or escalation stages27- Explicit no-fire cases ("don't fire if...", "suppress duplicates for...", "only once per...")2829## Workflow30311. Extract the trigger: Identify the exact condition that fires the message (metric threshold, event type, time window, keyword match). Note any compound conditions or timing delays ("wait 5 minutes before firing").322. Specify the payload: List every variable in the message (who, what, where, severity, links). Write the response template with placeholders.333. Define boundaries: Document no-fire cases, rate limits, suppression windows, and escalation stages. Explicitly state what happens on repeated triggers.344. Return the spec: Produce a trigger-response specification with test cases covering: nominal fire, no-fire, repeated-trigger suppression, and escalation progression. If Slack or a messaging API is available, include the concrete API call or workflow configuration.3536## Deliverables3738- A trigger-response specification or message template.39- Example payloads covering nominal and edge-case inputs.40- Notes on rate limits, suppression, escalation, and logging.4142## Guardrails4344- Do not automate messages requiring human judgment, empathy, or legal review45- Protect against loops, spam, and easily-spoofed trigger conditions46- Always include a suppression mechanism for repeated triggers4748## Default Invocation4950Use $magic-mouth to turn this trigger into a reliable automated response and show me the exact fire conditions.51
Hmbown