spellcraft

Composes multi-sigil workflows into auditable local spell artifacts with lifecycle discipline.

20|3|Updated May 14, 2026
One-click install
npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill spellcraft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spellcraft
Source: https://github.com/cyberAlchemyAI/Arcanum/tree/main/.claude/skills/spellcraft
Command: npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill spellcraft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spellcraft coordinates lifecycle-governed spell artifacts that compose multiple sigils into local workflows, enabling reusable, auditable spell-based automation.

Core Features & Use Cases

  • Design: create and adapt multi-sigil contracts that reference existing sigils and define phases, gates, handoffs, and observability.
  • Install/Run: install and localize library spells, adapt paths, validate structure, and establish observability for lifecycle governance.
  • Observe & Reflect: collect telemetry, drive iterative improvements, and preserve lifecycle ownership across runs.

Quick Start

Design a new spell by selecting compatible sigils and defining its lifecycle in your local repository.

Frequently Asked Questions about spellcraft

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

FAQPage Schema
How do I compose multi-step workflows with lifecycle gates and phase handoffs?

Multi-step workflow composition requires defining phases, gates, and handoffs within a local spell artifact, ensuring lifecycle governance and observability across the entire automated process. This approach coordinates multiple references into a single auditable contract.

What is lifecycle governance for local workflow orchestration?

Lifecycle governance for workflow orchestration enforces canonical IDs, aliases, and validation across local spells, ensuring that automated processes maintain phase discipline, observability, and reusable-harness readiness throughout execution.

How do I install and localize library spells for repository-local automation?

To install and localize library spells, you adapt paths, validate the spell structure, and establish observability to ensure the workflow integrates correctly with your repository-local automation environment.

Can I collect telemetry and drive iterative improvements from local spell workflows?

Yes, you can collect telemetry from local spell workflows to observe execution behavior, drive iterative improvements, and preserve lifecycle ownership across multiple runs for continuous automation refinement.

Does spellcraft work without external dependencies for workflow validation?

Yes, the skill operates with no external dependencies, relying on its internal engine to enforce canonical IDs, aliases, and structural validation for local spell artifacts within your repository.

When should I not use spell-based workflow orchestration?

You should avoid spell-based workflow orchestration for simple, single-step tasks that do not require phase design, gates, handoffs, or complex observability, as the lifecycle governance overhead provides no benefit.