Skip to content

Contributing

The plugin gets better the more we use it and tell each other what failed. Most contributions take less than five minutes and need no Git knowledge.

Three skills, no Git needed

  • skill-feedback — when a skill misbehaves or its output is wrong. Captures context and files a GitHub issue on your behalf.
  • skill-idea — when you want a skill that doesn't exist yet. Logs the idea for the roadmap.
  • skill-sender — when you've authored a new skill (via skill-builder) and want to ship it. Files a pull request.

All three work in any Cowork conversation. They need the GitHub MCP connected in your Cowork settings; without it, they print a paste-ready issue block you can copy.

Suggest a change to shared rules

  • Network-wide change (source tiers, EU process clarifications, anti-AI-tone patterns) → edit a file under shared/_common/.
  • Your overlay (your logos, workspaces, blurb) → edit a file in your organisation's folder. The maintainer reviews it doesn't leak into other installs.

Open a PR on EMPN-eu/empn-core. Or email the maintainer the change you want — they open the PR for you.

Author a new skill

Run skill-builder in Cowork. It walks you through the skill's frontmatter, trigger phrases, hand-offs, and files a PR via skill-sender. No need to learn the SKILL.md format by hand.

If you prefer to write the file directly, see shared/_common/skill-authoring-guide.md. Its C1–C14 table is the list your skill is checked against, so it is worth reading before you draft rather than after.

What happens after you send it

A reviewer runs on every contribution: safety, naming, a behaviour test, and a check that nothing else broke. Low-risk changes can land on their own; anything needing a judgment comes back as a five-line question. See Lab reviewer.

Register a new organisation

If your organisation isn't pre-registered (arena-ide, dezernat-zukunft, institut-avant-garde, empn), email the maintainer with your organisation's name, your preferred slug (lowercase letters and hyphens, like dezernat-zukunft), and a contact email. They open the PR. One day's turnaround.

Maintainer notes

For commit conventions, versioning, the testing pipeline, and the consistency-audit checklist, see CONTRIBUTING.md and MAINTAINERS.md at the repo root.