- Create or update a skill under
skills/. - Run
npm run validate. - Run
npm testwhen changing shared tooling. - Keep generated packages out of commits unless a release requires them.
- Use lowercase kebab-case directory names.
- Keep
SKILL.mdfocused on executable guidance. - Prefer examples that can be copied directly.
- Avoid embedding secrets, machine-specific paths, or private URLs.
- Validation passes with
npm run validate. - Tests pass with
npm test. - Documentation is updated when behavior changes.