Org Skills
How to use it

Use the catalog in Claude Code

Skills, agents, instructions and MCP servers all work in Claude Code. Skills load automatically when a prompt matches; agents are subagents you call by name.

What works here

Support in Claude Code

KindSupported
Skills All 57, loaded automatically when relevant
Agents All 8, as subagents
Instructions 12 rule files, path-scoped
MCP servers Azure DevOps, read-only by default
Choose once

Three ways to install it

You do not need Node.js, npm or npx unless you want them. Pick the row that matches the machine you are on.

RouteWhat you need installedBest for
1 · Claude Code CLI
Recommended
Nothing. Its installer is a standalone binary.The whole catalog, kept up to date. Jump to it
2 · npx installerNode.js 20+, which provides npx.Picking exactly the skills a project needs. Jump to it
3 · Manual copyNothing at all. Not even git.Locked-down machines, no admin rights, or just one or two skills. Jump to it

A skill is a folder holding a SKILL.md Markdown file. Nothing is compiled and nothing runs at install time, so route 3 is a plain file copy — it is not a lesser version of the other two, just a manual one.

Route 1 — nothing to install first

Install Claude Code itself, then let it pull the catalog

Claude Code's installer is a standalone binary — it does not need Node.js, and the installed claude does not run on Node either. If you have Claude Code, you already have everything needed for the whole catalog, with updates.

curl -fsSL https://claude.ai/install.sh | bash
irm https://claude.ai/install.ps1 | iex
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

Reopen your terminal afterwards and run claude --version. Prefer a graphical installer? brew install --cask claude-code on macOS, or winget install Anthropic.ClaudeCode on Windows.

Then add the catalog

Run these inside Claude Code as slash commands (drop the claude prefix), or in your terminal as written. Swap the plugin name for the stack you want — each one bundles the skills for that area.

claude plugin marketplace add AGCO-Global/org-skills claude plugin install frontend-react-skills@org-skills --scope project

Plugins track the marketplace they came from, so catalog changes reach you — review, update, disable or remove them from the /plugin menu. No Node.js is involved at any point. Scopes: --scope project commits it for everyone in the repo, user enables it in all your projects, local just this repo for you.

Route 2 — needs Node.js

Run these once, in your project

Requires Node.js 20 or newer. Every command is safe to re-run — it overwrites what it installed before. No Node.js? Install it at the bottom of this section, or skip to the manual route.

  1. 1Skills for your stack
    npx skills add AGCO-Global/org-skills -a claude-code

    Interactive picker. Add --skill <name> … to pick up front, or -g to install for every project.

  2. 2Agents
    npx -y github:AGCO-Global/org-skills add agent code-reviewer test-writer --tool claude

    Generates a Claude subagent from each agent. Read-only agents are generated with disallowedTools so they cannot write to Azure DevOps.

  3. 3Instructions
    npx -y github:AGCO-Global/org-skills add instructions typescript secure-coding --tool claude

    Becomes a path-scoped rule file — it applies only to files matching its globs.

  4. 4Azure DevOps MCP
    npx -y github:AGCO-Global/org-skills add mcp azure-devops --org <your-ado-org> --tool claude

    Writes .mcp.json. The shipped config is read-only; see the server README before granting writes.

Getting Node.js, if you need it

Only required for this route. It is a one-off install, and the commands above then work in any project.

Download the LTS macOS installer from nodejs.org/en/download and run it — it includes npm and npx. If you already use Homebrew:

brew install node

Download the LTS Windows installer (.msi) from nodejs.org/en/download and run it. Accept the defaults; npm and npx come with it. Then close and reopen your terminal, or npx will not be on PATH yet.

Do not use your distribution's nodejs package — on Debian and Ubuntu it is often several majors behind 20 and the installer then fails. Open nodejs.org/en/download, choose your platform and a version manager, and it prints the exact commands to paste.

Check it worked: node -v should print v20 or higher, and npx -v should print a number. No admin rights, or a machine you may not install software on? Skip Node entirely and use the manual route below — it needs nothing.

Route 3 — no Node.js, no npm, no git

Install by copying a folder

