Thank you for your interest in contributing! This document provides guidelines for contributing plugins and improvements to the marketplace.
Before contributing, ensure your plugin aligns with the marketplace philosophy:
- Challenges assumptions rather than validates them
- Identifies failure modes before they reach production
- Prioritizes long-term maintainability over short-term convenience
- Provides actionable feedback rather than vague suggestions
Adding a quality-focused plugin that fits the marketplace philosophy.
Enhancing existing plugins with better documentation, examples, or functionality.
Fixing issues in plugins or marketplace infrastructure.
Improving guides, examples, or clarity.
Before implementing, open a GitHub Discussion to:
- Describe the plugin's purpose
- Explain how it aligns with marketplace philosophy
- Discuss the problem it solves
- Get feedback from maintainers
Create your plugin following this structure:
plugins/
└── your-plugin-name/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata
├── agents/
│ └── your-agent.md # Agent definitions
├── skills/ # Optional: skills
│ └── your-skill.md
├── docs/
│ ├── USAGE.md # Comprehensive usage guide
│ └── EXAMPLES.md # Real-world examples
├── tests/ # Optional: test examples
│ └── example-test.sh
├── LICENSE # MIT or compatible
└── README.md # Plugin overview
Create .claude-plugin/plugin.json:
{
"name": "your-plugin-name",
"description": "Clear, concise description of what it does",
"version": "1.0.0",
"author": {
"name": "Your Name",
"email": "your.email@example.com"
},
"homepage": "https://github.com/yourusername/plugin-repo",
"repository": "https://github.com/yourusername/plugin-repo",
"license": "MIT",
"keywords": ["relevant", "keywords", "here"]
}Must include:
- What it does: Clear problem statement
- When to use it: Specific use cases
- When NOT to use it: Clear boundaries
- Installation: How to install
- Quick start: 2-3 simple examples
- Philosophy: How it aligns with marketplace values
Must include:
- Detailed usage instructions
- Real-world examples (not toy examples)
- Integration with other tools
- Troubleshooting section
- Advanced usage patterns
Must include:
- At least 3 real-world scenarios
- Expected output for each example
- Explanation of why the example matters
- Common pitfalls
Before submitting, verify:
- Plugin solves a real problem (not hypothetical)
- Documentation is comprehensive
- Examples are real-world, not toy examples
- Clear "when to use" and "when not to use" sections
- License is MIT or compatible
- No hardcoded personal information
- Agent descriptions are clear and concise
- Follows marketplace philosophy
- Fork the marketplace repository
- Add your plugin to
plugins/your-plugin-name/ - Update
.claude-plugin/marketplace.json:
{
"name": "your-plugin-name",
"source": "./plugins/your-plugin-name",
"description": "Your plugin description",
"version": "1.0.0",
"author": {
"name": "Your Name",
"url": "https://github.com/yourusername"
},
"license": "MIT",
"keywords": ["relevant", "keywords"],
"category": "quality",
"strict": false
}- Update marketplace README.md with plugin information
- Test locally:
claude plugin marketplace add ~/Developer/smartwatermelon-marketplace
claude plugin install your-plugin-name@smartwatermelon-marketplace- Submit pull request
Your PR should include:
- Plugin code in
plugins/your-plugin-name/ - Updated
.claude-plugin/marketplace.json - Updated
README.mdwith plugin listing - Clear PR description explaining:
- What problem it solves
- Why it belongs in this marketplace
- How you tested it
- Any dependencies or requirements
- Fork the repository
- Make improvements to plugin docs
- Submit PR with clear explanation of improvements
- Open an issue describing the bug
- Fork and fix
- Add test case if applicable
- Submit PR referencing the issue
- Open a GitHub Discussion first
- Get maintainer feedback
- Implement if approved
- Submit PR with comprehensive documentation
All contributions will be reviewed for:
- Alignment with philosophy: Does it challenge, identify, prioritize?
- Code quality: Clean, maintainable, well-documented
- Documentation completeness: Is it clear how to use this?
- Real-world value: Does it solve actual problems?
- Security: No credentials, safe practices
- Licensing: Compatible with MIT
- Toy examples or "hello world" plugins
- Plugins that only validate (need to challenge)
- Poorly documented plugins
- Plugins with security issues
- Plugins that duplicate existing functionality without improvement
- Plugins that don't align with marketplace philosophy
- Questions: Open a GitHub Discussion
- Issues: Open a GitHub Issue
- Ideas: Open a GitHub Discussion with "Idea" label
- Urgent: Email andrew.rich@gmail.com
Before submitting:
# Add marketplace locally
claude plugin marketplace add ~/path/to/smartwatermelon-marketplace
# Install your plugin
claude plugin install your-plugin@smartwatermelon-marketplace
# Test in real scenarios
claude --agent your-agent -p "Test prompt"
# Test with git hooks (if applicable)
git diff | claude --agent your-agent -p "Review changes"Plugins follow semantic versioning:
- MAJOR: Breaking changes
- MINOR: New features (backward compatible)
- PATCH: Bug fixes
Marketplace versions:
- Updated when infrastructure changes
- Plugin version changes don't require marketplace version bump
By contributing, you agree that your contributions will be licensed under the MIT License.
All contributors will be listed in:
- Plugin README (for plugin-specific contributions)
- Marketplace README (for significant contributions)
- CONTRIBUTORS.md file
Feel free to open a Discussion or reach out at andrew.rich@gmail.com
Thank you for helping make Claude Code development better through quality-focused tools!