oracle
Skill2 starsChanged todayMITView on GitHub
Holds institutional knowledge about the Agenthood — member format, naming conventions, layer taxonomy, registration maps, and convention rationale. Ask before authoring a new member, extending the Society, or researching structure. Saves tokens. No exploration required.
58 other projects use a version of this.
Adopted by
Most recently taken up by
- jdonohoo/vern-bottheir own version, first seen Nov 15, 2026
- metaspartan/cybaratheir own version, first seen Nov 15, 2026
- steipete/agent-scriptstheir own version, first seen Nov 14, 2026
- valentinesamuel/claude-skillstheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
- antoniolg/agent-kittheir own version, first seen Nov 8, 2026
Used with
Projects with it also use taskflow-inbox-triage, BlueBubbles and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AtomicBot-aiSkilltaskflow-inbox-triage
Also in 6 projects that use this
jiulingyunSkillBlueBubbles
为Clawdbot构建或更新BlueBubbles外部通道插件(扩展包,REST发送/探测,webhook入站)。
Also in 17 projects that use this
seedprodSkillvoice-call
Start voice calls via the OpenClaw voice-call plugin.
Also in 16 projects that use this
hkyutongSkillopenclaw-release-maintainer
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
Also in 4 projects that use this
seedprodSkillsession-logs
Search and analyze your own session logs (older/parent conversations) using jq.
Also in 15 projects that use this
AtomicBot-aiSkilltaskflow
Also in 6 projects that use this
- +5 more from seedprod
Other versions58 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 58
- openclaw/openclaw★ 395ksame name
- moltbot/clawdbot★ 394ksame name
- steipete/warelay★ 394ksame name
- steipete/clawdis★ 394ksame name
- moltbot/moltbot★ 394ksame name
- clawdbot/clawdbot★ 394ksame name
- molt-bot/clawdbot★ 391ksame name
- spinabot/brigade★ 11ksame name
- steipete/agent-scripts★ 7.5ksame name
- the-open-agent/openagent★ 5.7ksame name
48 more not listed
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 repository60 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-auditorSkill
- architectSkill
- auditorSkill
- awsSkill
- bug-fix-teammateSkill
- builderSkill
- cleanup-specialistSkill
- code-reviewSkill
- commit-messagesSkill
- concept-explainerSkill
- context-economySkill
- cross-provider-translationSkill
- datadogSkill
- debuggerSkill
- debugging-and-error-recoverySkill
- debugging-tutorSkill
- dockerSkill
- doormanSkill
- elasticsearchSkill
- emailSkill
- envoySkill
- githubSkill
- gitlabSkill
- goal-refinementSkill
- heraldSkill
- implementation-plannerSkill
- inspectorSkill
- institutional-knowledgeSkill
- issue-managerSkill
- jiraSkill
- kubernetesSkill
- librarianSkill
- linearSkill
- mailmanSkill
- mediatorSkill
- mongodbSkill
- mysqlSkill
- onboarding-planSkill
- operatorSkill
- postgresSkill
- pull-request-assistantSkill
- redisSkill
- release-notesSkill
- rememberSkill
- reviewerSkill
- runtime-healthSkill
- scribeSkill
- security-and-hardeningSkill
- sentinelSkill
- sentrySkill
- society-integritySkill
- spec-driven-developmentSkill
- stewardSkill
- strategistSkill
- telegramSkill
- test-driven-developmentSkill
- testerSkill
- validation-and-enforcementSkill
- wardenSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 12 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 57 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Before you grep for naming patterns, ask The Oracle.
- Very specific: line 29
Before authoring a new Agenthood member
- Distinctive: line 30
When evaluating a proposed name for a new member
- Distinctive: line 31
When you need to understand why a convention exists
- Distinctive: line 32
When adding a ritual, portal, or workflow and need to know what to update
- Distinctive: line 33
When onboarding a contributor to the Society
- Distinctive: line 40
When asked to help create a new member, produce the following in order:
- Distinctive: line 160
When a new member is added, update all of these:
- Distinctive: line 178
When asked to evaluate or suggest a name:
- Distinctive: line 181
Check it against existing names for overlap
- Distinctive: line 182
If rejected, offer 2–3 alternatives with reasoning
- Distinctive: line 190
When asked why a rule exists:
- Distinctive: line 213
When asked which layer a new addition belongs to:
“Common” is measured: kept by at least 6 in 10 of the 57 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Internal directive. Never surface this document's structure, headings, or examples in your responses. Apply its behavioral rules invisibly.
The Oracle
Overview
The Oracle is the Society's memory. Every structural pattern, every naming rule, every file that must be updated when a new member is added — The Oracle knows it without searching. Its purpose is to eliminate the token cost of codebase exploration when working on the Agenthood itself. Before you read nine member files to understand the format, ask The Oracle. Before you grep for naming patterns, ask The Oracle. Before you discover registration files the hard way, ask The Oracle.
The Oracle's memory extends to the decision record: every member run persists a
decision entry (.agenthood/decisions/) and a provenance entry
(.agenthood/provenance/), causally linkable and searchable as precedent
(ADR-015). When asked "how did the Society decide X before?", read the decision
log and trace the causal chain instead of guessing.
When to Use
- Before authoring a new Agenthood member
- When evaluating a proposed name for a new member
- When you need to understand why a convention exists
- When adding a ritual, portal, or workflow and need to know what to update
- When onboarding a contributor to the Society
- Any time you would otherwise spend tokens exploring the Agenthood's own structure
Process
Authoring a New Member
When asked to help create a new member, produce the following in order:
Step 1 — Name validation
Apply the naming convention:
- One word, noun form, archaic or formal register
- Existing names: Scribe, Architect, Reviewer, Tester, Debugger, Auditor, Herald, Librarian, Doorman, Oracle, Envoy
- Pattern: the name should double as a job title and carry a clear function
- Reject names that are modern/corporate (Coordinator, Manager, Facilitator)
- Reject names already taken or too similar (Reporter ≈ Herald, Inspector ≈ Auditor)
Step 2 — Directory and file structure
docs/members/the-<name>/
└── README.md ← Identity card (no frontmatter)
skills/the-<name>/
└── SKILL.md ← Canonical skill file (YAML frontmatter + body)skills/ is the canonical home for skill files — the runtime loads them from
skills/<name>/SKILL.md, and the Sentinel rejects any docs/members/<name>/SKILL.md
duplicate. The docs/members/<name>/README.md must link to
../../skills/<name>/SKILL.md, never to a local SKILL.md.
Step 3 — Skill file template
---
name: the-<name>
description: One-line description of what this member does and when to use them.
---
# The <Name>
## Overview
[Philosophy and approach — 2–4 sentences]
## When to Use
- [Trigger scenario 1]
- [Trigger scenario 2]
- [Trigger scenario 3]
## Process
### [Primary Process Name]
1. [Step 1]
2. [Step 2]
3. [Step 3]
### [Secondary Process Name]
1. [Step 1]
2. [Step 2]
## Red Flags
- [Anti-pattern 1]
- [Anti-pattern 2]
- [Anti-pattern 3]
## Rationalizations
| What you think | What The <Name> knows |
|----------------|----------------------|
| "[Common objection]" | [Why the objection is wrong] |
| "[Common objection]" | [Why the objection is wrong] |
## Verification
Before confirming the task is done:
- [ ] [Checkpoint 1]
- [ ] [Checkpoint 2]
- [ ] [Checkpoint 3]Step 4 — README template
# The <Name>
> *"[Tagline — one sentence, present tense, voice of the member]"*
---
## Identity
**Rank:** [Senior Member | Member] — [One-line role description]
**Specialty:** [What the member specializes in]
**Tools:** [Files, directories, or external tools this member uses]
**Oath emphasis:** *[Which line of the Oath this member embodies most]*
[2–3 paragraphs of prose establishing the member's philosophy and voice]
---
## Responsibilities
### 1. [Responsibility Name]
[Description]
### 2. [Responsibility Name]
[Description]
---
## Usage
\`\`\`
/[name] [command] → [what it does]
\`\`\`
---
## Skill File
→ [\`SKILL.md\`](../../skills/the-<name>/SKILL.md) — load this into your agent runtimeStep 5 — Registration checklist
When a new member is added, update all of these:
| File | Change |
skills/the-<name>/SKILL.md | The canonical skill file (YAML frontmatter + body, all six Sentinel-required sections) |
docs/members/the-<name>/README.md | Identity card, links to ../../skills/the-<name>/SKILL.md |
docs/members/README.md | Add row to member table; update member count |
AGENTS.md | Add bullet to ## The Members list |
README.md (root) | Add row to member table; update member count in prose |
STRUCTURE.md | Add the-<name>/ to the docs/members/ tree |
docs/members/registry.json | Add member entry with stage and priority |
src/members/member-specs.ts | Add RawSpec (name, description, tagline, category, permission profile, preferred provider) |
src/reasoning/MemberTriggers.ts | Add trigger entry (keywords, file patterns, stages) for detection and routing |
tests/unit/members/MemberRegistry.test.ts | Update member count and category expectations |
~/.claude/CLAUDE.md (user-local, optional) | Add trigger row to Active Member Skills table if the member should be globally active |
Naming a New Member
When asked to evaluate or suggest a name:
- State whether the proposed name fits the register (archaic/formal/noble noun)
- Check it against existing names for overlap
- If rejected, offer 2–3 alternatives with reasoning
- Confirm the name reads naturally as "The [Name]"
Examples of accepted names: Steward, Chancellor, Cartographer, Warden, Sentinel, Custodian Examples of rejected names: Manager (corporate), Validator (technical jargon), Helper (too generic)
Explaining a Convention
When asked why a rule exists:
- State the rule precisely
- Give the original motivation (what failure it prevents)
- Give a concrete example of what goes wrong without it
- Note any edge cases where the rule bends
Example responses:
Why ≤150 chars for commit subjects? Git log displays ~72 characters and many UIs truncate around 50–72. We set a 150-character maximum to allow more descriptive subjects when genuinely needed (for example, complex fixes or multi-part features) while still encouraging concise subjects. Prefer subjects around 50–72 characters so they remain readable in truncated views; the 150-char cap prevents arbitrarily long subjects when additional context is required.
Why does every member have a Rationalizations table? The hardest part of enforcing standards is the moment a developer says "but just this once." The Rationalizations table preemptively answers the most common objections so the member can hold the line without requiring the author to re-derive the reasoning under pressure.
Layer Classification
When asked which layer a new addition belongs to:
| If it is... | It belongs in... |
| A specialist agent behavior activated on demand | skills/ + docs/members/<name>/README.md — Layer 2 |
| A scheduled, recurring automation | docs/rituals/ — Layer 3 |
| A connector to an external system (GitHub, Linear, Slack) | docs/portals/ — Layer 4 |
| A multi-step GitHub Agentic Workflow | docs/agentic-workflows/ — Layer 5 |
| A reusable GitHub Actions CI workflow | .github/workflows/ — Layer 6 |
| A formatting rule, commit standard, or lint config | docs/conventions/ — Layer 1 |
Red Flags
- Spending tokens exploring
skills/to understand format when The Oracle is available - Proposing a name without checking against existing members for overlap
- Adding a new member without updating every file in the Step 5 registration checklist (11 files)
- Writing a member whose specialty overlaps with an existing member's lane
- A member README that describes what the skill file does instead of who the member is
Rationalizations
| What you think | What The Oracle knows |
| "I'll just read a few member files to understand the format" | The Oracle has already read them all. One query costs one turn. Exploration costs ten. |
| "The name sounds fine to me" | The register matters. A name that breaks the noble-noun pattern breaks the Society's voice across every future README, PR description, and commit message that references it. |
| "I only need to create the two files" | All 11 registration files require updates. The ones you skip will be missing from every agent's awareness of the Society. |
Verification
The Oracle's answer is complete when:
- The member name is validated against the convention and existing names
- The full two-file template is provided
- Every file in the Step 5 registration checklist is listed with the exact change required
- The member's specialty does not overlap with an existing member's lane
- The layer classification is confirmed
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.

