doc-lookup

Fetch specific documentation sections from DiPeO's docs using anchors or keyword queries.

12|2|Updated May 29, 2025
One-click install
npx skills add https://github.com/sorryhyun/DiPeO --skill doc-lookup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-lookup
Source: https://github.com/sorryhyun/DiPeO/tree/main/.claude/skills/doc-lookup
Command: npx skills add https://github.com/sorryhyun/DiPeO --skill doc-lookup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Sifting through large documentation files to find specific information is time-consuming and inefficient, especially for AI agents that incur token costs for large context windows. This skill provides a targeted way to retrieve only relevant documentation excerpts, drastically improving efficiency and reducing cognitive load.

Core Features & Use Cases

  • Anchor-Based Retrieval: Quickly locate and return specific documentation sections using explicit heading anchors (e.g., #cli-flags), ensuring the most precise results.
  • Keyword & Heading Search: Find relevant sections even if the exact anchor is unknown, using fuzzy matching on heading text and content keywords for flexible discovery.
  • Minimal Context Return: Returns only the top 1-3 most relevant sections with configurable line limits, drastically reducing token usage and providing focused context compared to loading entire documents.
  • Use Case: When a router skill needs to understand "handler patterns" for a new node, it can use doc-lookup to retrieve just that specific section from docs/agents/package-maintainer.md, providing immediate, focused context without overwhelming the agent with irrelevant information.

Quick Start

Example: Find CLI Flag Documentation

Look up CLI commands section

python .claude/skills/doc-lookup/scripts/section_search.py
--query "cli-commands"
--paths docs/agents/backend-development.md
--top 1

Frequently Asked Questions about doc-lookup

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

FAQPage Schema
How do I search documentation by specific heading or anchor without loading entire files?

Documentation lookup retrieves precise sections using explicit anchors (e.g., `#cli-flags`) or keyword matching on headings and content. It returns only the top 1-3 most relevant sections with file paths and excerpts, drastically reducing token usage compared to full-document retrieval.

Can I find documentation sections using fuzzy keyword search instead of exact anchor names?

Yes. Keyword and heading search uses fuzzy matching to locate relevant sections even without exact anchor knowledge. The skill scores content by keyword relevance and heading text similarity, returning focused excerpts that match your query.

What's the best way to reduce token costs when AI agents need targeted documentation context?

Documentation lookup minimizes context by fetching only topic-specific excerpts rather than full documents. Agents retrieve just relevant sections—like handler patterns or CLI flags—enabling efficient context windows without overwhelming token consumption.

How does anchor-based retrieval work with Markdown documentation structure?

Anchor-based retrieval parses Markdown heading structures using explicit anchors and auto-generated slugs. It matches requested anchors directly to heading text, returning the section content and file path with configurable line limits for precise, minimal excerpts.

Can documentation lookup handle multiple file paths and return ranked results?

Yes. The skill accepts multiple documentation file paths, searches across them, and ranks results by relevance. It returns the top 1-3 sections sorted by keyword and heading match strength, with full file paths and heading references for context.

What kind of documentation structures does this skill support?

The skill works with Markdown documentation featuring explicit heading anchors and keyword content. It supports flexible discovery through heading text matching and content scoring, making it compatible with standard documentation layouts without requiring special preprocessing.