summon
Skill293 starsChanged 10 days agoMITView on GitHub
Reuse, design, and launch Egregore spirits. Review available recipes and current host permissions, then start authorized on-demand work or design a scheduled process for an available scheduler.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Nafjan/summontheir own version, first seen Nov 15, 2026
- MIMIFY/skill_everyonetheir own version, first seen Apr 10, 2026
- secondorderai/summon-skilltheir own version, first seen Apr 8, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- MIMIFY/skill_everyone★ 59same name
- Nafjan/summon★ 4same name
- secondorderai/summon-skill★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activitySkill
- announceSkill
- archiveSkill
- branchSkill
- checkupSkill
- commitSkill
- contributeSkill
- create-skillSkill
- dark-modeSkill
- dashboardSkill
- deep-reflectSkill
- delete-userSkill
- emissarySkill
- envSkill
- handoffSkill
- harvestSkill
- ingest-corpusSkill
- ingest-notionSkill
- ingestSkill
- ingest-user-interviewSkill
- inviteSkill
- issueSkill
- meetingSkill
- meSkill
- noteSkill
- notion-connectSkill
- onboardingSkill
- prSkill
- pullSkill
- pushSkill
- questSkill
- recordsSkill
- reflectSkill
- review-prSkill
- saveSkill
- slack-connectSkill
- sync-reposSkill
- telegram-connectSkill
- telemetrySkill
- testSkill
- the-spiralSkill
- tui-designSkill
- tutorialSkill
- updateSkill
- viewSkill
- visual-explainSkill
- wrapSkill
- preview-designSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. About 0 are common, 14 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Use for “summon,” “I want a spirit that,” reusing a spirit recipe, or designing recurring work, monitoring, and condition-triggered work.
- Distinctive: line 22
Use the conversation first.
- Distinctive: line 32
Check the tools actually exposed by the current host:
- Very specific: line 34
If discover_capabilities is available, use it to find visible recipes and their limitations.
- Very specific: line 36
If review_spirit_recipe is available, review the selected recipe.
- Distinctive: line 40
If these tools are absent, continue with design using available evidence.
- Distinctive: line 41
Do not invent a recipe review, host binding, installed capability, or launch.
- Very specific: line 43
Never infer availability from this skill's examples.
- Very specific: line 54
Call delegate_work with recipe_id, the returned expected_binding_digest, and the user's task.
- Distinctive: line 78
Use the review-only form to inspect a recipe.
- Distinctive: line 81
If launch tools are unavailable, report that no work was started.
- Distinctive: line 112
Keep this schema exact. No credentials, actor grants, machine paths, current status, or ad hoc scheduler fields belong in it.
- Distinctive: line 131
Keep a scheduled design separate from the strict on-demand v2 JSON.
- Distinctive: line 135
When creating a schedule, retain the real scheduler ID, scope, trigger, expiry/restart behavior, and cancellation instructions returned by …
- Distinctive: line 137
Verify actual registration before saying it is running.
- Distinctive: line 147
Use owned work history where exposed and Runtime retrieval for canonical records.
- Distinctive: line 154
When a run reveals a reusable improvement, retain a candidate with source evidence, its limitation, and a proposed evaluation.
- Very specific: line 164
Use actual job or scheduler handles for inspect/cancel/resume actions.
- Distinctive: line 165
Do not claim a design is active from its file name or a legacy status field.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Summon an Egregore spirit
A spirit is an Egregore agent with a durable purpose and execution history. Begin with what the user wants done and reuse an available recipe when it fits. A recipe is a portable design; an admitted run and a running schedule each need their own host receipt. Saving a design does not launch a spirit.
When to invoke
Use for “summon,” “I want a spirit that,” reusing a spirit recipe, or designing recurring work, monitoring, and condition-triggered work. Ordinary one-off work needs no new recipe unless the user wants a reusable spirit. A fully specified schedule can go straight to an available scheduler.
1. Restore intent and discover what exists
Use the conversation first. Do not ask again for purpose, constraints, or authorization already supplied. Ask only for missing information that affects the next action; use structured questions when available.
For organizational context, follow the Runtime retrieval contract: reuse
supplied evidence, otherwise use bash bin/search.sh find and open. Show the
required retrieval beat. Do not scan raw memory or query relationships merely
because the request concerns a spirit. Existing .spirits/ designs are project
files and can be inspected normally.
Check the tools actually exposed by the current host:
- If
discover_capabilitiesis available, use it to find visible recipes and their limitations. A catalog entry alone does not establish readiness. - If
review_spirit_recipeis available, review the selected recipe. Show its purpose, profile, effective tools, on-demand trigger, and admission result. Required capability IDs describe workflow features; they do not limit the profile to only those tools. A review digest grants no permissions. - If these tools are absent, continue with design using available evidence. Do not invent a recipe review, host binding, installed capability, or launch.
Never infer availability from this skill's examples. Source recipes such as
egregore/researcher and egregore/pm must still pass the current host review.
Local candidates are not reviewed releases or evidence of deployment adoption.
2. Reuse a recipe for authorized work
With the host tools available, the sequence is:
review_spirit_recipe({"recipe_id":"<selected ID>"}).- Present the current scope and effective permissions. Proceed if the user's existing request authorizes the concrete task and admission is allowed.
- Call
delegate_workwithrecipe_id, the returnedexpected_binding_digest, and the user'stask. Includesource_message_idsonly for selected messages in the authorized direct conversation. Do not also supplyprofileor construct a binding yourself. - Report the returned job or clarification and how to inspect or cancel it.
Recipe discussion or a deferred source link is not a request to start work. Preserve the user's original constraints, source selection, and “do not implement” limits. On a stale review, re-review; changed permissions or scope need to be made visible before continuing. A denied admission is not a reason to bypass the recipe through a broader profile.
The Telegram host also supports direct commands in an authorized DM:
/summon <recipe ID> Review only
/summon <recipe ID> <task> Request one runThe task form obtains a fresh host review and admits against that binding. It uses the same queue, current actor grants, source clarification, and result delivery as other spirit work. It creates no schedule. Group commands do not expose recipe details or start recipe work. This is an explicit command form: every trailing task is submitted as work. Use the review-only form to inspect a recipe; use ordinary conversation to discuss a future task or retain a link without starting a run.
If launch tools are unavailable, report that no work was started. Say a design was saved only after actually writing it. Do not present a source file or a model promise as an active spirit.
3. Design a new reusable spirit when needed
Resolve the consequential unknowns: purpose and source scope; actions and boundaries; outcome evidence; budget and stop conditions; delivery; and whether the trigger is on-demand, scheduled, or event-based. Stop questioning when these are concrete. Reuse known capabilities instead of creating a parallel implementation because a spirit has a new name.
For a Pi Durable on-demand design, write .spirits/{name}.json using the
portable v2 shape. This example is illustrative, not an installed recipe:
{
"schema": "egregore.spirit-recipe/v2",
"id": "example/researcher",
"purpose": "Investigate selected sources and retain evidence-backed findings",
"runtime": "pi-durable",
"capabilities": ["egregore/contextual-delegation", "egregore/task-outcome"],
"skills": [],
"trigger": {"kind": "on-demand"},
"outcome_contract": "egregore.task-outcome/v1",
"budget_policy_ref": "local/bounded-work",
"binding_ref": "local/researcher",
"delivery": {"kind": "request-origin"}
}Keep this schema exact. No credentials, actor grants, machine paths, current status, or ad hoc scheduler fields belong in it. References still need a host binding; saving this file does not install it into the host's selected catalog. Review the design with the user. Continue authorized preparation without an extra permission round; resolve any new consequential choice before acting.
Existing version: 1 designs remain readable as legacy-unknown. They do not
prove grants, outcome acceptance, generation binding, or current activity.
Preserve them and their history; draft a migration separately rather than
silently converting or starting them.
4. Scheduled and condition-triggered spirits
Pi Durable's current recipe admission supports on-demand work. Scheduling is a separate host capability. Use a native scheduler only when it is actually available and authorized in the session. Otherwise save a design describing the trigger, observed sources, action, budget, stop conditions, and delivery, and explicitly report that no schedule was created.
Keep a scheduled design separate from the strict on-demand v2 JSON. For a watcher, define an observable condition and its source; do not assume a relationship query or introduce polling without explaining the cadence.
When creating a schedule, retain the real scheduler ID, scope, trigger, expiry/restart behavior, and cancellation instructions returned by that host. Verify actual registration before saying it is running. Suspend/resume through the scheduler and report its receipt; editing a status field is insufficient.
5. Observe outcomes and accumulate improvements
Distinguish execution state, the spirit's outcome claim, verified acceptance, and delivery. A completed model run is not proof the task was fulfilled. Report evidence and unresolved requirements; ask a bounded question when a source or decision is missing. Do not require a speculative insight every run.
Use owned work history where exposed and Runtime retrieval for canonical
records. Local history does not require Connected services. Metadata-only
records are not transcripts or proof of subjective experience. Recording,
publication, and outgoing notifications each follow their own current policy;
this workflow does not enable them implicitly. Agent-authored external
notifications follow .claude/context/notification-consent.md.
When a run reveals a reusable improvement, retain a candidate with source evidence, its limitation, and a proposed evaluation. Reuse the existing library/contribution tools if available. Keep observation, proposed change, tested capability, release, and receiving-host adoption distinct. A success claim alone must not update other spirits or grant new permissions.
Managing existing spirits
Show designs from .spirits/, admitted work from the host's owned job surface,
and active schedules from the scheduler. Label missing or stale evidence.
Use actual job or scheduler handles for inspect/cancel/resume actions.
Do not claim a design is active from its file name or a legacy status field.
Emit the standard command telemetry when the project adapter is available:
bash bin/telemetry.sh emit "command" '{"command":"summon"}' 2>/dev/null &Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

