Skip to content

Installation

The plugin approach installs skills directly into Claude Code and keeps them up to date automatically.

1. Add to ~/.claude/settings.json

{
  "extraKnownMarketplaces": {
    "bmsuisse-skills": {
      "source": {
        "source": "github",
        "repo": "bmsuisse/skills"
      }
    }
  },
  "enabledPlugins": {
    "coding@bmsuisse-skills": true,
    "databricks@bmsuisse-skills": true,
    "ui@bmsuisse-skills": true,
    "writing@bmsuisse-skills": true,
    "bms@bmsuisse-skills": true,
    "caveman@bmsuisse-skills": true
  }
}

Or via the Claude Code command palette:

/plugin marketplace add bmsuisse/skills
/plugin install coding@bmsuisse-skills

2. Reload

/reload-plugins

Skills are now active. Type / to see available slash commands.

Troubleshooting: "its source doesn't match its extraKnownMarketplaces entry"

/plugin marketplace add bmsuisse/skills registers a plain github source. If your extraKnownMarketplaces entry adds extra fields (ref, sparsePaths), the sources differ and Claude Code refuses the add. Use exactly the entry shown above (only source and repo), or skip the add command, since the settings entry already declares the marketplace.

Plugin reference

Plugin Skills Use for
coding Python, TypeScript, TanStack, FastAPI, Azure auth, Postgres, autoresearch, init-app-stack General dev work
databricks databricks-cli, spark-connect Databricks & Spark
ui rich-data-tables, inter-without-ai-slop, design-review Data tables, writing style, visual QA
writing remove-ai-writing, scientific-revision Writing & docs
bms Master skill + all core standards All standards via /bms
caveman caveman, caveman-review, caveman-commit Token-efficient comms
azure-deploy azure-deploy Azure deployments
bdt-status (a Claude Code mod, no skills; needs Claude Code ≥ 2.1.287 and bdt ≥ 0.30.0, ≥ 0.46.0 to list several PRs) shows one row per open PR of the branch, e.g. PR #69 feat: mod ✗ failing · closes #68 (title cut at 50 characters), above the prompt, from bdt pr info --json --all Seeing the PRs, their issues and the build state without leaving the session
azure-diagnostics azure-diagnostics Azure diagnostics
dev-workflow dev-workflow (+ hooks: worktree-only edits, auto-approved worktree entry, PR-publish gate requiring /code-review, /bms-code-review or a finished codex review (foreground and exiting 0 with nothing masking its status, or backgrounded with -o <file>; promotion PRs between dev/test/main are exempt); plus bms-code-review, bms-plan-review and branching-strategy) Enforcing the team's worktree → draft PR → review → publish flow
maintenance maintenance (/maintenance dead-code\|bump\|lint\|audit\|prod\|nightly\|xfail\|db-perf\|tests\|all) Periodic repo upkeep: dead code, dependency bumps, ruff/ty baseline, bun audit / uv audit, prod errors, nightly failures, xfail, slow queries, slow/flaky tests

Per-project setup

To scope skills to one project, add .claude/settings.json to the project root and commit it:

{
  "extraKnownMarketplaces": {
    "bmsuisse-skills": {
      "source": { "source": "github", "repo": "bmsuisse/skills" }
    }
  },
  "enabledPlugins": {
    "coding@bmsuisse-skills": true
  }
}

The init-app-stack scaffold generates this file automatically with the right plugins for the stack.

Codex CLI — Plugin

Codex installs the same plugins from .agents/plugins/marketplace.json, which is generated from .claude-plugin/marketplace.json by scripts/sync-codex.mjs.

codex plugin marketplace add bmsuisse/skills
codex plugin add coding@bmsuisse-skills
codex plugin add bms@bmsuisse-skills
codex plugin list                      # see all plugins and what is installed

Skills carry over from every plugin. The dev-workflow hooks work in Codex too: the PR-publish gate and the worktree-only edit check (applied to apply_patch). Not carried over: the PreToolUse command remapping, the review agents (Codex subagents are a different format), the EnterWorktree auto-approve (Codex has no such tool), and the bdt-status mod.

Codex only runs plugin hooks you have reviewed. After installing dev-workflow, start codex once and trust its hooks in /hooks. Without that, they are silently skipped (codex --dangerously-bypass-hook-trust skips the review for one run).

In a Codex session the PR-publish gate accepts as review: an explicit $bms-code-review / $code-review skill, a shell command that read that skill's SKILL.md, a finished Codex /review, or a finished codex exec / codex review code review (same rules as for Claude Code).

skills CLI — Cursor, Copilot, Codex, others

Prerequisites

Node.js 18+ and npm are required. Check:

node --version   # needs 18+
npm --version

Download Node.js (LTS) from nodejs.org if needed — npm is bundled.

Install

No global install required — bunx (recommended) or npx fetches the CLI on demand:

# All skills (recommended)
bun x skills add bmsuisse/skills

# One specific skill
bun x skills add bmsuisse/skills --skill coding-guidelines-python

# Update previously installed skills
bun x skills update
# Alternative with npx
npx skills add bmsuisse/skills

Platform detection

The CLI detects your agent from config files in the current directory:

Detected Platform Writes to
.claude/ Claude Code .claude/skills/
.cursor/ or .cursorrules Cursor .cursor/rules/
.github/copilot-instructions.md GitHub Copilot .github/instructions/
AGENTS.md or .codex/ Codex CLI .codex/skills/
.gemini/ Gemini CLI .gemini/skills/

Telemetry opt-out

DISABLE_TELEMETRY=1 bun x skills add bmsuisse/skills

Verify

Start a new Claude Code session and type / — installed skills appear in the list. Or ask:

What skills do you have active?