docs-seeker

Aggregate technical documentation from llms.txt sources and GitHub repositories via Repomix.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

docs-seeker helps users locate, compare, and synthesize technical documentation from llms.txt sources, repository content via Repomix, and parallel exploration to deliver a unified understanding.

Core Features & Use Cases

  • llms.txt discovery and processing
  • Repository analysis via Repomix when llms.txt is absent
  • Parallel exploration with multiple sources for thorough coverage
  • Version-aware verification and cross-source validation
  • Use cases include migrating docs, comparing versions, and aggregating API references

Quick Start

Instruct the AI to locate the latest llms.txt for the target library, run parallel exploration across sources, and synthesize 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 aggregate technical documentation from fragmented sources for a unified understanding?

To synthesize multi-source documentation, the system discovers official llms.txt files, analyzes GitHub repositories via Repomix, and runs parallel exploration to output a unified, cross-referenced report.

What is the best way to find library documentation when a repository lacks an llms.txt file?

When llms.txt is absent, the system uses Repomix to directly analyze repository content, enforcing source discovery and fallback strategies to extract and synthesize the required technical documentation.

Can I compare and verify API references across different versions using multi-source exploration?

Yes, you can compare API references across versions. The process enforces version alignment and cross-source validation during parallel exploration, delivering version-aware reporting for accurate verification.

Does docs-seeker work with any GitHub repository or only those with llms.txt present?

It works with both. It processes llms.txt sources when present, and falls back to analyzing repository content via Repomix for repositories lacking llms.txt, ensuring comprehensive multi-source coverage.

How do I handle version misalignment when synthesizing documentation from multiple sources?

To handle version misalignment, the synthesis process enforces version-aware verification and cross-source validation, applying error handling and fallback strategies to ensure the aggregated documentation matches the target version.