Creating a Member
A member is a SKILL.md file with a name, a description, and instructions a model can follow. This
guide takes you from nothing to a reviewed member in six steps. The reference contract: trust model,
versioning, registry names: lives in Third-Party Members; this page
is the walkthrough.
Everything below is copy-paste ready. The worked example builds The Translator, a member that turns
technical specifications into plain language.
1. Before you start
Read The Oath. It is one page and it sets the standard: a member does not flatter, it
does not guess, and it does not claim work it did not do.
Skim The Oracle. It is the member that writes members, and it holds the
naming rules and the section template this guide follows.
You need nothing else: no account, no build step. A SKILL.md file is the whole deliverable.
2. Name your member
- One word, noun form, formal register:
Scribe,Warden,Translator - It must read naturally as "The Name" and double as a job title
- Lowercase, hyphen-separated in the file and directory:
the-translator - Reject modern corporate words (
Coordinator,Facilitator) and generic ones (Helper) - Check it is not taken:
ls skills/, thennpx agenthood skillsto see what a project has installed
The name is the identity. If it changes later, every link and every reference breaks.
3. Create the file
skills/contrib/the-<name>/
└── SKILL.md
skills/contrib/ is the third-party home. Discovery walks it automatically, so there is no registry
file to edit. If you are adding a member to this repository rather than to your own project, useskills/the-<name>/ and follow the registration list in The Oracle.
The frontmatter is small and strict:
description is what the model sees when choosing a member. Front-load the trigger words, name both
what it does and when to use it, and keep it under about two sentences; it is paid for on every
request.
4. Write the six sections
Every member has the same shape. The Sentinel checks for it, and readers rely on it.
| Section | Answers |
|---|---|
## Overview | What this member is and the failure it prevents |
## When to Use | The concrete situations, and what it is not for |
## Process | The ordered steps, imperative and verifiable |
## Red Flags | What the member must stop and report |
## Rationalizations | The excuses it must refuse, with the counter |
## Verification | How to check the work before calling it done |
A complete member, ready to copy:
That is the whole file. npx agenthood create the-translator scaffolds the same shape if you prefer
not to copy.
5. Register it
Three things make a member real, and none of them is a config edit:
- Location:
skills/contrib/the-<name>/SKILL.mdinside the project (or this repo). Discovery finds it on the next run. - Frontmatter:
metadata.authoris your handle and becomes theownerinowner/name; thenamematches the directory. - Lockfile:
npx agenthood verify --update-lockrecords the file hash so drift is detectable.
Check the whole thing:
6. Submit it
Open a PR (or a PR to the registry, when publishing). The PR is reviewed on four axes:
- Structure: the six sections, the frontmatter, the name
- Behaviour: does the Process actually produce the outcome it claims?
- Security: anything that executes code gets a security review before it is listed
- Permissions: the member's profile stays read-only unless it has a reason not to
Say in the PR why the member exists, what it is not for, and how you tested it. A member with no
tested Process is a prompt, not a member.