Toolkit for authoring Claude Code plugins, marketplaces, and skills
Use when authoring, publishing, or composing Claude Code plugin marketplaces. Covers `marketplace.json` schema and field reference, the five plugin source types (relative path, github, url, git-subdir, npm), `pluginRoot`, `category`, `tags`, `keywords`, `strict` mode, hosting and ref/sha pinning, version resolution, release channels, listing external plugins as a catalogue or plugin catalog, recommending marketplaces via `extraKnownMarketplaces`, and cross-marketplace dependencies via `allowCrossMarketplaceDependenciesOn`. Triggers on "create marketplace", "publish marketplace", "register a marketplace", "host a marketplace", "marketplace.json", "marketplace structure", "add plugin to marketplace", "share plugins with my team", "list someone else's plugin in my marketplace", "combine multiple marketplaces", "cross-marketplace dependency", "release channels", "stable vs latest plugin".
Use when authoring, configuring, testing, or shipping a Claude Code plugin. Covers the `plugin.json` manifest (all fields including `lspServers`, `monitors`, `themes`, `outputStyles`, `userConfig`, `channels`, `dependencies`, `$schema`), naming conventions, plugin lifecycle and storage (`${CLAUDE_PLUGIN_ROOT}` vs `${CLAUDE_PLUGIN_DATA}`, scope union, hot-swap, GC, `--keep-data`), local testing with `--plugin-dir`, headless benchmarking, the `claude plugin` CLI, releases, troubleshooting, and per-capability authoring (agents, commands, hooks, MCP, bins, LSP, monitors, themes, output styles, channels). Triggers on "create plugin", "build a plugin", "scaffold plugin", "plugin manifest", "plugin.json", "${CLAUDE_PLUGIN_ROOT}", "${CLAUDE_PLUGIN_DATA}", "add a hook", "add a command", "add an agent", "add a skill to my plugin", "make a skill", "bundle MCP server", "add LSP", "plugin dependencies", "test my plugin locally", "plugin not loading".
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Personal Claude Code plugin marketplace maintained by Sid.
/plugin marketplace add sidhanthapoddar99/sids-plugin-marketplace
If you'd like your plugin listed in this marketplace, open a GitHub issue with the entry as a copy-pasteable JSON snippet. The snippet should be ready to drop directly into the plugins array of .claude-plugin/marketplace.json — no reformatting needed on my end.
Open: https://github.com/sidhanthapoddar99/sids-plugin-marketplace/issues/new
Title: submission: <your-plugin-name>
Body:
### Plugin entry (paste as-is into marketplace.json)
```json
{
"name": "your-plugin-name",
"source": {
"source": "github",
"repo": "your-username/your-plugin-repo"
},
"description": "One-sentence description of what the plugin does"
}
```
### About the plugin
- **What it does:** 1–2 paragraphs
- **Plugin manifest:** link to your `.claude-plugin/plugin.json` in the repo
- **License:** SPDX identifier (e.g. `MIT`, `Apache-2.0`)
- **Maintenance intent:** ongoing / one-shot / experimental
| Field | Use |
|---|---|
version | Pin to a specific git tag (e.g. "version": "1.2.0" resolves to the your-plugin-name--v1.2.0 tag in your repo) |
category | Free-form category for /plugin UI grouping |
tags | Array of search tags |
strict | true to require exact-match version resolution |
The github form above is the most common. The source field also accepts url, git-subdir, npm, or a relative string (only relevant for plugins hosted inside this repo). See the marketplace docs for the full schema: docs/Claude Plugins/04_marketplaces.md.
Submissions are reviewed manually. I'll check that:
.claude-plugin/plugin.jsonclaude plugin install --plugin-dir <your-repo>Approval = your snippet is appended to marketplace.json and the marketplace ref is bumped.
| Plugin | Description | Status |
|---|---|---|
ai-toolkit-dev | Toolkit for authoring Claude Code plugins, marketplaces, and skills | Work in progress (scaffold + plan) |
monorepo-setup | Personal monorepo conventions: env vars, config files, docker-compose, scripts, database/alembic, secrets management | Work in progress (scaffold) |
ai-toolkit-dev vendors content from upstream anthropics/claude-plugins-official using the soft-fork + upstream tracking pattern. Drift detection lives at the marketplace level (scripts/ai-toolkit-dev-check-upstream), not inside the plugin — consumers of the plugin shouldn't have to think about this.
See CLAUDE.md for when Claude triggers a drift check, and docs/Claude Plugins/05_creating-plugins/08_soft-fork-and-upstream-tracking.md for the pattern itself.
.
├── .claude-plugin/marketplace.json # the marketplace manifest
├── CLAUDE.md # agent guidance (upstream check, scope rules)
├── docs/Claude Plugins/ # reference docs on plugin/marketplace internals
├── plugins/
│ ├── ai-toolkit-dev/ # plugin authoring toolkit
│ └── monorepo-setup/ # personal monorepo conventions
└── scripts/ # marketplace-level maintainer tooling
└── ai-toolkit-dev-check-upstream # per-plugin soft-fork drift checker
Sid — [email protected]
TBD — pending decision before first release. Vendored upstream content (under plugins/ai-toolkit-dev/skills/.../topics/ and plugins/ai-toolkit-dev/skills/skill-creator/) remains Apache 2.0; in-house content's license to be set.
npx claudepluginhub sidhanthapoddar99/sids-plugin-marketplace --plugin ai-toolkit-devOperating manual for the documentation-template framework — writing markdown, configuring site.yaml/navbar.yaml/footer.yaml, working with the issue tracker, blog posts, themes, and anything under dynamic_data/. Triages tasks to domain-specific reference files (writing, docs-layout, blog-layout, issue-layout, settings-layout). Ships 11 CLI wrappers (docs-list/show/subtasks/agent-logs/set-state/add-comment/add-agent-log/review-queue for the issue tracker; docs-check-blog/config/section validators) and 2 slash commands (/docs-init to bootstrap a new docs project, /docs-add-section to scaffold a new top-level section).
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Binary reverse engineering, malware analysis, firmware security, and software protection research for authorized security research, CTF competitions, and defensive security
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
Next.js development expertise with skills for App Router, Server Components, Route Handlers, Server Actions, and authentication patterns
Comprehensive .NET development skills for modern C#, ASP.NET, MAUI, Blazor, Aspire, EF Core, Native AOT, testing, security, performance optimization, CI/CD, and cloud-native applications