claude-plugin-distribution

Package your plugin by creating a distribution-ready ZIP file with the correct directory structure, including plugin.json, README, LICENSE, CHANGELOG, and your plugin code. The Skill guides you through structuring files, excluding unnecessary items, and validating the package meets marketplace requirements.

Use semantic versioning for Claude plugins, updating version numbers in plugin.json and CHANGELOG to track breaking changes, new features, and fixes. This Skill provides templates and best practices for maintaining version consistency across release artifacts and GitHub tags.

Yes. This Skill sets up GitHub Actions workflows to automate plugin validation, packaging, and publishing to GitHub releases with generated release notes. CI/CD integration ensures your plugins are tested and distributed reliably without manual steps.

A valid Claude plugin distribution requires plugin.json with correct metadata, a README explaining functionality, a LICENSE file specifying terms, and a CHANGELOG documenting version history and changes. This Skill enforces these requirements and provides templates for each.

Update the plugin version to a release number, write a CHANGELOG entry documenting initial features, generate a distribution ZIP with correct structure and file inclusions, and publish to GitHub with release notes. This Skill streamlines the entire workflow end-to-end.

A distribution-ready package uses a structured layout with plugin.json at the root, source code in a src or lib directory, documentation files (README, LICENSE, CHANGELOG) at the top level, and excludes build artifacts, node_modules, and development files. This Skill enforces the correct structure automatically.