Verified:GitHub

orchestrate

Name: orchestrate
Availability: InStock
Author: cyberAlchemyAI

Route repository tasks through installed Arcanum capabilities while preserving dispatch-spec and observability boundaries.

20|3|Updated May 14, 2026

Search Tags:#workflow #observability #orchestrate #spell #sigil #arcanum

Ready to run

npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill orchestrate-cyberalchemyai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orchestrate
Source: https://github.com/cyberAlchemyAI/Arcanum/tree/main/.claude/skills/orchestrate
Command: npx skills add https://github.com/cyberAlchemyAI/Arcanum --skill orchestrate-cyberalchemyai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables routing repository tasks through installed Arcanum capabilities, providing governance, observability, and boundary-preserving orchestration across sigils and spells.

Core Features & Use Cases

Orchestrates task routing through installed Arcanum capabilities (sigils and spells) while maintaining dispatch-spec, task-session, and observability boundaries.
Supports end-to-end governance for complex repository workflows, enabling safe collaboration, traceability, and modular extension.
Use Case: Coordinate a multi-capability run that processes a repository task from initiation to validated artifact with full observability.

Quick Start

Provide a repository task and let Orchestrate route it through the installed Arcanum capabilities while preserving boundaries.

Frequently Asked Questions about orchestrate

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

FAQPage Schema

How do I route repository tasks through installed capabilities while preserving observability boundaries?▼

Workflow orchestration routes repository tasks through installed capabilities while preserving dispatch-spec, task-session, and observability boundaries for traceable artifact generation across sigils and spells.

What is the best way to coordinate multi-capability repository workflows with governance?▼

Multi-capability coordination applies governance to complex repository workflows by guiding classification, execution, validation, and handoff stages to ensure safe collaboration and modular extension.

How does orchestration handle task routing from initiation to validated artifact?▼

Task routing processes repository work from initiation through validated artifact by applying a defined frontmatter, objective section, and process block that govern classification and execution.

Do I need a defined frontmatter structure to use repository workflow orchestration?▼

Yes, workflow orchestration requires a defined frontmatter including name, description, runtime, and surface_kind, plus an objective section and process block to guide execution accurately.

Can I use workflow orchestration for complex repository tasks requiring traceable artifacts?▼

Yes, workflow orchestration supports complex repository workflows requiring governance, multi-capability coordination, and traceable artifacts across sigils and spells for end-to-end observability.

When should I avoid using orchestration for repository task routing?▼

Workflow orchestration should be avoided for simple repository tasks that do not require multi-capability coordination, governance boundaries, or traceable artifacts across sigils and spells.