docs-seeker
Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration. Use when user needs: (1) Latest documentation for libraries/frameworks, (2) Documentation in llms.txt format, (3) GitHub repository analysis, (4) Documentation without direct llms.txt support, (5) Multiple documentation sources in parallel
npx skills add majiayu000/claude-skill-registry --skill docs-seeker-alex-tgk-saasquatch --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Documentation Discovery & Analysis ## Overview Intelligent discovery and analysis of technical documentation through multiple strategies: 1. **llms.txt-first**: Search for standardized AI-friendly documentation 2. **Repository analysis**: Use Repomix to analyze GitHub repositories 3. **Parallel exploration**: Deploy multiple Explorer agents for comprehensive coverage 4. **Fallback research**: Use Researcher agents when other methods unavailable ## Core Workflow ### Phase 1: Initial Discovery 1. **Identify target** - Extract library/framework name from user request - Note version requirements (default: latest) - Clarify scope if ambiguous 2. **Search for llms.txt** ``` WebSearch: "[library name] llms.txt site:[docs domain]" ``` Common patterns: - `https://docs.[library].com/llms.txt` - `https://[library].dev/llms.txt` - `https://[library].io/llms.txt` → Found? Proceed to Phase 2 → Not found? Proceed to Phase 3 ### Phase 2: llms.txt Processing **Single URL:** - WebFetch to retrieve content - Extract and present information **Multiple URLs (3+):** - **CRITICAL**: Launch multiple Explorer agents in parallel - One agent per major documentation section (max 5 in first batch) - Each age
- Overview
- Core Workflow
- Phase 1: Initial Discovery
- Phase 2: llms.txt Processing
- Phase 3: Repository Analysis
- Phase 4: Fallback Research
- Agent Distribution Guidelines
- Version Handling
- Output Format
- Quick Reference
- Error Handling
- Key Principles
- Detailed Documentation
npm install -g repomix # if needed git clone [repo-url] /tmp/docs-analysis cd /tmp/docs-analysis repomix --output repomix-output.xml
What does the docs-seeker skill do?
Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration. Use when user needs: (1) Latest documentation for libraries/frameworks, (2) Documentation in llms.txt format, (3) GitHub repository analysis, (4) Documentation without direct llms.txt support, (5) Multiple documentation sources in parallel
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill docs-seeker-alex-tgk-saasquatch --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.