Put your playbook in the library.
Every skill here is one practitioner’s method, with their name and photo on it. Pick one thing you are unusually good at, and let your agent do the paperwork. It interviews you, writes the files and opens the pull request.
- 1.With your agentClaude or ChatGPT interviews you about one thing you are expert at, drafts the files, runs the check and opens the pull request under your name. Start below.
- 2.By hand with gitFork the repo, copy the templates, write the skill, run the validator and open a pull request.Contributor guide
- 3.No git at allOpen the Submit a skill issue form and paste your files. A maintainer turns it into a pull request under your name.Open the form
One prompt. About twenty minutes of answering questions.
Fetch https://raw.githubusercontent.com/agiea-brain/agency-skills/main/AGENTS.md and follow its contribution flow. Interview me about one thing I'm genuinely expert at, until you have my frameworks, my numbers and two real examples. Draft it in their format, check it, and open the PR. If you can't use git here, give me the prefilled issue link or the paste bundle it describes.
What a skill is here
Narrow beats broad. “How I run a pipeline review”, not “sales”. If you can say in one sentence when someone should reach for it, it is the right size. Three kinds of experts write here.
What gets reviewed
Every submission is checked in this order. The first step that fails is where it comes back to you.
- 1FormatThe validator passes and the files are in the right place. Checked by CI.
- 2SafetyNothing in the files could harm the person running the skill.
- 3SubstanceA clear trigger, real judgment, and depth in the reference pages.
- 4IdentityA real person, verifiable from the author card. Personal LinkedIn is the check.
Your first pull request includes an author card: name, role, headline, LinkedIn, company domain and the areas you work in. It becomes your contributor page and your install count starts there.