Meeting Notes

Productivity Toolkit — example plugin marketplace

An example Claude plugin marketplace. It catalogues three small, domain-neutral knowledge-work plugins, each bundling a couple of Skills. One plugin also ships an MCP connector to show how that slots in.

It's deliberately generic so it can be used as a template: copy the structure, swap in your own skills, and publish.

What's in here

Plugin	Skills	Notes
writing-assistant	proofread, rewrite-tone	Clean up and re-tone any prose.
meeting-notes	summarise, action-items	Turn raw notes into a recap + tracked actions.
task-planner	breakdown, prioritise	Decompose and order work. Also ships a memory MCP connector.

These are Skills — portable, model-invoked instructions. They're written to work as knowledge-work helpers across Claude surfaces (Claude chat, Cowork) and equally in Claude Code. They intentionally avoid surface-specific tricks, so the same skill behaves the same everywhere.

Repository layout

.
├── .claude-plugin/
│   └── marketplace.json          # the catalogue: lists the three plugins
└── plugins/
    ├── writing-assistant/
    │   ├── .claude-plugin/plugin.json
    │   └── skills/
    │       ├── proofread/SKILL.md
    │       └── rewrite-tone/SKILL.md
    ├── meeting-notes/
    │   ├── .claude-plugin/plugin.json
    │   └── skills/
    │       ├── summarise/SKILL.md
    │       └── action-items/SKILL.md
    └── task-planner/
        ├── .claude-plugin/plugin.json
        ├── .mcp.json             # the MCP connector lives here
        └── skills/
            ├── breakdown/SKILL.md
            └── prioritise/SKILL.md

A few structural rules worth knowing if you adapt this:

• Only plugin.json goes inside .claude-plugin/. Everything else (skills/, .mcp.json, etc.) sits at the plugin root. This is the most common mistake.
• Skill folder name = the skill's invocation name, namespaced by its plugin (/writing-assistant:proofread).
• Names are kebab-case (marketplace, plugins, skill folders). Non-kebab-case names are rejected when syncing to the Claude.ai marketplace.
• A skill's description is what Claude uses to decide when to auto-invoke it — front-load the "use when…" cue.

Using it in Claude Code

Add the marketplace, then install the plugins you want.

# from a local checkout
/plugin marketplace add ./claude-marketplace-example

# or, once pushed to GitHub
/plugin marketplace add <owner>/claude-marketplace-example

# install a plugin
/plugin install writing-assistant@productivity-toolkit

Skills then appear as /writing-assistant:proofread, /meeting-notes:summarise, and so on — and Claude can invoke them automatically based on their descriptions.

Local development

Iterate on a single plugin without installing:

claude --plugin-dir ./plugins/writing-assistant
# edit a SKILL.md, then run /reload-plugins to pick up changes

Validate before sharing:

claude plugin validate .                          # the marketplace
claude plugin validate ./plugins/task-planner     # one plugin

The MCP connector

task-planner bundles a connector in plugins/task-planner/.mcp.json. It uses the reference @modelcontextprotocol/server-memory server to give the planning skills somewhere to persist a task list within a session. The connector starts automatically when the plugin is enabled; the skills work fine without it too. Swap this entry for any MCP server (local binary or remote) to wire up your own connector.

Customising this template

1. Rename the marketplace in .claude-plugin/marketplace.json (name, owner, description).
2. Add or replace plugins under plugins/ and list them in the plugins array.
3. Each plugin needs a .claude-plugin/plugin.json and a skills/<name>/SKILL.md per skill.
4. Run claude plugin validate . and commit.

Licence

MIT — see LICENSE.