refslisted

# refs `refs` gives coding agents real, local source code for the libraries and repos a project depends on, so questions about behavior, history, and releases get answered against the actual checkout — never against training data or `node_modules` bundles. If this skill directory still contains a `references/` subdirectory, it is left over from an older manual install. Ignore it; the files beside this one are authoritative. ## 1. Capability gate Run `refs --version`. **This skill installs nothing.** It never installs or upgrades a runtime, a global package, or a skill, and never asks for elevated privileges. Where setup is missing, name what's missing, print the command for the user to run themselves, and stop. Pick the branch back up once they confirm it's done. `<cli_version>` below means the `metadata.cli_version` value from this file's frontmatter — substitute it before printing any command. - **The command was not found** — `refs: command not found`, `zsh: command not found: refs`, Windows' `'refs' is not recognized`, or whatever the shell says → the CLI isn't installed. Check `node --version` first; refs needs Node.js `>=24.2`, and on a mismatched runtime that is the real problem rather than a failed install — say so and point at the official installer at <https://nodejs.org/en/download>. Otherwise the CLI is published on npm as `@kaisers-io/refs`: print `npm i -g @kaisers-io/refs@<cli_version>` and stop. Re-run `refs --version` once the user confirms,