Version-aware
Knows 8.0.0 from 9.3.1. Agents get the surface of the version a project actually pins.
// skills for ai agents
That's your agent — ten seconds after it loads your package as a skill. No docs crawl. No guesswork. It just knows your library.
Jack In compiles your NuGet package into a version-aware skill: the exact API surface of the exact version a project pins — so agents call methods that actually exist, never hallucinated ones.
Mirrored to GitHub (opens in new tab) & the web · auto-updates on every release
“Can you fly that thing?”
“Not yet.”
— a program is loaded —
“I know Kung Fu.”
In the Matrix, you don't learn a skill — you load it. Jack into the construct, request a program, and a moment later the knowledge is simply there.
AI coding agents work the same way. A skill is a program for an agent's brain. Jack In takes your package and turns it into one — a precise, grounded construct of your real API.
The agent loads it and instantly knows your library: the right version, the right members, the right idioms. Authors of the package teach every agent on earth, once.
Point us at your NuGet id and GitHub repo. That's the whole setup.
A version-aware construct of your real API surface — extracted, never invented.
Any agent loads the skill and instantly knows your package. I know Kung Fu.
New release? The skill auto-updates to the new version — mirrored to GitHub & the web.
Knows 8.0.0 from 9.3.1. Agents get the surface of the version a project actually pins.
Only real members ship in the skill. If it isn't in your package, the agent won't call it.
Push a release and the skill regenerates against the new version. No manual step.
Your skill lives in our GitHub repo and on the site — discoverable, forkable, durable.
A skill is portable. Wherever your users' agents run, your package can be loaded.
You publish, you control. One subscription per package keeps your construct live.
Every skill is also live on a hosted MCP server at
https://jackin.dev/mcp. Point any
Model Context Protocol (opens in new tab)
client — Claude Code, Claude Desktop, Cursor, Windsurf, VS Code — at that URL and it pulls the
grounded, version-pinned API surface, patterns, examples, and migration notes
into context on demand. No download, no key, no .csproj guesswork.
# add the hosted server (HTTP transport) — nothing to install
$ claude mcp add --transport http jackin https://jackin.dev/mcp
Added HTTP MCP server "jackin"
# then, inside Claude Code:
/mcp
jackin · connected · 4 tools
# connected — now just ask; Claude picks the tool & arguments for you:
> list the .NET skills jackin can ground
list_skills → ardalis-spec, fastendpoints, stripe, hangfire, …
> pull the api-surface for Ardalis.Specification 9.3.1
get_skill_reference("Ardalis.Specification", "9.3.1", "api-surface")
served v9.3.1 · real members, nothing invented
> show me FastEndpoints 8.1.0 examples
get_skill_reference("FastEndpoints", "8.1.0", "examples")
> which skills does this .csproj pin? (paste it)
detect_version(…) → FastEndpoints 8.1.0, Stripe.net 51.2.0
Every skill the server can ground, with the versions each one ships.
The version-pinned doc — api-surface, patterns, examples, or migration. Resolves the closest tracked version.
Reads a raw .csproj and reports the pinned version of every
supported library.
The closest tracked reference version for a package and a requested version.
Author plan
$5/ mo
per package
Subscribe one package at a time — add more whenever you like.
Create your author account, then add packages from your dashboard: register the package, start the $5/mo subscription, and every agent that jacks in will know it. Updates ride along automatically. One subscription per package, keyed by its GitHub link — add as many packages as you like. (The link can be changed once.)