agent-resume is a community standard, and it exists because of the people who design, refine, document, and maintain it. This page is our way of saying thank you — and a durable record of who built what.
Maintainers #
Maintainers own the direction of the standard, review proposals, and have merge rights. They are responsible for keeping the schemas coherent and the versioning policy honored.
| Contributor | Role | Focus |
|---|---|---|
| @rahhbster (Robert Merrill) | Creator & Lead Maintainer | Schema design, spec, project direction |
Core contributors #
Core contributors have made sustained, significant contributions — multiple merged PRs that materially advanced the schemas, spec, tooling, or ecosystem.
Be the first — see How to get listed.
Contributors #
Everyone who has had a meaningful change merged. Bug fixes, doc improvements, new examples, language bindings, adapters — it all counts.
Your name goes here.
Acknowledgements #
Standards build on prior art. agent-resume is grateful to:
- JSON Resume — the de-facto standard for the
human-facing résumé, which CCDM is designed to be complementary to and
interoperable with via
ccdmToJsonResume(). - JSON Schema — the foundation the entire standard is expressed in.
How to get listed #
We add people here as they contribute — you don’t need to ask, but you’re welcome to.
- Contributors: once your first meaningful PR is merged, a maintainer adds you to the Contributors list (or add yourself in the same PR — see below).
- Core contributors: promoted after sustained, significant contributions.
- Maintainers: invited by existing maintainers based on a track record of trusted, high-quality work and good stewardship of the standard.
Adding yourself in your PR #
When you open a PR, feel free to add a line to the Contributors section in the same PR:
- [@your-handle](https://github.com/your-handle) — what you changed (#PR)
Keep it to one concise line. Maintainers may tidy formatting on merge.
What counts as “significant” #
Judgment, not a checklist — but roughly: a merged change that improves the standard or its tooling for everyone. Typos and trivial tweaks are appreciated but generally rolled up rather than individually listed; a meaningful schema fix, a new adapter, a language binding, a substantive doc/spec improvement, or a well-scoped feature all qualify.
See CONTRIBUTING.md for how to propose changes.