The Claude Code plugin catalog maintained by Cadasto B.V., for Claude Code users who want Cadasto's plugins for openEHR clinical modeling, spec-driven development, Go and PHP coding standards, and documentation standards. A plugin extends a coding assistant with skills, commands, agents, and tools, teaching it a domain, connecting it to a service, or giving it a specific workflow. A marketplace is a catalog of plugins you browse, install, and update from inside the assistant. Add this one once and install any listed plugin as <plugin>@cadasto.
This repository is a catalog only. Each plugin lives in its own repository and is listed here pinned to a release tag, so an install gives you a released version. The source of truth is .claude-plugin/marketplace.json; .cursor-plugin/marketplace.json is generated from it for field parity. Every listed plugin also ships a Cursor manifest, but Cursor installs each plugin from that plugin's own repository, not from this catalog.
The same repository builds the public site: what each plugin is for, and how to add the marketplace. make docs-serve previews it at http://127.0.0.1:8000 (Docker). GitHub Pages publishes main to https://cadasto.github.io/plugin-marketplace/ when the repository's Pages source is GitHub Actions. See docs/site.md.
Requirements. Claude Code with the /plugin command, and network access to GitHub: each plugin is fetched from its Cadasto/… repository at the pinned tag. Cursor users install from each plugin's repository instead; see Cursor. Individual plugins state their own host requirements in their repositories. Maintaining the catalog needs Python 3 (the validator uses only the standard library).
| Plugin | Description |
|---|---|
| openehr-assistant | openEHR clinical modeling for AI assistants — archetypes, templates, compositions, AQL, CKM reuse search, and specification lookup. |
| openehr-assistant-dev | Maintainer plugin for developing the openEHR Assistant MCP server and plugin — authoring guides, prompts, MCP tools, examples, and managing releases |
| go-coding | Idiomatic Go coding standards for AI assistants — formatting, errors, concurrency, testing, layout. |
| php-coding | Idiomatic PHP coding standards for AI assistants — PHP 8.4+, PER Coding Style, PHPStan level 8. |
| sdd | Spec-Driven Development for AI assistants — requirements, RFC-2119 specs, and ADRs with stable identifiers, machine-checked traceability, and the delivery pipeline that runs on them: workers, review into a findings file, close-out; two profiles. |
| docs-editing | Human-facing documentation and content standards for AI assistants: technical writing, copy editing, AI-tell cleanup, marketing copy, SEO and AI citability, with claims grounded in cited evidence. |
Add the Cadasto marketplace. You only need to do this once:
/plugin marketplace add Cadasto/plugin-marketplace
Then install any plugin from the catalog:
/plugin install openehr-assistant@cadasto
To pick up new plugins and released versions later:
/plugin marketplace update cadasto
Install each plugin from its own repository. Cursor's Team Marketplace indexes plugins that live in the repository you import, so importing this catalog of remote sources finds nothing to install. Each Cadasto plugin ships .cursor-plugin/plugin.json and is added on its own; see docs/install.md.
Each catalog entry pins a release tag (vX.Y.Z) instead of tracking a default branch, so installing a plugin gives you a released version and never an in-flight commit. Publishing a new plugin version takes two steps: tag the release in the plugin repo, then bump version and source.ref in this catalog. Until the catalog moves, users keep the previous version.
Adding or updating a plugin means editing .claude-plugin/marketplace.json, then regenerating the Cursor twin and validating the result:
python3 scripts/validate.py --fixBefore committing, also run claude plugin validate ., Claude Code's own schema check; it warns on unknown fields and is not part of CI.
CI runs the same script, plus a Vale prose lint, on every pull request and every push to main. The site has its own check, make docs-check. See docs/testing.md for what each check covers, docs/authoring.md for the entry format, docs/site.md for the site build, and docs/versioning.md for the release steps.
| Document | Covers |
|---|---|
| docs/install.md | Adding the Claude Code marketplace, and installing the same plugins on Cursor |
| docs/authoring.md | The catalog entry format, and adding, updating, renaming, or removing a plugin |
| docs/testing.md | Validating the manifests and smoke-testing a real install |
| docs/versioning.md | How the catalog is versioned, and the release procedure |
| docs/site.md | How the public site is built, pinned, and published |
| CHANGELOG.md | What changed in each catalog release |
AGENTS.md is the working brief for AI assistants maintaining this repository.