Intent
Your dependency can ship the knowledge required to use it.
TanStack Intent gives maintainers a versioned path from source docs to Agent Skills, then gives consumers a controlled way to discover that guidance from installed packages.
installed dependencies
lockfilescan mode
static files · no package code executed
discovered skill
tanstack-router
useful for
Model typed search params and route loaders
source: docs/framework/react/guide/search-params.md
Consumer trust model
Discovery can scan the workspace. Trust is still explicit.
Intent can inspect workspace dependencies for static skill files without executing package code. An allowlist and exclusions decide which packages may contribute guidance, and the agent loads a skill only when the task calls for it.
01
Scan
Read package metadata and static skill files.
02
Allow
Match package names against your allowlist and exclusions.
03
Inspect
Keep source references and skill content visible.
04
Load
Give only relevant guidance to the active agent task.
Editor and install hooks may streamline discovery. They are not a security boundary.
documentation changed
The source relationship changed. A maintainer decides whether the skill needs an edit.
Conservative freshness
A changed source is a review signal, not proof of bad guidance.
Skills declare the documentation they depend on. intent stale can flag a skill when those sources move, but it does not pretend to understand whether the semantic advice is wrong. Maintainers make that call.
Maintainer loop
The skill releases with the code it explains.
Generate or author guidance near the package, validate its structure and source references in CI, then include it in the npm tarball. The package version becomes the skill version; the public registry makes that history browsable after indexing.
- 1
Author
SKILL.md + source refs
- 2
Validate
structure checked in CI
- 3
Publish
included in npm files
- 4
Discover
indexed package history
@tanstack/react-router
code + docs + skills share one release