Community Guidelines
ClawKit and OpenClaw are open-source projects built by contributors like you. These guidelines help maintain a welcoming, productive community.
Code of Conduct
We follow a simple principle: treat everyone with respect. This community includes people from diverse backgrounds, experience levels, and perspectives. Harassment, discrimination, or personal attacks are not tolerated.
- Constructive feedback on code and ideas
- Helping newcomers with setup issues
- Sharing your use cases and configurations
- Reporting bugs with reproduction steps
- Suggesting features with clear rationale
- Personal attacks or hostile language
- Spam, self-promotion, or off-topic content
- Sharing others' private information
- Submitting malicious code or Skills
- Dismissing questions as "obvious"
How to Contribute
We welcome PRs of all sizes — from typo fixes to new features.
- 1. Fork the repository and create a feature branch
- 2. Develop your changes with clear, focused commits
- 3. Test locally — run
npm run buildand verify no errors - 4. Submit your PR with a clear description of what changed and why
- 5. Respond to review feedback promptly
Found a bug or have an idea? Open a GitHub Issue:
- Bug reports: Include your OS, Node version, error messages, and steps to reproduce
- Feature requests: Describe the problem you're solving, not just the solution you want
- Questions: Check existing issues and the documentation first
Spotted an error in the wiki or docs? Know something that should be documented? Documentation contributions are just as valuable as code changes. Follow the same PR process.
Contributing Skills
Want to add a Skill to the Skill Registry? Here's the process:
- Build your Skill following the MCP tool specification (see Skill System Design)
- Test thoroughly — document expected inputs and outputs
- Submit for review — open a PR adding your Skill to the registry data file
- Community review — maintainers and community members test and verify
- Published — once approved, your Skill appears in the registry with a verified badge
Security Policy
If you discover a security vulnerability, please do not open a public issue. Instead, report it privately via GitHub's security advisory feature or email the maintainers directly. We take security seriously and will respond within 48 hours.
Recognition
We believe in recognizing contributors:
Contributors List
All contributors are listed in the README and on the website.
PR Credits
Every merged PR is credited in the changelog with your GitHub handle.
Skill Authors
Skills in the registry display the author name and link to their profile.