Contributing a Skill

The catalog is open to contributions. Good candidates for new skills:

Repeatable Nullstone workflows that agents get subtly wrong without guidance.
Conventions specific to your team or stack that you'd like agents to codify.
Project bootstrap tasks (scaffolding a fresh .nullstone/ layout, adding a new block type, etc.).

Quick process

Open a discussion or issue. Describe the workflow and when the skill should trigger. Use the skill feature-request template.
Copy the template. Start from skills/_template/ — it has the frontmatter and section scaffolding.
Fill in the skill. Keep the body focused on one workflow. Put large reference material under references/ and load it on demand from SKILL.md. Frontmatter follows the Agent Skills standard — name (lowercase, matches the directory) and description are required; license and metadata.version are recommended.
Register the skill in the plugin. Add "./skills/<your-skill-name>" to the skills array in .claude-plugin/plugin.json. Skills that aren't listed don't ship in the Claude Code plugin. (_template/ is intentionally left unregistered.)
Run CI locally. yarn install && yarn validate in .github/scripts/ checks frontmatter against the Agent Skills spec and example YAML against the bundled schema.
Open a PR. Update CHANGELOG.md under the next release heading.

[ ] Trigger description is specific. Vague triggers fire the skill when they shouldn't.
[ ] When-NOT-to-use section lists lookalike situations that belong elsewhere.
[ ] Examples demonstrate the style you want agents to copy, not just valid output.
[ ] Large docs and schemas live under references/, linked from the body — keeps the loaded body short.
[ ] MCP tool references are real and current.

The authoritative contribution guide lives in the repo: agent-skills README.