Install

Up and running in one command

Two lines in Claude Code - the reference host. Using Codex, Cursor, or Copilot? Your host is right below.

/plugin marketplace add reurgency/marketplace
/plugin install deep-skills@reurgency

Update later with /plugin marketplace update reurgency.

Every host

One plugin, five ways in

The same six skills install natively on each host - no forks, no per-host rewrites. Full commands, the capability matrix, and per-host caveats live in the repo's HOSTS.md.

Host Skills Parallel fan-out Per-agent model Install
Claude Code /plugin marketplace add reurgency/marketplace/plugin install deep-skills@reurgency
Codex codex plugin marketplace add reurgency/marketplace/plugins → install 1
Cursor /add-plugin deep-skills (or Customize → Marketplace) 1
Copilot CLI gate 2 copilot plugin marketplace add reurgency/marketplacecopilot plugin install deep-skills@reurgency
Copilot / VS Code ⚠ sequential 2 file-based: set chat.agentSkillsLocationsplugins/deep-skills/skills (no marketplace)

1 Manifest authored; the empirical capability gate (install + run a full cycle, confirm fan-out + model binding) is pending. Fast-moving schema/command details are marked RE-VERIFY in HOSTS.md - check them against your host's current docs at install time.

2 VS Code Copilot's docs show only sequential handoffs. If the gate confirms no parallel fan-out, the single-agent skills (deep-plan, deep-implement, deep-docs) run fully, and the fleet skills (deep-code-review, deep-plan-review, deep-bugfix) route to a single-agent fallback on that host only.

Step by step

Pick your host

Copy-paste commands per host. Each one installs the identical skills - one shared source of truth, thin per-host manifests.

Claude Code · reference host

Claude Code

Add the marketplace, install the plugin - done.

/plugin marketplace add reurgency/marketplace
/plugin install deep-skills@reurgency
update later → /plugin marketplace update reurgency
Codex

Codex

Codex reads the skills natively. Add the marketplace from your shell, then install inside Codex: /plugins → search “deep-skills” → Install.

codex plugin marketplace add reurgency/marketplace
capability gate pending ¹ · re-verify subcommand/flags against current Codex docs
Cursor

Cursor

Install from Agent chat - or through the Customize panel → Marketplace → install.

/add-plugin deep-skills
capability gate pending ¹ · re-verify the command against current Cursor docs
GitHub Copilot · CLI

Copilot CLI

Copilot CLI consumes the same marketplace directly. Verify afterwards with /skills list.

copilot plugin marketplace add reurgency/marketplace
copilot plugin install deep-skills@reurgency
fan-out gate pending ²
GitHub Copilot · VS Code editor

Copilot in VS Code

The VS Code editor has no skills marketplace - it's file-based. Point the chat.agentSkillsLocations setting at the repo's plugins/deep-skills/skills directory (preferred - no duplication), or copy/symlink the skill directories into .github/skills/.

sequential handoffs only ² · single-agent skills run fully; fleet skills fall back

No slash required

Plain English is the primary interface

Slash commands and flags are conveniences, not the way in. Every skill answers to natural language.

Just ask. “Make a deep plan for the export feature” invokes deep-plan exactly like typing /deep-plan - and “run a deep code review on this branch” invokes deep-code-review. On hosts without slash commands or CLI flags - Codex and Copilot chat among them - plain language isn't a fallback, it's the primary path. Say what you want at whatever rigor you want; the skill sorts out the rest.

Quickstart

Run your first /deep-plan

Five minutes from install to a plan a fresh agent could execute cold.

  1. Open your assistant in a real repo. Deep Skills plans against your actual codebase - its questions get sharp because it explores your code first.
  2. Describe the change you want. Type the command with your idea - or just say it in plain English.
    /deep-plan add rate limiting to the public API
  3. Answer only what the code can't. It explores first, then asks the few questions that remain - one at a time, in batches, or all at once. Steer it live; it always returns to where it left off.
  4. Collect the artifact. Your plan lands in your repo at .deep-skills/<effort-name>/01-Plan/plan.md - self-contained, resumable, ready to hand off.
  5. Keep the loop going. Hand the plan to deep-plan-review for independent critique, then deep-implement, deep-code-review, deep-bugfix, and deep-docs. See the whole loop →

What you just installed

Six skills, one pipeline

Each does exactly one job - run the whole chain or reach for any one on its own.