Dispel Magic
Safely decommission active automations, agents, monitors, and integrations.
What This Skill Does
Use this spell when you need to cleanly shut down, disable, or remove active AI tooling — the reverse of Detect Magic.
In this grimoire, Dispel Magic is treated as a literal spell with a shipping-now delivery profile.
Canonical reference input: Dispel Magic (spell).
When To Use
- An active automation, cron job, webhook, or agent loop needs to be turned off cleanly.
- You are decommissioning a system and need to ensure no orphaned automations keep running.
- A monitor or integration is misfiring and needs to be disabled before it causes more damage.
Prerequisites
- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.
Procedure
- Restate the target, the success condition, and any no-touch boundaries before taking action.
- Identify the active magic to dispel — use Detect Magic first if the landscape is unclear.
- Assess dependencies: what else relies on this automation, and what breaks if it stops.
- Execute a graceful shutdown, preserving configuration for potential re-enable.
- Verify the automation is fully stopped and report any residual effects or orphaned state.
- Stop for explicit confirmation before taking a live action that changes access, triggers an alert, or touches a real system boundary.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- Confirmation that the target automation is fully stopped.
- A preserved copy of the configuration for potential re-enable.
- A list of downstream effects and any orphaned state that needs cleanup.
Pitfalls / Guardrails
- Treat the live action surface as real operational work, not decorative lore.
- Always confirm with the user before disabling production-connected automations.
- Prefer graceful shutdown over hard kill — preserve state for recovery.
- Never dispel something you do not understand. Use Detect Magic first if uncertain.
Verification
- Check that the result includes every deliverable promised above.
- Check that confirmed facts, assumptions, and inferences are visibly separated.
- Check that the exact live target, confirmation gate, and rollback or recovery path are explicit.
Example Invocation
/dispel-magic safely shut down this automation and confirm nothing is left running that shouldn't be
1---2name: dispel-magic-23description: Use this spell when you need to cleanly shut down, disable, or remove active AI tooling — the reverse of Detect Magic.4license: CC0-1.05---6# Dispel Magic7Safely decommission active automations, agents, monitors, and integrations.8## What This Skill Does9Use this spell when you need to cleanly shut down, disable, or remove active AI tooling — the reverse of Detect Magic.10In this grimoire, Dispel Magic is treated as a literal spell with a shipping-now delivery profile.11Canonical reference input: Dispel Magic (spell).12## When To Use1314- An active automation, cron job, webhook, or agent loop needs to be turned off cleanly.15- You are decommissioning a system and need to ensure no orphaned automations keep running.16- A monitor or integration is misfiring and needs to be disabled before it causes more damage.1718## Prerequisites1920- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.2122## Procedure23241. Restate the target, the success condition, and any no-touch boundaries before taking action.252. Identify the active magic to dispel — use Detect Magic first if the landscape is unclear.263. Assess dependencies: what else relies on this automation, and what breaks if it stops.274. Execute a graceful shutdown, preserving configuration for potential re-enable.285. Verify the automation is fully stopped and report any residual effects or orphaned state.296. Stop for explicit confirmation before taking a live action that changes access, triggers an alert, or touches a real system boundary.307. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.3132## Deliverables3334- Confirmation that the target automation is fully stopped.35- A preserved copy of the configuration for potential re-enable.36- A list of downstream effects and any orphaned state that needs cleanup.3738## Pitfalls / Guardrails3940- Treat the live action surface as real operational work, not decorative lore.41- Always confirm with the user before disabling production-connected automations.42- Prefer graceful shutdown over hard kill — preserve state for recovery.43- Never dispel something you do not understand. Use Detect Magic first if uncertain.4445## Verification4647- Check that the result includes every deliverable promised above.48- Check that confirmed facts, assumptions, and inferences are visibly separated.49- Check that the exact live target, confirmation gate, and rollback or recovery path are explicit.5051## Example Invocation52```text53/dispel-magic safely shut down this automation and confirm nothing is left running that shouldn't be54```
Hmbown