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. Both go through the AgentSkills CLI (agentskills-cli), a .NET global tool. Pick whichever matches how JasperFx Software granted you access:

• Option A: Private NuGet registry: install via agentskills-cli add JasperFx.AiSkills from packages.jasperfx.net/nuget/. Preferred for the simplest install and predictable versioned releases.
• Option B: Private GitHub repository (support contract only): direct git clone access to jasperfx/ai-skills. Available exclusively to customers with an active JasperFx Support Plan. Preferred for teams who want to pin a specific commit, audit the skills before deployment, or review changes via PR before rolling out.

Both paths end with the same agentskills-cli add command that registers the skills into your agent.

Prerequisites

• .NET 8 LTS or .NET 10 runtime (required by agentskills-cli).
• Claude Code, Cursor, Codex, OpenCode, or another agentskills.io-compatible tool.
• A read-only auth token for https://packages.jasperfx.net/nuget/, emailed to you after you purchase AI Skills - or, for customers with an active JasperFx Support Plan, GitHub read access to jasperfx/ai-skills.

Install the AgentSkills CLI

dotnet tool install --global agentskills-cli
agentskills-cli --help

Update or uninstall any time with dotnet tool update --global agentskills-cli or dotnet tool uninstall --global agentskills-cli.

---

Option A: Private NuGet registry

Each skill is a self-contained directory under skills/ that follows the agentskills.io spec, so it works with any conformant client - Claude Code, Cursor, Copilot, OpenCode, Aider, Codex, Windsurf. The steps below show Claude Code and the universal target (read by Cursor, Codex, OpenCode, and every other spec-compliant agent); swap or repeat -a for the agents you use.

1. Add the JasperFx NuGet feed

Where your token comes from

After you purchase AI Skills, JasperFx Software emails you setup instructions containing your personal read-only registry token. The token authorizes read/download from the private registry only; it cannot publish.

You can also view, reveal, and regenerate your token any time from the customer portal - handy if the token is lost, rotated, or compromised. Regenerating revokes the old token atomically.

Don't have the email yet? Check spam, or contact JasperFx Software.

Register the feed with the dotnet CLI. Replace YOUR_TOKEN_HERE with the token from your purchase email:

macOS / Linux

dotnet nuget add source https://packages.jasperfx.net/nuget/v3/index.json \
  --name jasperfx \
  --username jasperfx \
  --password YOUR_TOKEN_HERE \
  --store-password-in-clear-text

Windows (PowerShell)

dotnet nuget add source https://packages.jasperfx.net/nuget/v3/index.json `
  --name jasperfx `
  --username jasperfx `
  --password YOUR_TOKEN_HERE

--store-password-in-clear-text is required on Linux and macOS because Windows-style encrypted password storage is unavailable there. On Windows the token is stored encrypted and the flag is unnecessary.

If you prefer a checked-in per-repo NuGet.Config, drop this file at the project root:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="jasperfx" value="https://packages.jasperfx.net/nuget/v3/index.json" />
  </packageSources>
  <packageSourceCredentials>
    <jasperfx>
      <add key="Username" value="jasperfx" />
      <add key="ClearTextPassword" value="YOUR_TOKEN_HERE" />
    </jasperfx>
  </packageSourceCredentials>
</configuration>

2. Install the skills

agentskills-cli reads the same NuGet.Config as dotnet restore, so once the source is registered the install is a single command. -g makes it user-global so every project picks it up.

# universal target: writes to ~/.agents/skills/
# (Cursor, Codex, OpenCode, and every other spec-compliant agent reads here)
agentskills-cli add JasperFx.AiSkills -g -a universal -y

# Claude Code uses its own ~/.claude/skills/, so target it explicitly
agentskills-cli add JasperFx.AiSkills -g -a claude-code -y

# both at once
agentskills-cli add JasperFx.AiSkills -g -a universal -a claude-code -y

Drop -g to install only into the current project's ./.agents/skills/ and ./.claude/skills/ directories. Project-local installs write a skills-lock.json at the project root; commit it so collaborators on the same repo install identical versions.

