Org Skills
How to use it

Use the catalog in Cursor

Cursor reads the Agent Skills format, so all 57 skills install and load automatically. Agents, instructions and MCP servers from this repo target Copilot and Claude Code.

What works here

Support in Cursor

KindSupported
Skills All 57, loaded automatically
Agents Not supported — run the skill directly
Instructions Not supported — use Cursor Rules
MCP servers Configure Cursor’s own MCP settings directly
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 cursor

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

  2. 2One stack only
    npx skills add AGCO-Global/org-skills --skill react-development react-architecture react-testing -a cursor

    Install just the skills a repo needs, rather than the whole catalog.

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

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

  4. 4Reload, then check it is there

    Reload the Cursor window, then start a new chat.

You should end up with exactly this:

your-project/
└── .cursor/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.

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.cursor/skills/ — or ~/.cursor/skills/ with -g
IndexAGENTS.md at the repo root lists every skill and its path
Day to day

Using it once it is installed

Skills fire on their own

Ask normally in chat or inline. The skill whose description matches loads itself.

No agent picker — ask for the job

Ask for a review of your diff and the matching *-code-review skill loads.

Want always-on rules?

Cursor has its own Rules feature. Our instructions files are short and readable — copy the rules you want into a Cursor rule rather than installing the file.

Worth knowing

Gotchas

Instructions are not Cursor Rules

Different formats. The content is portable, the file is not.

Pull updates deliberately

Re-run the install command to pick up catalog changes; installed skills are copies, not links.

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