Agent skill · Documentation

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

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill docs-seeker-agentgptsmith-monadframework --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.0.0
Path: skills/analysis/docs-seeker-agentgptsmith-monadframework/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 - Identify if target is GitHub repository or website 2. **Search for llms.txt (PRIORITIZE context7.com)** **First: Try context7.com patterns** For GitHub repositories: ``` Pattern: https://context7.com/{org}/{repo}/llms.txt Examples: - https://github.com/imagick/imagick → https://context7.com/imagick/imagick/llms.txt - https://github.com/vercel/next.js → https://context7.com/vercel/next.js/llms.txt - https://github.com/better-auth/better-auth → https://context7.com/better-auth/better-auth/llms.txt ``` For websites: ``` Pattern: https://context7.c

What's inside
Steps it walks through
  1. Overview
  2. Core Workflow
  3. Phase 1: Initial Discovery
  4. Phase 2: llms.txt Processing
  5. Phase 3: Repository Analysis
  6. Phase 4: Fallback Research
  7. Agent Distribution Guidelines
  8. Version Handling
  9. Output Format
  10. Quick Reference
  11. Error Handling
  12. Key Principles
  13. Detailed Documentation
Ships with 1 file
  • metadata.json
Commands it runs
npm install -g repomix  # if needed
git clone [repo-url] /tmp/docs-analysis
cd /tmp/docs-analysis
repomix --output repomix-output.xml
More from claude-skill-registry
All skills →
About this skill
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-agentgptsmith-monadframework --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.

Keep going