Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
71 lines (52 loc) · 3.83 KB

CONTRIBUTING.md

File metadata and controls

71 lines (52 loc) · 3.83 KB
Raw

Contributing to Awesome Agent Plugins

Thanks for considering a contribution. This list exists to be the accurate reference for a spec published on 2026-08-06, so we're strict about verification but fast about merging — the goal is under 7 days to a first response on every PR.

Entries from ZeroPointRepo

Some entries in this list are built by ZeroPointRepo: transcriptapi, zillapi and stayingapi, each in a different category. They are held to the same rules as every other entry, and to a higher bar on one point:

  • Same entry format as everyone else. No bold, no emoji, no "featured" styling, placed alphabetically.
  • At most one per category.
  • A higher acceptance bar: no working manifest and a real README, it does not go in.
  • A competing entry is never rejected or downranked to protect one of ours.

If you ever think one of those entries does not belong, open an issue. We will take it as seriously as any other broken-entry report.

Adding an entry to the catalog

Open a PR that adds one line, in the right category, alphabetically, in this exact format:

- [name](repo-url) by [author](author-url) — one-line description. **[tag]**
  • name — the plugin's name field from its plugin.json, or a clear human-readable name.
  • repo-url — link to the plugin's root folder (the folder containing plugin.json), not just the repo root, if the plugin lives in a subfolder of a monorepo.
  • author / author-url — from plugin.json's author field, or the repo owner.
  • description — one line, plain, no marketing language. Say what it does, not why it's great.
  • tag — one of production (used in the wild), beta, experimental, or reference (spec text/examples, not meant to run standalone).

Do not update the plugin count. The badge and the line under the title both sit between <!-- count:… --> markers and are rewritten from the catalog itself by .github/scripts/sync-counts.mjs. Add your entry and leave the numbers alone — CI corrects them when your PR merges. (They drifted apart, 48 against 33, precisely because they used to be typed by hand.)

Acceptance bar (we merge if all four are true)

  1. The link resolves. We check this before merging, and again on every weekly link-check run.
  2. There's a real, schema-valid plugin.json at the linked path — $schema pointing at https://agent-plugins.org/schemas/1.0.0/plugin.schema.json (or a later version) and a valid name. Run it through ajv-cli yourself before opening the PR (see the README's Tools section) — PRs that fail validation get a friendly bot comment, never an auto-close.
  3. It's not already listed. Check the category and the "Skills & MCP servers ready to be packaged" section first — if it's a skill/MCP server without a plugin.json yet, it belongs there instead.
  4. The category is right. If it spans two, pick the primary use case; maintainers will move it if needed rather than bounce the PR.

We reject only for: a dead link, no real substance (a stub repo), pure spam, or an exact duplicate. We always reply, even to a rejection — a closed PR with a kind reason is fine, silence is not.

Adding a skill or MCP server that isn't a plugin yet

If it's genuinely high-quality but hasn't shipped a plugin.json, it belongs in "Skills & MCP servers ready to be packaged," tagged **[skills]** or **[mcp]** instead of a maturity tag. Same format, same alphabetical placement, same bar for "is this real and maintained."

Reporting a broken entry

Use the "Report broken entry" issue template. Tell us what's broken (dead link, invalid manifest, archived repo) — we'll fix or pull the entry within a week.

Style

  • One entry per line. No sub-bullets, no nested nesting.
  • No affiliate links, no UTM parameters, no tracking redirects.
  • Keep descriptions under ~120 characters where you can.