link-retrieve
Link-retrieve provides CLI commands to query, summarize, and navigate a Link wiki repository without loading entire contents into context. Use it when an agent needs to search, answer questions from, or brief on wiki content through bounded commands like `lnk query`, `lnk brief`, and `lnk graph-summary` that manage token budgets automatically.
git clone --depth 1 https://github.com/gowtham0992/link /tmp/link-retrieve && cp -r /tmp/link-retrieve/skills/link-retrieve ~/.claude/skills/link-retrieveSKILL.md
# Link Retrieve Use bounded CLI commands so the agent does not dump the whole wiki into context. In a source checkout, replace `lnk` with `python3 link.py`. 1. If readiness is unclear, start with: ```bash lnk health [link-root] ``` 2. For most questions, use a compact query packet: ```bash lnk query "<question or task>" [link-root] --budget small ``` Increase to `--budget medium` or `--budget large` only when the packet says more context is needed. 3. Before longer work, prime from memory: ```bash lnk brief "<current task>" [link-root] ``` 4. For graph context, stay bounded: ```bash lnk graph-summary "<topic>" [link-root] --limit 40 --depth 1 ``` 5. For performance checks, use: ```bash lnk benchmark "<topic>" [link-root] --budget small ``` Do not enumerate every page or request the full graph unless the user explicitly asks for an export or exhaustive audit.
Use when a user wants to verify Link readiness, troubleshoot a local wiki, inspect interrupted writes, repair generated indexes, or back up Link without setting up MCP.
Use when a user asks to ingest raw files into Link, refresh stale source pages, propose memories from sources, or validate source-backed wiki updates through the CLI without MCP.
Use when a user asks an agent to remember, recall, review, update, archive, restore, forget, or explain local Link memories through the CLI without requiring MCP.