docs-seeker

Identify and synthesize technical documentation from multiple sources.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/Khoatran1999/aquarium-commerce --skill docs-seeker-khoatran1999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-seeker
Source: https://github.com/Khoatran1999/aquarium-commerce/tree/main/.claude/skills/docs-seeker
Command: npx skills add https://github.com/Khoatran1999/aquarium-commerce --skill docs-seeker-khoatran1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Documentation Seeker identifies and analyzes technical documentation from multiple sources to deliver up-to-date, comprehensive guidance for user questions across libraries, frameworks, and APIs.

Core Features & Use Cases

  • llms.txt-first discovery to locate AI-friendly docs quickly
  • Repository analysis with Repomix to extract in-repo documentation
  • Parallel exploration with Explorer agents for broad, fast coverage
  • Fallback research when sources are scattered or missing
  • Use case: quickly gather installation, API references, and examples for a new library

Quick Start

Instruct the system to locate llms.txt for the target library, then deploy parallel explorers to fetch, synthesize, and present a unified documentation report.

Frequently Asked Questions about docs-seeker

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

FAQPage Schema
How do I find technical documentation for a library using llms.txt?

To find technical documentation using llms.txt, you must specify the target library, version preferences, and a clear question. The system then locates the llms.txt file to retrieve AI-friendly docs and synthesize a unified report.

How does parallel exploration improve repository analysis for APIs?

Parallel exploration deploys multiple Explorer agents to fetch and analyze sources simultaneously. This broad coverage accelerates repository analysis, extracting in-repo documentation and cross-referencing diverse sources for comprehensive API guidance.

Can I use repository analysis when documentation is scattered or missing?

Yes, when documentation is scattered or missing, the system applies fallback research. It uses Repomix for repository analysis to extract in-repo documentation directly, ensuring you still get installation guides and API references.

What is the best way to synthesize API references from multiple sources?

The best way to synthesize API references is using llms.txt-first discovery combined with parallel exploration. This fetches, verifies, and presents a unified documentation report from diverse sources quickly.

Do I need version preferences to discover framework documentation?

Yes, providing version preferences is required to guide accurate llms.txt retrieval and repository analysis. Defining the target library and version ensures the synthesized documentation matches your environment.

Why does cross-source verification matter for library documentation?

Cross-source verification ensures technical documentation accuracy by checking facts across multiple sources. When sources are scattered, parallel exploration and fallback research validate the API references and examples before synthesis.