hmbown/magic-mouth
generated/openclaw/magic-mouth/SKILL.md
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)
$ install --global
skillsauthnpx skillsauth add hmbown/wizards-of-the-ghosts magic-mouthInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:37 PM1.6s1 file scanned
SKILL.md
- name:
- magic-mouth
- description:
- 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)\n- Full chatbots: \"Build a conversational AI that understands context and handles open-ended questions\" (requires NLU, dialogue management)\n- Monitoring dashboards: \"Set up Grafana with real-time graphs and trend analysis\" (visualization, not message routing)\n- Silent traps/wards: \"Revert changes silently and log who tried\" (defensive code manipulation, not messaging)\n- Encryption: \"Encrypt a message so only the recipient can read it\" (cryptography, not event-driven delivery)\n- Multimedia presentations: \"Play a 20-slide deck with animations and narration\" (media playback, not conditional messaging)
- user-invocable:
- true
- primaryEnv:
- SLACK_TOKEN
- emoji:
- 🗣️
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.
Related Skills
hmbown/zone-of-truth
testing
VerifiedTrustedCommunity
Enter a mode where every assertion is backed by evidence, confidence is calibrated, speculation is flagged, and hallucination is actively resisted.
55SKILL.mdUpdated Apr 5, 2026
hmbown/vicious-mockery
development
VerifiedTrustedCommunity
The bard's cantrip that deals psychic damage through insults. In practice this is adversarial review — the art of finding and articulating exactly what is wrong with something in a way that is impossible to ignore. Unlike polite feedback that gets filed and forgotten, vicious mockery lands. It is the red-team report that makes the PM cancel the launch, the code review that makes the author delete the PR, the roast that makes the founder pivot. The damage is the point.
55SKILL.mdUpdated Apr 5, 2026
hmbown/unseen-servant
tools
VerifiedTrustedCommunity
Use this spell when you need a tireless helper that organizes, tidies, triages, and maintains without requiring your constant attention.
55SKILL.mdUpdated Apr 5, 2026
hmbown/true-strike
testing
VerifiedTrustedCommunity
Use this spell for preflight certainty: dry runs, validation checks, dependency verification, and rehearsals that make the next deploy, query, or command much more likely to succeed. It trades a little time up front for fewer blind swings and fewer expensive misses.
55SKILL.mdUpdated Apr 5, 2026