mordenkainen-s-sword

Automate a persistent daemon pattern with lifecycle hooks and graceful cancellation.

105|13|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill mordenkainen-s-sword
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mordenkainen-s-sword
Source: https://github.com/Hmbown/Wizards-of-the-Ghosts/tree/main/generated/hermes/actions-access-and-automation/mordenkainen-s-sword
Command: npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill mordenkainen-s-sword

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a metaphorical but practical pattern for running a single-purpose, long-lived background task as a daemon, watcher, or scheduled worker. It helps ensure lifecycle control, observability, and safe cancellation for automated, repetitive actions.

Core Features & Use Cases

  • Narrow mandate: Runs a single, well-defined action without granting broad system access.
  • Lifecycle controls: Provides start, monitor, and stop hooks with safe cancellation.
  • Observability: Includes basic reporting of state and progress for ongoing tasks.
  • Use Case: Deploy as a daemon that periodically processes a queue item or monitors a resource.

Quick Start

Run the daemon spell to instantiate a persistent worker that repeatedly executes a single task until stopped.

Frequently Asked Questions about mordenkainen-s-sword

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a background task as a daemon with safe startup and graceful cancellation?

To run a background task as a daemon with graceful cancellation, you can use an automated portable pattern that implements runnable lifecycle hooks for safe startup, reliable repetition, and clear failure handling.

What is the best way to schedule a long-running worker with lifecycle controls and observability?

Scheduling a long-running worker with observability requires a pattern that provides start, monitor, and stop hooks, ensuring basic reporting of state and progress for ongoing automated repetitive tasks.

Can I use a daemon pattern to monitor a resource without granting broad system access?

Yes, you can deploy a daemon pattern with a narrow mandate to monitor a resource, ensuring it runs a single, well-defined action repeatedly without granting broad system access.

Does background task automation support idempotent execution for scheduled workers?

Background task automation supports idempotent execution, applying a portable daemon pattern to run single-purpose schedulers and watchers that require reliable repetition and safe cancellation.

When should I use a narrow-mandate daemon for task scheduling instead of broader automation?

Use a narrow-mandate daemon for task scheduling when you need a single-purpose, long-lived background process with basic observability and safe lifecycle controls rather than broad, complex system access.