This always works. You are copying Markdown files into a folder the tool reads, which is exactly what the installer does — it just saves you the clicks.

  1. 1Get the files — pick whichever is easiest
    SourceHow
    One skillOpen its page in the catalog and press Download .zip. Smallest download, no GitHub access needed.
    The whole catalogOn GitHub, press the green Code button → Download ZIP. Or use this direct link: main.zip.
    If you have gitgit clone https://github.com/AGCO-Global/org-skills.git — git alone is enough; no Node required.
  2. 2Unzip it and find the folder that contains SKILL.md

    That folder is the skill, and its name matters — the tool matches it. Nesting varies, so go by the SKILL.md rather than counting folders:

    skills/frontend/react/react-development/SKILL.md   ← copy "react-development"
    skills/general/backlog-writing/SKILL.md           ← copy "backlog-writing"

    Copy the whole folder, not just SKILL.md — some skills ship a references/ subfolder the skill links to.

  3. 3Drop it into .claude/skills/

    Create those folders in your project root if they do not exist. For every project on your machine instead of just this one, use ~/.claude/skills/.

    Run from your project root. The source path below assumes you unzipped the catalog ZIP into ~/Downloads; change it to wherever your unzipped folder is.

    mkdir -p .claude/skills cp -R ~/Downloads/org-skills-main/skills/frontend/react/react-development .claude/skills/
    New-Item -ItemType Directory -Force .claude\skills Copy-Item -Recurse "$env:USERPROFILE\Downloads\org-skills-main\skills\frontend\react\react-development" ".claude\skills\"

    No terminal needed. In Finder or File Explorer, create the folders .claude/skills inside your project if they are not there, then drag the skill folder in. Keep its name exactly as it is.

    Windows: File Explorer refuses a folder name beginning with a dot. Type it with a trailing dot as well — .claude. — and Explorer saves it as .claude. macOS: dot-folders are hidden in Finder; press ⌘⇧. to show them.

  4. 4Reload, then check it is there

    If you just created the .claude/skills/ folder, run /reload-skills — a directory that did not exist when the session started is not picked up on its own. Then run /skills to confirm yours is listed.

You should end up with exactly this:

your-project/
└── .claude/skills/
    └── react-development/
        ├── SKILL.md
        └── references/        (only some skills have one)

Updating later. A copied skill is a copy, not a link — it will not change when the catalog does. To update, delete the folder and copy the new one in. If that becomes a chore, that is the argument for one of the routes above.

Also by hand

Agents, instructions and MCP without tooling

These are single files rather than folders, so copying them is quicker still.

KindCopy thisTo here
Agentplugins/org-agents/agents/<name>.md — the Claude-ready version, already converted.claude/agents/
Instructionsinstructions/…/<name>.instructions.md.claude/rules/<name>.md. One edit: swap the applyTo: "a,b" front-matter line for a paths: list, one glob per line.
MCPmcp/integrations/azure-devops/claude.mcp.json.mcp.json in the project root, with your Azure DevOps organization filled in

Copy the agent from plugins/org-agents/agents/, not from agents/general/. The plugins/ copies are generated for Claude Code and carry the disallowedTools entries that keep read-only agents from writing to Azure DevOps.

Where files land

What gets written to your repo

The same paths whichever route you took — useful for checking a manual copy went to the right place.

KindPath
Skills.claude/skills/ — or ~/.claude/skills/ with --user
Agents.claude/agents/<name>.md
Instructions.claude/rules/<name>.md
MCP.mcp.json in the project root
Day to day

Using it once it is installed

Skills fire on their own

Ask normally — "add a swipe-to-dismiss gesture to this card". The matching skill loads from its description; you never name it.

Call an agent by name

Ask for the code reviewer, or the build triage agent. Each runs as a subagent with only the tools its job needs.

Instructions are always on

They apply to every file matching their globs, with no prompt needed.

Check what loaded

If a skill did not fire, the description did not match your wording — say what you are working on more concretely, or name the skill.

Worth knowing

Gotchas

/plugin does not work in the VS Code extension

It reports "not available in this environment". Use the installer commands above, or the shell commands claude plugin marketplace add AGCO-Global/org-skills and claude plugin install org-agents@org-skills --scope project.

Agents cannot hold a conversation

A subagent runs once and returns. Our agents put questions in an "Open questions" section of their output instead of waiting for an answer.

Next

Pick the skills for your stack

With Node.js, this picks them interactively. Without it, copy the folders — same result.

npx skills add AGCO-Global/org-skills