KARIBU · CONTRIBUTING TO ZANA
One directory, one manifest, one pull request.
The skill you already wrote is the contribution. Paste it below and this page writes the manifest, names the folder, and opens the pull request. In a browser, in a terminal, or the long way round in the repo.
You would be joining
Three ways in
Pick the one that matches how you already work.
They produce the same entry and get the same review. Nobody has to learn our toolchain to put something in the catalog.
In the browser
Paste your file, fill six fields, press a button. GitHub does the fork, the branch and the pull request. No git, no clone, no local setup.
In the terminal
The same draft, emitted as one block of shell. It writes the files, rebuilds the registry, and pushes the branch for you.
In the repo
Fork, add a directory under catalog/, open a PR. The way you would have done it anyway. Templates and the guide are linked below.
The studio
Paste it. The manifest writes itself.
Everything below runs in your browser. Nothing is sent anywhere until you open the pull request yourself.
Step one
Paste the thing you made.
A SKILL.md, a system prompt, a readme. If it has frontmatter, the fields below fill themselves in.
A markdown file that teaches an agent how to do something well.
This file is the contribution. It goes in beside the manifest, unchanged.
Step two
Say what it is.
Lowercase, hyphens. This is its permanent id.
0/160. One line, the way you would say it out loud.
Comma separated, up to twelve.
Step three
Sign it.
This block is your profile. It puts your name on the entry and your flag on the community map. The catalog should read like it was written by people, because it was.
Optional. GitHub, usually.
Optional. Yours to state, however you say it.
Your name
Somewhere. Add a country to appear on the map
Ready to open a PR
5 LEFT- It has a name
- The slug is kebab-case
- One line summary, 160 characters or less
- It is signed by a person or an org
- The SKILL.md itself
- A place, so your flag lands on the community map · optional
schemaVersion: 1
slug: my-entry
name: My Entry
kind: skill
category: productivity
summary: One line on what this does.
author:
name: Your Name
runtime: none
install:
type: skill-copy
package: catalog/skills/my-entry
flags:
official: false
verified: false
You need a GitHub account and nothing else. The editor opens with the file already written; GitHub forks the repo, makes the branch and offers the pull request for you.
amini.yaml, prefilled, and press Commit changes.Nothing on this page is sent anywhere. The draft lives in your browser until you open the pull request yourself.
Your profile
A flag, a city, and a name that is yours.
There is no account to make. The author block in your manifest is your profile: the name you want on the work, an optional handle, and the place you wrote it from. Add a country and your flag lands on the community map the moment the registry rebuilds.
City and country are yours to state, in your own words. Region, coordinates and local clock come from the country code, so nobody files their own place under someone else’s taxonomy, and nobody is asked for anything more personal than a country.
Reads as
Amini · @aminitech
Nairobi, Kenya · East Africa
The same block appears on your entry page, on the community atlas, and next to every other contribution you make. It is the only identity the catalog keeps.
Flags come from the ISO code, drawn with your system’s own emoji. Where they do not render, the country name carries the same information.
Written by people
The catalog should not read like it was generated.
Four things that make an entry worth finding six months from now. None of them are enforced by CI, and all of them are the difference.
Write it the way you would say it
A summary is one line a colleague would understand without a demo. No "leverages", no "seamlessly". If the sentence needs a diagram, it is two sentences.
Say where it came from
A city and a country in your author block. Tools built somewhere else arrive knowing everything except the place they landed in. This is how we track who already holds the context.
Keep the seams visible
Say what it does badly, what it assumes, what it needs. An entry that admits its edges gets used correctly; one that oversells gets abandoned on the second try.
Sign it
Your name or your org, and a handle if you want one. Nothing lands here anonymously. Attribution is the point, not the paperwork.
After you press it
What happens to your pull request.
Review is about scope and safety, not style. If a field is wrong, CI says which one. You are not left guessing, and a first contribution is not a test.
- 1
CI validates your manifest against the schema and tells you, in plain words, which field is wrong.
- 2
The registry is rebuilt, so your entry appears in the catalog and in the CLI.
- 3
Your flag joins the community map, filed under the city you named.
- 4
A maintainer reviews for scope and safety. Security tooling has to be framed for authorized testing.
By contributing you agree your work is licensed under Apache-2.0. If something in this flow is harder than it should be, that is a bug. Open an issue and say so.