DHIS2 CHAP — Claude Code plugins

Internal Claude Code plugin marketplace for people working on the DHIS2 CHAP modeling platform.

A "marketplace" is just this GitHub repo. You add it to Claude Code once, then install any plugins you want from it. Plugins can add slash commands, skills, subagents, hooks, and MCP servers to your Claude Code.

---

Prerequisites

• Claude Code installed and signed in.
• Access to GitHub (this repo is public, so no extra setup is needed).

---

1. Add the marketplace (once)

Run this inside Claude Code:

/plugin marketplace add dhis2-chap/claude-plugins

Claude Code fetches the repo and registers it under the name dhis2-chap. You only need to do this once per machine.

---

2. Find and install a plugin

Browse everything available, then install what you want:

/plugin

This opens the plugin manager UI where you can see the marketplace's plugins and install them interactively.

Or install directly by name, using the <plugin>@dhis2-chap form:

/plugin install hello-world@dhis2-chap

After installing, the plugin's commands and skills are available immediately. For example, the hello-world plugin adds a /hello command — try it to confirm everything works.

Install scope (optional)

By default a plugin is installed for you only (user scope). You can also share an install through a repo's checked-in settings:

/plugin install <plugin>@dhis2-chap --scope project   # shared via .claude/settings.json
/plugin install <plugin>@dhis2-chap --scope local      # this repo only, gitignored

---

3. Manage installed plugins

/plugin list                                # show installed plugins
/plugin disable <plugin>@dhis2-chap         # turn off without uninstalling
/plugin enable  <plugin>@dhis2-chap         # turn back on
/plugin uninstall <plugin>@dhis2-chap       # remove completely

---

4. Get updates

New plugins and new versions land in this repo over time. Refresh your local copy of the marketplace to see them:

/plugin marketplace update dhis2-chap

Then install or update plugins as usual. Installed plugins pick up new versions when the plugin's version is bumped (or, for unversioned plugins, when the git commit changes).

---

Auto-suggest plugins to a whole repo (optional)

If you want everyone who opens a particular CHAP code repo in Claude Code to be prompted to enable this marketplace and a set of plugins, add this to that repo's .claude/settings.json and commit it:

{
  "extraKnownMarketplaces": {
    "dhis2-chap": {
      "source": { "source": "github", "repo": "dhis2-chap/claude-plugins" }
    }
  },
  "enabledPlugins": {
    "hello-world@dhis2-chap": true
  }
}

---

Using the skills with Codex, Copilot and other agents

The skills inside the plugins use the open Agent Skills format, so other agents can use the ones that do not depend on Claude Code. Today that is write-issue, write-roadmap-idea, convert-to-chapkit, improve-chap-model and docs-review. Install them with the skills CLI, from the root of the repo you work in:

npx skills add dhis2-chap/claude-plugins --skill write-issue --agent codex github-copilot

Leave out --skill to choose from a list, and change --agent for other agents. Run npx skills update to get new versions. Claude Code users do not need this; install the plugin instead.

Skills that only work in Claude Code are marked metadata: internal: true in their SKILL.md and are not offered by npx skills.

---

Available plugins

Plugin	Description
hello-world	Example plugin — a /hello command and an example skill. Copy it as a template for new plugins.
improve-chap-model	Iteratively improve an existing CHAP model. Evaluates a model (local folder or GitHub URL) on a dataset with the chap CLI, tunes the model code and/or config, and tracks every experiment with git. Run /improve-chap-model.
discourse	Set up and use the Discourse MCP server against the DHIS2 Community of Practice (community.dhis2.org). Run /discourse-setup once, then ask Claude to search the CoP, read threads, or draft a release announcement in the Chap category.
convert-to-chapkit	Convert an existing CHAP model repo (MLproject plus train/predict scripts, Python or R) into a chapkit 2.x service. Captures a pre-conversion baseline, maps every MLproject field, and gates the PR on numeric parity with the legacy predictions. Run /convert-to-chapkit.
jira-audit	Audit CLIM Jira against what has landed in the chap repos: wrong statuses, outdated epic/issue descriptions, duplicates, missing components, epics missing from the team roadmap page or not linked from a ROADMAP idea, and roadmap ideas with no epic delivering them or linked with the wrong link type (it suggests epic-to-idea links by text similarity). Produces a shareable report with tiered proposed changes and applies the ones you approve. Needs the Atlassian MCP. Run /jira-audit.
product-landscape-diagram	Workshop facilitator for mapping the products and tools we build and depend on, from getting data into DHIS2 to enabling decisions. Interviews the group with clickable questions and free text, and keeps a live, zoomable diagram updated as an artifact. Workshop instructions in plugins/product-landscape-diagram/WORKSHOP.md. Run /product-landscape-diagram.
write-issue	Write or revise Jira epics and issues from discussion with you, not from guesses. Asks for context before drafting, keeps undecided things as open questions, uses a fixed epic format, asks who the finished work should be shown to, and links new epics from the team roadmap page, and marks issues that need a leadership check with the ch-leadership label. Other filing details (components, labels) come from each repo's own Jira instructions. Triggers when you ask to create or describe an epic or issue. Its second skill, write-roadmap-idea, writes Chap and Open Climate Service ideas in the DHIS2 Roadmap project (ROADMAP, Jira Product Discovery) in the team's Why / What / Who format, sets the product area fields, and links ideas to the CLIM epics that implement them. Triggers when you ask to post or propose a roadmap idea.
docs-review	Review documentation across the modeling platform and climate team repos to find holes: docs that no longer match the code, overlap and contradictions between sources, places where a reader following the docs gets stuck, and broken structure and links. Pick teams, groups or single repos; the sources are listed in skills/docs-review/sources.md and the reader journeys come from dhis2-chap/user-stories, which the review also checks against the docs and against the user stories in the open-climate-service documentation. Uses the team terminology, principles and earlier docs reviews in dhis2-chap/chap-first-brain (and says when a principle looks wrong next to the docs), and lists repos in the orgs that the sources do not cover yet. Produces a shareable report. Works in Claude Code and, with fallbacks, in other agents. Run /docs-review.

---

Contributing a plugin

Want to share a plugin with the team? See CONTRIBUTING.md for the repo layout and a step-by-step guide.

---

Troubleshooting

• A new command/skill doesn't show up after installing. Run /plugin list to confirm it's installed and enabled. If you just published a change, run /plugin marketplace update dhis2-chap first, then reinstall.
• The marketplace name. Plugins are always referenced as <plugin>@dhis2-chap, regardless of the repo name (claude-plugins). The dhis2-chap part comes from the name field in .claude-plugin/marketplace.json.