ed3dai/ed3d-plugins
Overview
This skill helps create, release, and maintain a Claude Code Plugin Marketplace with checks to prevent version and metadata drift. It documents the marketplace.json schema, source formats, release checklist, changelog conventions, and validation steps. Use it to keep plugin manifests, marketplace catalog, and changelog synchronized for reliable installs.
How this skill works
The skill inspects .claude-plugin/marketplace.json and each plugin’s .claude-plugin/plugin.json to verify required fields and matching version strings. It guides the ordered release workflow: bump plugin.json, update marketplace.json, add changelog entry, validate, then commit and push. It also validates schema fields, source formats, and common pitfalls that break installation or auto-update behavior.
When to use it
- Creating a new marketplace repository from scratch
- Releasing or tagging a new plugin version
- Adding a plugin entry to an existing marketplace
- Auditing or troubleshooting plugin install failures
- Ensuring changelog, plugin.json, and marketplace.json stay in sync
Best practices
- Always include $schema in marketplace.json for validation tooling
- Bump plugin.json first, then update marketplace.json and CHANGELOG.md in a single commit
- Run claude plugin validate . (or /plugin validate .) before pushing
- Use explicit source formats (relative paths for git-based local repos, github/url objects for remote)
- Write precise changelog entries that name specific skills or agents changed
Example use cases
- Prepare a release: bump plugin version, update marketplace entry, add changelog, validate, commit and push
- Add an internal plugin to the company marketplace using a relative source path and a changelog entry
- Audit a marketplace to find version drift between plugin.json, marketplace.json, and the changelog
- Configure team repo settings so colleagues are prompted to install recommended plugins via .claude/settings.json
- Set up private repo auto-updates by providing appropriate environment tokens for GitHub/GitLab/Bitbucket
FAQ
Required: name (kebab-case), owner object with name and email, metadata.version, metadata.pluginRoot, and a plugins array with each plugin name and source.
How do I verify versions match across files?
Confirm plugins/<name>/.claude-plugin/plugin.json version, .claude-plugin/marketplace.json plugin entry version, and CHANGELOG.md entry header all show the same version string.
When should I use relative source paths vs remote sources?
Use relative paths for monorepo or git-based marketplace adds. Use github or url source objects for external repositories or pinned refs.
21 skills
This skill helps maintain a Claude Code Plugin Marketplace by ensuring marketplace.json and plugin.json stay in sync across versions and changelogs.
This skill analyzes large corpora by coordinating Worker and Critic subagents with a final Summarizer to produce a cohesive report.
This skill helps you craft CLAUDE.md files that capture domain intent, contracts, and freshness dates across top-level and subdirectories.
This skill helps you write robust tests by emphasizing integration over unit tests, waiting for real conditions, and using strategic mocks.
This skill helps you verify codebase state and locate existing patterns to ground design decisions in reality.
This skill enforces Functional Core and Imperative Shell separation in new or refactored Python code, ensuring pure logic remains separate from I/O.
This skill helps you write technical content for developers with clarity and conciseness, avoiding AI patterns and ensuring authentic, actionable documentation.
This skill helps you write robust Playwright automation by applying best practices for selector strategies, waiting patterns, and flaky test reduction.
This skill helps you write and refactor code effectively by enforcing functional vs imperative separation and defensive data validation.
This skill writes validated brainstorming results into a design plan document, filling summary and glossary and outlining implementation phases for clear
This skill helps you craft Claude directives that maximize clarity, motivation, and compliance while minimizing token use and avoiding overtriggering.
This skill refines rough ideas into validated designs through structured questioning, multiple approaches, and incremental validation for clear project
This skill guides you through test-driven development, ensuring you write a failing test first and implement minimal code to pass.
This skill maintains project context by updating CLAUDE.md or AGENTS.md after contract changes, ensuring documentation stays accurate and aligned with code.
This skill helps you scaffold a Claude Code plugin with complete structure, manifest, and components for commands, agents, skills, and MCP servers.
This skill helps you create specialized agents for Claude Code plugins by drafting descriptions, tool sets, and testing workflows.
This skill enforces a research-plan-implement workflow, ensuring Read, brainstorm, and create task todos before coding to deliver reliable results.
This skill helps decide which generic agent to use based on task clarity and complexity to optimize workflow.
This skill helps you apply property-based testing to validate serialization, normalization, and pure functions by asserting key invariants across inputs.
This skill provides a systematic Playwright debugging workflow to diagnose flaky tests, timeouts, and element interactability issues quickly.
This skill helps you verify skills under pressure using RED-GREEN-REFACTOR, documenting failures and iterating to close loopholes.
