npm as a Distribution Channel for Agent Context
joelclaw's 52-skill canonical system is exactly this pattern — TanStack is formalizing it for the entire npm ecosystem
TanStack Intent is a CLI for library maintainers to generate, validate, and ship Agent Skills alongside their npm packages. Install @tanstack/query, get the query skills too. Auto-discovered, versioned with the code, compatible with the open Agent Skills standard.
The core idea is that a library shouldn’t just ship code — it should ship the context an agent needs to use that code correctly. Right now agents either rely on training data (which goes stale), scrape docs (which is slow and noisy), or developers write skills by hand. Intent short-circuits all of that. The maintainer writes the skill once, checks it into the repo, and it versions alongside the API. When the library breaks a pattern in v5, the skill says so.
Tanner Linsley and the TanStack team have the distribution to make this matter. Between TanStack Query, TanStack Router, TanStack Form, and the rest of the ecosystem, they’ve got millions of npm downloads per month. If those packages all ship Intent skills, agents working in React and TypeScript codebases suddenly have structured context for the most common dependencies — without anyone having to write it manually.
The underlying agentskills.io standard is the interesting long game here. It’s an attempt to establish a cross-runtime format so skills are consumable by Claude, Codex, pi, or anything else that reads them. Whether it achieves that or fragments into competing formats is the open question.
Key Ideas
- Skills ship with the package — versioned in
package.json, discoverable without any extra config - CLI validates skills at publish time, so broken or outdated skills don’t make it to npm
- agentskills.io is the open standard Intent targets — runtime-agnostic skill format
- joelclaw already does this pattern for its own packages —
skills/is canonical, symlinked into~/.pi/agent/skills/and~/.agents/skills/— the ecosystem is converging on what Joel built for personal use - Version lock matters — a skill that describes v4 query behavior against a v5 codebase actively misleads agents; coupling skill versioning to package versioning solves this
- Potential to monitor: if TanStack adopts this broadly, it becomes a meaningful data point for how agent-aware npm packages evolve