docs-seeker

Execute scripts to detect query types and retrieve documentation from context7 llms.txt.

15|27|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/kevinnguyen271090/claudekit-engineering --skill docs-seeker-kevinnguyen271090
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-seeker
Source: https://github.com/kevinnguyen271090/claudekit-engineering/tree/main/docs-seeker
Command: npx skills add https://github.com/kevinnguyen271090/claudekit-engineering --skill docs-seeker-kevinnguyen271090

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the tedious and time-consuming process of searching for technical documentation across various sources. It intelligently detects query types, fetches relevant information, and analyzes results, saving developers hours of manual research and ensuring they get the most accurate and targeted documentation.

Core Features & Use Cases

  • Intelligent Query Classification: Uses detect-topic.js to classify user queries as topic-specific or general, extracting library names and keywords for targeted searches.
  • Automated Documentation Fetching: Employs fetch-docs.js to construct and execute context7.com URLs, handling fallback chains (topic-specific → general → repository analysis) automatically.
  • Smart Result Analysis & Agent Distribution: Utilizes analyze-llms-txt.js to categorize URLs by priority (critical, important, supplementary) and recommends an optimal agent distribution strategy (single, parallel, phased) for efficient processing.
  • Use Case: A developer needs to understand "how to use date picker in shadcn/ui". This Skill will quickly identify it as a topic-specific query, fetch only the relevant documentation, and present it, avoiding a broad, time-consuming search.

Quick Start

Find documentation on 'how to use date picker in shadcn/ui'.

Frequently Asked Questions about docs-seeker

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

FAQPage Schema
How do I search technical documentation across multiple sources automatically?

Automated documentation search uses query classification to detect whether you're looking for topic-specific library docs or general information, then constructs and fetches relevant URLs from documentation sources, eliminating manual browsing across repositories and reference sites.

Can I automate finding API documentation for specific libraries?

Yes. Topic-specific query detection identifies library names and keywords in your search, automatically fetching targeted API documentation instead of broad search results, then prioritizes results by relevance level.

How does intelligent query classification work for technical documentation searches?

Query classification analyzes your input to distinguish between topic-specific searches (e.g., 'date picker in shadcn/ui') and general documentation requests, extracting library names and keywords to route your search to the most relevant documentation sources.

What happens when documentation isn't found in the primary source?

The Skill applies automatic fallback chains: if topic-specific documentation isn't available, it attempts general library documentation, then repository analysis, ensuring you get results even when primary sources lack the information.

How does this approach save time compared to manual documentation searches?

Manual searches require identifying query intent, browsing multiple sites, and filtering irrelevant results. Automated detection, URL construction, and prioritization by criticality eliminate these steps, returning targeted documentation immediately.

Can I optimize how documentation results are processed?

Yes. Result analysis categorizes URLs by priority—critical, important, supplementary—and recommends agent distribution strategies (single, parallel, or phased processing) to match your documentation volume and processing needs.