Teach your AI assistant to
read the code graph, not the whole repo
Vibgrate Skills are ready-made agent instructions plus wiring for Vibgrate AI Context — the local, offline MCP server started by vg serve — that vg installwrites into your AI coding assistant. One command teaches the agent to prefer the local code graph — cheaper tokens, more relevant context — over grepping and reading dozens of files.
What is a Vibgrate Skill?
A skill is the combination of two things vg install writes into a coding assistant: a SKILL.md with ready-made agent instructions, and the local MCP wiring that registers Vibgrate's read-only graph server.
Together they teach the agent to ask the local code graph for relevant context first — which is cheaper and more focused than grepping and reading many files to reconstruct the same picture.
What each install writes
- A
SKILL.mdwith the agent instructions, in the assistant's expected location. - Registration of Vibgrate AI Context — the local, offline MCP server (
vg serve) — so the agent can query the graph. - An advisory, opt-out nudge that points the agent at the graph before it reaches for grep.
- A clean reverse with
vg uninstall.
One command installs everything
Install into a single assistant, or every assistant Vibgrate detects, in one go.
vg install --all
Writes the skill into every supported assistant detected in your environment.
vg install claude vg uninstall claude
vg is the default command (alias vibgrate).
What the skill instructs the agent to do
The instructions steer the agent toward graph-first reasoning.
Prefer the local code graph
The skill tells the agent to query the local code graph for relevant context first, rather than grepping and reading many files — cheaper tokens, more relevant context.
Reason about impact and structure
It teaches the agent to check impact before editing, trace paths between symbols, and use hubs and areas to orient in an unfamiliar codebase.
Stay version-correct
For library questions, the agent is pointed at version-correct docs for the dependencies the project actually uses, and at drift reports for upgrade context.
CLI commands the skill teaches
vg areasGroup the codebase into cohesive functional areas.vg "<question>"Ask a question and get a budget-bounded context block drawn from the code graph — instead of grepping and reading dozens of files.vg driftReport upgrade drift; pair with vg scan for CI-friendly output.vg hubsSurface the most-connected symbols — the high-leverage parts of the code.vg impact <name>List what a change to this symbol could affect, following the dependency edges.vg lib <name>Pull version-correct documentation for a library the project actually uses.vg path <A> <B>Find how two symbols are connected through the graph.vg show <name>Show a single node — its definition, signature, and immediate neighbours.vg tree <name>Print the call tree rooted at a node.
Vibgrate AI Context — read-only MCP tools
vg serve starts Vibgrate AI Context, a local, offline MCP server: version-correct library docs — plus your code map and drift — served to your AI, offline. The same graph and more is exposed to the agent as a set of read-only tools.
orientStart here: one call returns the map overview, ranked matches for your question, and the top hit’s blast radius.
search_symbolsFind a known name or string fast — ranked symbol lookup with a literal file-search fallback.
query_graphAnswer a natural-language question with a bounded context block.
get_nodeFetch a single symbol with its definition and neighbours.
find_pathTrace the connection between two symbols.
impact_ofReturn the blast radius of changing a symbol.
tests_forList the tests that cover a symbol — is a change here tested?
get_graph_summaryReturn a compact overview of the whole graph.
list_areasList the cohesive functional areas of the codebase.
list_hubsList the most-connected, high-leverage symbols.
get_factsReturn deterministic facts — contracts and invariants — for a node (needs a --deep build).
guide_nodeReturn cited standards and practices (OWASP/CWE) for a node.
check_driftOffline dependency drift inventory across npm/PyPI/Go.
vuln_attributionAttribute each open vulnerability to who introduced it, with exposure windows and CRA remediation metrics.
list_vulnerabilitiesList known vulnerabilities from the last vg scan --vulns — id/CVE, severity, CVSS, fixed version.
upgrade_impactShow what a package upgrade would break: major distance, import blast radius, vulns fixed.
list_modelsLocal model discovery — Ollama / LM Studio / GGUF, offline.
resolve_libraryResolve a library to the version in YOUR project — version-correct, drift-annotated.
library_docsVersion-correct, drift-annotated usage docs for a library, offline.
The graph these tools query is the Free Code Graph, and the docs come from the Free Dev Docs Library — both free, local, and offline.
Looking for the hosted, cloud MCP server with drift and portfolio data? See the Vibgrate Cloud MCP Server.
Supported assistants
21 install targets — each one written from the same vg install command.
claudecursorwindsurfvscodecodexgeminiopencodekiloaiderfactorytraekiroampkimicodebuddycopilot-clipidevinhermesopenclawagentsPer-assistant quickstart
Pass the assistant's id to vg install.
vg install claude
vg install cursor
vg install windsurf
vg install vscode
Ready to wire it up?
Install the CLI, then run vg install --all to give every assistant graph-first context.
# Run without installing anything
npx @vibgrate/cli scan
# Pin a version or see every command
npx @vibgrate/cli@latest --helpno install·Nothing is installed globally — ideal for CI or a one-off scan.