skills - Claude Code plugin marketplace

Plugin marketplace hosting dev-workflow plugins and standalone utility skills.

Two marketplace files sit at the repo root: .claude-plugin/marketplace.json for Claude Code and Copilot CLI, and .cursor-plugin/marketplace.json for Cursor (it lists jidoka-cursor).

The name jidoka comes from the Toyota Production System: automation that stops the line and calls a human when something is off. The plugin does the same, pausing at the clarifying-question and plan-review gates. line is its entry-point skill: it runs one user story down the line to a PR.

Start it yourself: /jidoka:line followed by the story, acceptance criteria or ticket in Claude Code, or line from the / menu in Copilot CLI and Cursor. The skill sets disable-model-invocation, so it stays out of every session's skill listing, and pasting a story without the command does not start it. The companion skills are the reverse: user-invocable: false keeps them out of Claude Code's / menu, but they stay visible to the model because the orchestrator and the subagents invoke them.

The three jidoka* directories are build outputs. Everything is authored once under src/ and rendered by make build:

Each agent source carries one shared body and a frontmatter block per harness (tool names, model ids, flags), so a change to an agent's instructions lands in all three harnesses from one edit. Rendered files start with a GENERATED comment: edit the source, run make build, commit both. make check (also run in CI) fails when the committed outputs are stale. The renderer needs Python 3 with PyYAML; scripts/render.py documents the source format.

Agents name a role, not a model. src/models.yaml maps roles to tiers and tiers to a model per harness:

Two agents pin a harness: impl-simplify runs on the economy tier in Copilot and Cursor, and security-reviewer stays on Claude Opus in Cursor. To change the routing, edit src/models.yaml and run make build. To change it for one machine without touching the plugin:

• Claude Code: ANTHROPIC_DEFAULT_OPUS_MODEL (or SONNET, HAIKU, FABLE) in settings.json env remaps a tier; CLAUDE_CODE_SUBAGENT_MODEL sets a default that frontmatter still beats; a same-named agent in .claude/agents/ replaces the plugin's.
• Copilot CLI: subagents.agents.<name>.model in ~/.copilot/settings.json or .github/copilot/settings.json. Copilot downgrades a subagent to the session model's price tier, so run the session on an Opus-tier model when you want verification on Opus.
• Cursor: copy the plugin's agents into .cursor/agents/ and edit model: there (plugin subagents ignore the field today).

On Claude Code the line skill also overrides per dispatch in two cases: refactor-tier stories review on sonnet, and an implementer re-dispatched after a failed review or evidence check goes up to opus.

Test it with make test (renderer and routing rules), make check (render drift), make lint (markdownlint over every Markdown file) and make smoke-claude (one real dispatch per role on Claude Code, reporting the model each ran on; costs a few API calls).

Before installing either plugin, make sure your machine has:

1. Azure CLI signed in to your ADO organisation - required for ADO ticket lookups and task creation in the workflow.

   az login
   az account show          # verify the right tenant/subscription
   az devops configure --defaults organization=https://dev.azure.com/<your-org> project=<your-project>

2. Git - required by the git-worktrees and raise-pr skills. Confirm with git --version; ensure user.name and user.email are set (git config --global --list).

Run inside a Claude Code session (slash commands):

# 1. Register the marketplace (one-time)
/plugin marketplace add wei6bin/skills

# 2. Install the plugin
/plugin install jidoka@skills

# 3. Refresh discovery after edits (no restart needed)
/reload-plugins

# 4. Run one story down the line
/jidoka:line <user story, acceptance criteria or ticket>

# Browse / verify / manage
/plugin                                       # picker, "Installed" tab
/plugin marketplace list
/plugin disable   jidoka@skills
/plugin enable    jidoka@skills
/plugin uninstall jidoka@skills

Plugin contents land at ~/.claude/plugins/cache/skills/jidoka/.

After editing the plugin source, refresh with /reload-plugins.

Run inside a Copilot CLI session:

# 1. Register the marketplace (one-time)
/plugin marketplace add wei6bin/skills

# 2. Install the plugin
/plugin install jidoka-copilot@skills

The plugin carries the same line skill, companion skills and nine subagents as jidoka, rendered into Copilot's .agent.md format with Copilot tool aliases and model ids, plus the after-edit hooks as a Copilot postToolUse hook set. Dispatch strings use the jidoka-copilot: prefix. The hooks expect the plugin at ~/.copilot/installed-plugins/skills/jidoka-copilot/, which is where a marketplace install lands.

# 1. Register the marketplace (one-time)
/plugin marketplace add wei6bin/skills

# 2. Install the plugin
/plugin install utility-skills@skills

# 3. Reload
/reload-plugins

Adding a new skill: create utility-skills/skills/<name>/SKILL.md and add ./skills/<name> to the skills array in .claude-plugin/marketplace.json. A skill may also bundle scripts/ and references/ alongside its SKILL.md; reference them by skill-relative path.

jidoka-cursor is a Cursor plugin rendered from the same source: skills and agents already use Cursor's bare subagent_type and picker-slug models, the hooks ship as afterFileEdit plugin hooks, and rules/jidoka-cursor.mdc is an always-on rule with the per-phase dispatch table. Cursor discovers it through .cursor-plugin/marketplace.json at the repo root:

1. Customize → Plugins → Import from Repo, paste https://github.com/wei6bin/skills, install jidoka-cursor, and turn on Enable Auto Refresh so pushes to main re-index within ten minutes.
2. Or add the repo as a team marketplace from the dashboard.
3. For local testing, symlink or copy jidoka-cursor/ into ~/.cursor/plugins/local/.

Do not also install the Claude Code jidoka plugin in Cursor: its skills carry the same names and would collide.

Known Cursor limitation. Subagents loaded from a marketplace plugin run on the parent model; Cursor ignores their model: frontmatter (forum reports 157485 and 168771). Project agents are honoured and take precedence, so to pin models copy the plugin's agents into the project and re-copy after updates:

cp ~/.cursor/plugins/cache/*/jidoka-cursor/*/agents/*.md .cursor/agents/

See jidoka-cursor/README.md for the model tier table and jidoka-cursor/SMOKE-TEST.md to verify the routing.

MIT.