This skill should be used when creating plugins, publishing to marketplaces, or when plugin.json, marketplace, create plugin, or distribute plugin are mentioned.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
claude-plugins
description
This skill should be used when creating plugins, publishing to marketplaces, or when plugin.json, marketplace, create plugin, or distribute plugin are mentioned.
Discovery -> Init -> Components -> Validate -> Distribute -> Marketplace
| | | | | |
v v v v v v
Purpose Scaffold Commands Structure Package Catalog
Scope plugin.json Agents Testing Version Publish
Type README Hooks Quality Release Share
Stage 1: Discovery
Before creating a plugin, clarify:
Question
Impact
What problem does this solve?
Plugin scope and features
Who will use it?
Distribution method
What components are needed?
Commands, agents, hooks, MCP servers
Where will it live?
Personal, project, or marketplace
Stage 2: Initialization
Standalone Plugin
Standalone plugins need their own .claude-plugin/plugin.json:
my-plugin/
├── .claude-plugin/
│ └── plugin.json # Required for standalone
├── README.md # Required for distribution
├── commands/ # Optional components
├── agents/
├── skills/
└── hooks/
plugin.json (Standalone)
{"name":"my-plugin","version":"1.0.0","description":"Brief description of what this plugin does","author":{"name":"Your Name","email":"you@example.com"},"license":"MIT"}
Marketplace with Local Plugins (Consolidated)
For marketplaces where all plugins live in the same repo, use strict: false to consolidate metadata. Plugins don't need their own manifests:
Add components based on plugin needs. See Steps section for which skills to load.
Slash Commands
Create custom commands in commands/ directory:
---
description: "Review code for quality issues"
---
Review the following code: {{0}}
Check for: code style, bugs, performance, security
For complex commands, load the claude-craft skill.
Custom Agents
Define specialized agents in agents/ directory:
---
name: security-reviewer
description: "Security-focused code reviewer"
---
You are a security expert. When reviewing code:
1. Check for vulnerabilities
2. Verify input validation
3. Report issues with severity levels
For agent design patterns, load the claude-craft skill.
Event Hooks
Two ways to define hooks:
File-based (auto-discovered from hooks/hooks.json):
Agents have YAML frontmatter with name and description
Hook scripts are executable (chmod +x)
Hook matchers are valid regex
Documentation:
README.md with installation instructions
LICENSE file included
Local Testing
# Add as local marketplace
/plugin marketplace add ./my-plugin
# Install and test
/plugin install my-plugin@my-plugin
# Test commands
/my-command arg1 arg2
See structure.md for validation commands and detailed component schemas.
Stage 5: Distribution
Semantic Versioning
Follow semver (MAJOR.MINOR.PATCH):
MAJOR: Breaking changes
MINOR: New features (backward compatible)
PATCH: Bug fixes
Release Workflow
# 1. Update version in plugin.json# 2. Update CHANGELOG.md# 3. Commit and tag
git add plugin.json CHANGELOG.md
git commit -m "chore: release v1.0.0"
git tag v1.0.0
git push origin main --tags
# 4. Create GitHub release
gh release create v1.0.0 --title "v1.0.0" --notes "Initial release"
Distribution Methods
Method
Best For
Setup
GitHub repo
Public/team plugins
Push to GitHub
Git URL
GitLab, Bitbucket
Full URL in source
Local path
Development/testing
Relative path
See distribution.md for packaging, CI/CD, and release automation.
Stage 6: Marketplace
A marketplace catalogs plugins for discovery and installation.
