Install Cadasto plugins

This page is for anyone installing Cadasto plugins: how to add the catalog to Claude Code, install and update its plugins, install the same plugins on Cursor, and load a plugin's working copy while developing it.

This repository is a catalog, not a plugin. It contains no skills, agents, or commands, only the marketplace manifest that names each Cadasto plugin and which release to install. The source of truth is .claude-plugin/marketplace.json for Claude Code; .cursor-plugin/marketplace.json is generated from it ($schema dropped) for field parity. Cursor installs are per plugin repository; see Cursor.

Claude Code

Add the marketplace

/plugin marketplace add Cadasto/plugin-marketplace

Once only. The marketplace name is cadasto, so its plugins are addressed as <plugin>@cadasto.

Install a plugin

/plugin install <plugin>@cadasto

The current names are in the plugin list.

Update

/plugin marketplace update cadasto     # refresh the catalog itself
/plugin update <plugin>                # move a plugin to the catalog's current pin

Restart the session for an update to take effect. Because entries are pinned (see versioning.md), /plugin update moves you to the version this catalog names, not to whatever is on the plugin repo's default branch.

Inspect

claude plugin list                     # what is installed, and from which marketplace
claude plugin details <plugin>         # component inventory + projected token cost

Cursor

Install each plugin from its own repository. Cursor's Team Marketplace indexes plugins that live in the repository you import, and this catalog holds no plugin directories (only references to remote ones), so importing it in Cursor finds nothing to install.

Each plugin repo ships .cursor-plugin/plugin.json (skills, agents, rules, hooks). Add that repo locally, or submit it on its own, following that repo's docs/install.md.

Local development against a plugin

To work on a plugin itself, bypass the catalog and load the working copy directly; it picks up uncommitted changes, which a pinned catalog entry deliberately does not. Place or symlink the checkout under the skills directory:

ln -s /path/to/go-coding-plugin ~/.claude/skills/go-coding

The next session loads it as go-coding@skills-dir; confirm with claude plugin list. If the same plugin is also installed from the catalog, claude plugin disable <plugin> leaves only the working copy loaded.

See that plugin repo's own docs/install.md for its host requirements and hook wiring.

What is in the catalog

The authoritative list is the Claude manifest. README.md lists the same plugin names in the same order, and CI checks that agreement. Each entry names the plugin's version and pins source.ref to the matching vX.Y.Z release tag, so a Claude Code install gives you a released version and never an in-flight commit.