@nithin554/code-crawler 0.1.64 → 0.1.66

package/skills/code-crawler/SKILL.md

@@ -1,6 +1,16 @@
 ---
 name: code-crawler
 description: Answer questions about code relationships in an indexed repository - callers, callees, impact, entry points, routes, DI wiring, dead code, cycles - using the code-crawler MCP server's SQLite property graph. Use when the question is about how symbols connect (who calls this, what breaks if I change it, where does a request enter, is this reachable) rather than about text you can find by searching. Do not crawl a repository just to answer a question about a single file you already have open.
+metadata:
+  openclaw:
+    emoji: "🕸️"
+    homepage: https://nithin554.github.io/code-crawler/
+    requires:
+      bins: ["node"]
+    install:
+      - kind: node
+        package: "@nithin554/code-crawler"
+        bins: ["codecrawler"]
 ---
 
 # Code Crawler
@@ -20,6 +30,14 @@ delivers these instructions, and `npx add-mcp @nithin554/code-crawler` — or th
 below — registers the server that delivers the tools. Both are needed, and they are
 independent.
 
+If this skill arrived inside the **code-crawler plugin**, the server is registered for you.
+The plugin starts the server from the plugin directory, but resolves a project for each
+call — `crawl_project`, the client's workspace roots, or the project this session already
+selected — and keeps that repository's graph in `<project>/.code-crawler/index.db`. One
+plugin install serves
+every repository you open, each with its own database. Set `CODECRAWLER_DB` to pin a single
+file instead.
+
 The server is the npm package `@nithin554/code-crawler` and needs Node.js ≥ 22.12. Every
 stdio MCP client takes the same command/args/env triple: