summon
Autonomous orchestrator processing manifest work items through the development lifecycle with budget tracking
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/athola/nm-egregore-summonNight Market Skill — ported from claude-night-market/egregore. For the full experience with agents, hooks, and commands, install the Claude Code plugin.
Table of Contents
- Overview
- When To Use
- When NOT To Use
- Orchestration Loop
- Pipeline-to-Skill Mapping
- Context Overflow Protocol
- Token Budget Protocol
- Failure Handling
- Module Reference
Summon
Overview
Summon is the egregore orchestration loop.
It reads the manifest (.egregore/manifest.json), selects
the next active work item, maps the current pipeline step to
a specialist skill, and invokes that skill.
After each step it advances the pipeline, checks context and
token budgets, and repeats until all items are completed or
the budget is exhausted.
The orchestrator never re-implements phase logic.
Each pipeline step delegates to an existing skill via
Skill() calls.
Summon only manages state transitions, retries, and budget
guards.
When To Use
- Processing one or more work items through the full intake-build-quality-ship pipeline.
- Resuming an interrupted egregore session (manifest already exists with active items).
- Running autonomously under a watchdog that relaunches on exit.
When NOT To Use
- Running a single skill in isolation (call the skill directly instead).
- Exploratory work where the pipeline does not apply.
- When human review is needed before every step (use manual skill invocations).
Launching the Orchestrator
Always launch the orchestrator agent in the FOREGROUND.
Do not use run_in_background: true. The main session
becomes the egregore -- it blocks on the orchestrator agent
until the egregore finishes or is dismissed.
Agent(
subagent_type: "egregore:orchestrator",
prompt: "<context about work items and current state>",
run_in_background: false // Required
)
If you launch the orchestrator in the background, the main session will have nothing to do and will stop. This defeats the entire purpose of the egregore. The stop hook cannot prevent this because background agents are detached.
Manifest Mode
Before launching the orchestrator, ensure the manifest has the correct run mode:
- Default (no
--boundedflag): set"indefinite": truein the manifest. The egregore will scan for new work after completing all items and run until dismissed. - With
--boundedflag: set"mode": "bounded"in the manifest. The egregore stops after all items are completed or failed.
If the manifest already exists and has "mode": "bounded"
but the user did NOT pass --bounded, update the manifest
to "indefinite": true before launching.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-athola-nm-egregore-summon": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
extract
Analyze a codebase and build a knowledge base of business logic, architecture, data flow, and engineering patterns. The foundation for gauntlet challenges and agent integration
discourse
>- Scan community discussion channels (HN, Lobsters, Reddit, tech blogs) for experience reports and opinions on a topic
synthesize
>- Merge, deduplicate, rank, and format research findings from multiple channels into a coherent report. Use after research agents return their results
workflow-monitor
Detect workflow failures and inefficient patterns, then create GitHub issues for improvement via /fix-workflow
architecture-paradigm-hexagonal
Hexagonal (Ports and Adapters) architecture isolating domain logic from infrastructure