Org Skills
How to use it

Use the catalog in GitHub Copilot

Copilot is the other tool with full support: skills, custom agents, always-on instructions and MCP servers all install into the repo, so they are shared with everyone who clones it.

What works here

Support in GitHub Copilot

KindSupported
Skills All 57
Agents All 8, as custom agents
Instructions 12 files, scoped by applyTo
MCP servers Azure DevOps, via .vscode/mcp.json
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 · npx installerNode.js 20+, which provides npx.Picking exactly the skills a project needs. Jump to it
2 · 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 — 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 github-copilot

    Interactive picker. Add --skill <name> … to choose up front, and -y to skip the prompts in CI.

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

    Copilot is the default target, so no --tool flag is needed.

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

    Each file carries an applyTo glob and loads only for matching files.

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

    Writes .vscode/mcp.json, merging with any servers already there.

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 2 — 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 .github/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 ~/.copilot/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 .github/skills cp -R ~/Downloads/org-skills-main/skills/frontend/react/react-development .github/skills/
    New-Item -ItemType Directory -Force .github\skills Copy-Item -Recurse "$env:USERPROFILE\Downloads\org-skills-main\skills\frontend\react\react-development" ".github\skills\"

    No terminal needed. In Finder or File Explorer, create the folders .github/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 — .github. — and Explorer saves it as .github. macOS: dot-folders are hidden in Finder; press ⌘⇧. to show them.

  4. 4Reload, then check it is there

    Reload the VS Code window (Developer: Reload Window), then start a new Copilot Chat.

You should end up with exactly this:

your-project/
└── .github/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
Agentagents/general/<name>.agent.md.github/agents/ — unchanged, no edits needed
Instructionsinstructions/…/<name>.instructions.md.github/instructions/ — unchanged
MCPmcp/integrations/azure-devops/mcp.jsonMerge into .vscode/mcp.json, replacing the org placeholder with your Azure DevOps organization
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.github/skills/ — or ~/.copilot/skills/ with --user
Agents.github/agents/<name>.agent.md
Instructions.github/instructions/<name>.instructions.md
MCP.vscode/mcp.json
Day to day

Using it once it is installed

Commit them

Everything installs into the repo, so a colleague who clones it gets the same skills, agents and rules with no setup.

Pick an agent

Custom agents appear in the agent picker in Copilot Chat. Choose the one whose job matches the task.

Instructions apply silently

A file matching applyTo pulls in those rules for every suggestion in it.

Start the MCP server

Open .vscode/mcp.json and start the server, then sign in when prompted.

Worth knowing

Gotchas

Instructions are always on — keep them short

They are added to every matching request. That is why they are capped at 30–70 lines and push depth into skills.

Check the glob actually matches

An applyTo that matches nothing fails silently. Our Angular globs match CLI 20+ layouts, and Node globs are scoped to server folders so they do not fire on front-end files.

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