cursor-template

Install aitmpl.com skills, commands, agents, and MCPs into Cursor.

npx cursor-template --skill creative-design/frontend-design

Installation

npm install -g cursor-template
cursor-template --help

Or run it once without a global install:

npx cursor-template@latest --skill creative-design/frontend-design

Quick start

Global install is the default. Add --project or --directory <path> to write into a repository.

npx cursor-template --skill creative-design/frontend-design
npx cursor-template --command testing/generate-tests
npx cursor-template --agent development-team/frontend-developer
npx cursor-template --mcp web/web-fetch
npx cursor-template --doctor

| Component | Location | | --- | --- | | Skill | ~/.cursor/skills/<name>/ | | Command | ~/.cursor/commands/<name>.md | | Agent | ~/.cursor/agents/<name>.md | | MCP | merged into ~/.cursor/mcp.json |

The category prefix is dropped, so creative-design/frontend-design installs as frontend-design.

Commands and options

cursor-template [options]

--skill <ids>          Install skills, comma-separated
--command <ids>        Install commands, comma-separated
--agent <ids>          Install agents, comma-separated
--mcp <ids>            Install MCPs, comma-separated
-d, --directory <path> Install into a project instead of the user profile
--project              Same as --directory .
-y, --yes              Overwrite without prompting
--dry-run              Show planned writes and do not change files
--list [type]          List catalog ids
--search <type> <query>
--info <type> <id>
--installed
--remove <type> <id>
--update <type> <id>
--update --all
--doctor
--verbose
--debug                Print stack traces
-h, --help
-V, --version

Browse the catalog at skills, commands, agents, and MCPs.

Configuration

There is no config file. Scope comes from the CLI:

1. --directory or --project installs into that project
2. otherwise files go under the user profile

Existing MCP servers in mcp.json are kept. A different value for the same server asks before overwrite unless --yes is set.

Environment variables

| Variable | Purpose | | --- | --- | | GITHUB_TOKEN | Optional token for the GitHub catalog API when unauthenticated requests are rate-limited. The token is not printed. |

Programmatic API

import { installComponent, destRoots, createCatalog } from 'cursor-template';

const roots = destRoots({ target: 'cursor', scope: 'project', directory: process.cwd() });
const catalog = createCatalog();
await installComponent({
  target: 'cursor',
  roots,
  type: 'skill',
  id: 'creative-design/frontend-design',
  yes: true,
  catalog,
});

Also exported: removeComponent, listInstalled, checkInstall, and runCli.

Troubleshooting

GitHub rate limit means the catalog request was rejected. Set GITHUB_TOKEN and run the command again.

Unknown component type means the type was not skill, command, agent, or mcp.

not found means that catalog id is not in davila7/claude-code-templates. Check the id on aitmpl.com.

Exit codes: 0 success, 1 the operation failed, 2 the arguments were invalid.

Development

Requires Node.js 20 or newer.

npm ci
npm run validate
npm run ci

npm run validate lints, typechecks, builds dist/, tests, and writes coverage. npm run ci also checks the packed files and runs the tarball with npx from a clean temporary directory.

Publishing

Publishing happens from a git tag vX.Y.Z whose version matches package.json. The release workflow runs the same validation, publishes with npm provenance, and creates a GitHub Release.

The published package contains dist/, bin/cli.js, README.md, and LICENSE. Check a packed build locally with:

npm run ci