docs-retrieval

Retrieve documentation context from local ai-docs using library indexes and targeted page loading.

8|1|Updated Jul 11, 2025
One-click install
npx skills add https://github.com/Consiliency/treesitter-chunker --skill docs-retrieval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-retrieval
Source: https://github.com/Consiliency/treesitter-chunker/tree/main/.ai-dev-kit/skills/docs-retrieval
Command: npx skills add https://github.com/Consiliency/treesitter-chunker --skill docs-retrieval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill retrieves documentation context from local ai-docs to speed up development, debugging, and feature planning by prioritizing on-device sources before web search.

Core Features & Use Cases

  • Local-first lookup: Check ai-docs before web searches to surface relevant pages quickly.
  • Targeted loading: Load concise page summaries instead of full documents and consolidate context for sub-agents.
  • Workflow alignment: Follows the docs-management protocol for structured workflows and reproducible results.
  • Use Case: A developer needs library usage examples and API references without leaving the local docs environment.

Quick Start

Check the local ai-docs store by loading ai-docs/libraries/_index.toon to identify relevant docs. Open the specific library index and load targeted pages, then consolidate into a single context block for the sub-agent. If local docs are insufficient, fall back to web search.

Frequently Asked Questions about docs-retrieval

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve documentation context from local ai-docs instead of searching the web?

Local-first doc retrieval checks your on-device ai-docs store before web search, loading targeted pages and consolidating context for faster lookup. Start by checking ai-docs/libraries/_index.toon to identify relevant docs, then load specific library indexes and consolidate pages into a single context block.

Can I load just the documentation I need without pulling entire documents?

Targeted loading retrieves concise page summaries instead of full documents, reducing token usage and speeding up context consolidation. Load specific library indexes, select relevant pages, and merge them into a focused context block for your sub-agent.

How do I integrate local documentation lookup into my development workflow?

Docs-retrieval follows the docs-management protocol for structured workflows. Load ai-docs library indexes, identify pages matching your task, consolidate context, and pass it to sub-agents for feature implementation, debugging, or library exploration with reproducible results.

What happens if the documentation I need isn't in local ai-docs?

Local-first retrieval falls back to web search when local docs are insufficient. Check your ai-docs store first using the library index, then query the web if you don't find what you need, ensuring you exhaust on-device sources before external lookup.

Does docs-retrieval work with multiple libraries and documentation sets?

Yes, docs-retrieval applies across multiple docs by loading and consolidating context from different library indexes. Use the ai-docs/_index.toon to discover available libraries, then load targeted pages from each relevant set and merge them into unified context.