Thank you for your interest in contributing to Creo.
Open a GitHub issue with:
- Operating system and version
- Python/Node.js version (if using extensions)
- The
/creocommand you ran - Full error output
- Steps to reproduce
Open a GitHub Discussion with your idea. Include:
- What problem it solves
- Which domain it belongs to (design, content, SEO, DevOps, testing)
- Whether it should be a core skill or an extension
- Fork the repository
- Create a feature branch:
git checkout -b feature/my-feature - Make your changes
- Test your changes (run the relevant
/creocommands) - Submit a pull request
git clone https://github.com/oyusypenko/creo.git
cd creo
# Core is pure markdown -- no build step needed
# For extensions, see their individual README.md files- SKILL.md files must stay under 500 lines
- Reference files must stay under 200 lines
- Agent files must stay under 200 lines
- Use kebab-case for all directory and file names
- No emojis in skill or agent files
- Keep dependencies minimal -- extensions should be self-contained
- All shell scripts must use
set -euo pipefail - Python scripts should output JSON and accept CLI arguments