jupi-skills

jupi-skills

The source of truth for the Agent Skills that talk to Jupi — the team's decision platform. Install once; updates flow automatically.

These skills let an agent (in Claude Code, Cowork, or Cursor) work with your team's decisions through the Jupi MCP:

Skill	What it does
search-decisions	Surface prior decisions related to what you're working on — precedents and contradictions. Read-only.
log-decision	Record a decision you've already made as a finalized, searchable entry (title + chosen path + rationale).
submit-decision	Open a decision you can't settle alone and assign it to the right decider. Creates but never finalizes.

All three are bundled in a single plugin, jupi-skills.

The skills call the Jupi MCP server (https://apis.jupi.co/mcp). In Claude Code & Cowork it's bundled with the plugin — nothing to install separately. Cursor needs it added manually (see Cursor).

---

Install

Claude Code & Cowork (plugin marketplace)

/plugin marketplace add jupi-co/jupi-skills
/plugin install jupi-skills@jupi-skills

CLI equivalent (handy for scripting / Cowork setup):

claude plugin marketplace add jupi-co/jupi-skills
claude plugin install jupi-skills@jupi-skills

Invoke a skill (namespaced by plugin):

/jupi-skills:search-decisions
/jupi-skills:log-decision
/jupi-skills:submit-decision

The plugin bundles the Jupi MCP, so it's registered automatically when the plugin installs — no separate MCP setup, no .mcp.json, no claude.ai connector. On first use, approve the one-time authentication prompt.

They also auto-trigger from natural phrasing — e.g. "have we decided X?" (search), "log that we're going with Y" (log), "escalate this to the eng lead" (submit).

Versioning: none, by design. Consumers track main (the default branch); the effective version is its latest commit SHA. Every commit that lands on main is one clean update for everyone — no version bumps, no release bookkeeping. So keep main shippable.

Testing unreleased changes (jupi-skills-staging)

The catalog also exposes a jupi-skills-staging plugin that tracks the staging branch instead of main — use it to try a change before it merges.

Point staging at the branch you want to test, then install:

git branch -f staging origin/<pr-branch> && git push -f origin staging
/plugin install jupi-skills-staging@jupi-skills

It installs under its own namespace (/jupi-skills-staging:…), so it runs alongside the production plugin. Refresh the plugin after each push to staging. The branch is disposable — don't develop on it.

Auto-update

Enable per-marketplace auto-update for jupi-skills in the /plugin interface. Because this repo is public, no token is needed — Claude Code pulls the latest at session start and reinstalls changed plugins. Without auto-update, refresh manually:

/plugin marketplace update jupi-skills

Cursor

Cursor doesn't read marketplace.json or load Claude Code plugins, so it can't use the marketplace above. Install the same skills straight from this repo with the open skills CLI (one installer, works across Cursor and ~80 other agents):

# from your project root — installs all three into .agents/skills/ (which Cursor reads)
npx -y skills add jupi-co/jupi-skills --skill '*' -a cursor

# pull the latest from this repo anytime
npx -y skills update

• Scope: project by default (lands in the repo, shareable with the team); add -g to install globally for all your projects. Add --copy to vendor independent copies instead of symlinking to a canonical store.
• After install, reload the window (Cmd/Ctrl+Shift+P → "Developer: Reload Window") if Cursor doesn't pick the skills up immediately.

No-CLI alternatives:

• Settings UI (auto-synced): Cursor → Settings → Rules → Add Rule → Remote Rule (GitHub) → paste https://github.com/jupi-co/jupi-skills. Per-user; stays synced with this repo.
• Manual copy: copy a skill folder into .cursor/skills/<skill>/ (or .claude/skills/<skill>/, which Cursor also reads), then reload.

Cursor also needs the MCP. Plugins don't reach Cursor, so the bundled server doesn't apply here — add the Jupi MCP once to .cursor/mcp.json (or global ~/.cursor/mcp.json), then reload the window. Without it the skills load but their Jupi calls have nothing to reach.

{
  "mcpServers": {
    "Jupi": { "url": "https://apis.jupi.co/mcp" }
  }
}

Optional: pre-wire install for a consuming repo

A repo that wants these skills available to everyone who clones it can add to its .claude/settings.json:

{
  "extraKnownMarketplaces": {
    "jupi-skills": {
      "source": { "source": "github", "repo": "jupi-co/jupi-skills", "ref": "main" }
    }
  },
  "enabledPlugins": {
    "jupi-skills@jupi-skills": true
  }
}