Anyone can create and share a brief via GitHub. To get it listed in the official registry (so users can agentbrief use your-brief-name), submit a PR.
brief.yamlhasname,version, anddescriptionpersonality.mdis concise (~30 lines): Role + Tone + Constraints- At least 1 knowledge file or 1 skill directory
- Skills follow SKILL.md format (frontmatter with
name+description) - Tested locally:
agentbrief use ./your-briefworks without errors - Open source license (MIT or Apache-2.0)
| Level | Meaning | How to get it |
|---|---|---|
| official | Maintained by the AgentBrief team | Core team only |
| verified | Community-created, reviewed and approved | Submit a PR (see below) |
| community | Listed but not reviewed | Coming soon |
- Fork this repository
- Add your brief entry to the end of
registry.yaml:your-brief-name: source: github:your-username/your-repo description: One-line description of what it does trust: verified
- Open a PR with:
- What the brief does and who it's for
- Link to the brief's GitHub repo
- Confirmation that you've tested it locally
- Maintainer review (typically within 48 hours)
- Merge = your brief is live in the registry
Before submitting, verify:
-
personality.mdis lean (~30 lines) — identity, not encyclopedia - Knowledge files are reference material, not duplicated personality content
- Each skill has a clear trigger condition in its
descriptionfield -
agentbrief use ./your-briefworks in a clean temp directory -
agentbrief eject your-brief-namecleans up completely - No hardcoded paths or machine-specific content
Open an issue with:
- Steps to reproduce
- Expected vs actual behavior
- Your Node.js and npm/pnpm version
Start a Discussion in the Ideas category.