Pinning a version

Add @<version> to the package id to pin:

agentskills-cli add JasperFx.AiSkills@1.4.0 -g -a universal -a claude-code -y

Pin for reproducible installs across your team; take the latest for immediate access to new guidance. Production agent deployments should pin.

3. Install only a subset

Use -s <skill-name> (repeatable) to install one or more specific skills instead of the full catalog:

agentskills-cli add JasperFx.AiSkills \
  -s wolverine-handlers-middleware \
  -s marten-aggregate-handler-workflow \
  -g -a universal -y

4. Updating

# re-running add pulls the latest published version and overwrites the
# installed skill directories
agentskills-cli add JasperFx.AiSkills -g -a universal -a claude-code -y

Browse available versions in the customer portal or via dotnet package search JasperFx.AiSkills --source jasperfx.

---

Option B: Private GitHub repository

Support contract required

Direct repository access is provided only to customers with an active JasperFx Support Plan. If you do not have a support contract, use Option A.

agentskills-cli reuses your existing git authentication (SSH key, Personal Access Token via git-credential-manager, or gh auth login). If git clone git@github.com:jasperfx/ai-skills.git already works on your machine, no extra configuration is needed.

1. Install directly from the repo

agentskills-cli add jasperfx/ai-skills -g -a universal -a claude-code -y

agentskills-cli clones the repo into a temporary cache, copies the skills into the target directories, and discards the clone.

2. Or clone and install from a working copy

Useful when you want to pin to a specific commit, audit the skills before installing, or share one checkout across many agentskills-cli add runs:

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

# (optional) pin to a tag
git checkout v1.4.0

agentskills-cli add ~/jasperfx/ai-skills/skills -g -a universal -a claude-code -y

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.4.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. Updating

cd ~/jasperfx/ai-skills
git pull
agentskills-cli add ~/jasperfx/ai-skills/skills -g -a universal -a claude-code -y

---

Flag reference

The agentskills-cli add command used in both paths:

• -g: user-global install into ~/.agents/skills/ and per-agent dirs (omit for project-local).
• -a <agent>: target a specific agent. Repeat for multiple. universal writes to the canonical .agents/skills/ directory read by Cursor, Codex, OpenCode, and every other spec-compliant agent; claude-code writes to Claude Code's own .claude/skills/.
• -s <skill-name>: install one specific skill. Repeat for multiple. Omit to install all 74.
• -y: non-interactive (no prompts, accept defaults). Required for scripts/CI.

See the AgentSkills CLI add command reference for the full list.

Uninstall

Remove the registered skills by source:

# from a global install
agentskills-cli remove JasperFx.AiSkills -g -y    # NuGet install
agentskills-cli remove jasperfx/ai-skills -g -y   # GitHub install

# from a project-local install (run from project root)
agentskills-cli remove JasperFx.AiSkills -y
agentskills-cli remove jasperfx/ai-skills -y

Or remove individual skills by name:

agentskills-cli remove wolverine-handlers-middleware -g -y

For Option B users who cloned the repo manually, also rm -rf ~/jasperfx/ai-skills if you no longer want the local working copy.

Troubleshooting & support

If agentskills-cli add JasperFx.AiSkills returns a 401 from packages.jasperfx.net:

• Confirm the token hasn't been revoked or rotated. Sign in to the customer portal to view the active token for your entitlement.
• Confirm the source was registered with --store-password-in-clear-text (Linux/macOS) so the token was actually persisted, and that the token in your dotnet nuget add source command was the active one.
• Verify the source is registered: dotnet nuget list source. The jasperfx entry should be enabled and point at https://packages.jasperfx.net/nuget/v3/index.json.
• If the token is missing or compromised, regenerate it from the entitlement detail page in the customer portal - the old token is revoked atomically. Or contact JasperFx Software.

For bug reports, install questions, or feedback on AI Skills (and any other JasperFx commercial offering), open an issue or discussion at github.com/JasperFx/ProductSupport - the canonical tracker for commercial products. Real-time community chat lives in Discord.

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