Installation

Access required. Both installation paths below require a license from JasperFx Software. See Access & Licensing to request one.

There are two supported ways to install the Critter Stack AI Skills. Pick whichever matches how JasperFx Software granted you access:

• Option A — Private GitHub repository — direct git clone access to jasperfx/ai-skills. Preferred for teams who want to pin a specific commit, audit the skills before deployment, or review changes via PR before rolling out.
• Option B — Private npm registry — install via npm install -g @jasperfx/ai-skills from packages.jasperfx.net. Preferred for the simplest install and predictable versioned releases.

Both paths end with the same npx skills add command that registers the skills into Claude Code.

Prerequisites

• Node.js 20 or later.
• Claude Code (or another agentskills.io-compatible tool).
• Either GitHub read access to jasperfx/ai-skills or a read-only auth token for https://packages.jasperfx.net/npm/ — issued by JasperFx Software based on your license.

---

Option A — Private GitHub repository

1. Clone the repository

Make sure your GitHub account has been granted read access, then clone somewhere stable on your machine (e.g. under ~/jasperfx/):

mkdir -p ~/jasperfx && cd ~/jasperfx
git clone https://github.com/jasperfx/ai-skills.git
cd ai-skills

2. (Optional) Check out a specific release

To pin to a specific version rather than tracking main:

git checkout v1.2.0

Tracking main vs. pinning a tag

Tracking main gives your agent the latest guidance as soon as JasperFx publishes it — at the cost of occasional surprise when a skill's wording or scope changes mid-sprint. Pinning a tag (e.g. v1.2.0) freezes behavior and guarantees identical installs across your team, but you'll miss new patterns and bug-fixes until you explicitly git fetch --tags && git checkout v1.x.y. For production agent deployments, pin a tag and upgrade on a schedule; for exploratory work, tracking main is fine.

3. Register the skills with Claude Code

From anywhere on your machine, point npx skills add at the cloned skills/ directory:

npx skills add ~/jasperfx/ai-skills/skills --skill '*' -g -a claude-code

4. Updating

Pull the latest changes and re-register:

cd ~/jasperfx/ai-skills
git pull
npx skills add ~/jasperfx/ai-skills/skills --skill '*' -g -a claude-code

---

Option B — Private npm registry

1. Configure your global .npmrc

Find the path to your global .npmrc:

npm config list -l

Look for the globalconfig entry in the output. On macOS and Linux this is typically /Users/<username>/.npmrc or ~/.npmrc; on Windows it's usually C:\Users\<username>\.npmrc.

Open that file (create it if it doesn't exist) and add:

@jasperfx:registry=https://packages.jasperfx.net/npm/
//packages.jasperfx.net/npm/:_authToken=<auth_token_provided>

Replace <auth_token_provided> with the read-only token JasperFx Software issued you. The token authorizes read/download from the private registry — it does not publish.

2. Install the package globally

npm install -g @jasperfx/ai-skills

This downloads @jasperfx/ai-skills from the private registry into your global npm prefix.

Pinning a version

npm install -g @jasperfx/ai-skills installs the latest published version. To pin:

npm install -g @jasperfx/ai-skills@1.2.0

Same trade-off as Option A — pin for reproducible installs across your team, take the latest for immediate access to new guidance. Production agent deployments should pin.

3. Register the skills with Claude Code

npx skills add "$(npm root -g)/@jasperfx/ai-skills/skills" --skill '*' -g -a claude-code

4. Updating

Pull the latest published version and re-register:

npm install -g @jasperfx/ai-skills
npx skills add "$(npm root -g)/@jasperfx/ai-skills/skills" --skill '*' -g -a claude-code

---

Flag reference

The npx skills add command used in both paths:

• --skill '*' — install every skill in the target directory.
• -g — register into Claude Code's global skills configuration (available across all projects).
• -a claude-code — target the Claude Code agent.

After registering, Claude Code automatically loads the right skill based on the task at hand — no per-project wiring needed.

Uninstall

Remove Claude Code's registered skills by prefix (same for both installation paths):

npx skills remove "wolverine-*" -g -a claude-code
npx skills remove "marten-*" -g -a claude-code
npx skills remove "polecat-*" -g -a claude-code
npx skills remove "critterstack-*" -g -a claude-code

Then clean up the underlying source:

• Option A — delete the cloned repo: rm -rf ~/jasperfx/ai-skills
• Option B — uninstall the npm package: npm uninstall -g @jasperfx/ai-skills

Next steps

Browse the full catalog in the sidebar, or start with one of the product-specific getting-started skills:

• Wolverine + Marten — New Project
• Wolverine + Polecat — New Project
• Wolverine + EF Core — New Project
• Wolverine + Cosmos DB — New Project