docs-seeker
Skill0 starsChanged 11 months agoMITView on GitHub
Search technical documentation using executable scripts to detect query type, fetch from llms.txt sources (context7.com), and analyze results. Use when user needs: (1) Topic-specific documentation (features/components/concepts), (2) Library/framework documentation, (3) GitHub repository analysis, (4) Documentation discovery with automated agent distribution strategy
- Reads credentials
15 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- david33137/claude-skillsedited, first seen Nov 16, 2026
- hu465/claude-skills-their own version, first seen Oct 25, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- vibe-cokit/claude-codeedited, first seen Oct 17, 2026
- Dinh2026/claudekit-skillstheir own version, first seen Oct 15, 2026
- typv/nest-turbo-starteredited, first seen Oct 8, 2026
Other versions15 projects use a version of this.
Word for word · 3
- duongthinh03/portfolio★ 85100% same
- OpenAnalystInc/10x-Team★ 8100% same
- truongtv22/theone-training-skills★ 1100% same
Edited · 4
- typv/nest-turbo-starter★ 22491% same
- vibe-cokit/claude-code★ 190% same
- david33137/claude-skills★ 063% same
- docaohieu2808/claude-skills★ 063% same
Wrote their own version · 8
- mrgoonie/claudekit-skills★ 2.2ksame name
- avibebuilder/claude-prime★ 119same name
- vneseyoungster/ChocoVine★ 27same name
- VoDaiLocz/kilo-kit-mcp★ 27same name
- davidanthonyn/claude-skills★ 0same name
- Dinh2026/claudekit-skills★ 0same name
- hu465/claude-skills-★ 0same name
- Linhv14/claude-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository31 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-multimodalSkill
- backend-developmentSkill
- better-authSkill
- chrome-devtoolsSkill
- claude-codeSkill
- code-reviewSkill
- databasesSkill
- DebuggingSkill
- devopsSkill
- frontend-design-proSkill
- frontend-designSkill
- frontend-dev-guidelinesSkill
- google-adk-pythonSkill
- mcp-builderSkill
- mcp-managementSkill
- media-processingSkill
- mobile-developmentSkill
- payment-integrationSkill
- planningSkill
- Problem-Solving TechniquesSkill
- repomixSkill
- researchSkill
- sequential-thinkingSkill
- shopifySkill
- skill-creatorSkill
- template-skillSkill
- threejsSkill
- ui-stylingSkill
- ui-ux-pro-maxSkill
- web-frameworksSkill
The file
Files
Documentation Discovery via Scripts
Overview
Script-first documentation discovery using llms.txt standard.
Execute scripts to handle entire workflow - no manual URL construction needed.
Primary Workflow
ALWAYS execute scripts in this order:
# 1. DETECT query type (topic-specific vs general)
node scripts/detect-topic.js "<user query>"
# 2. FETCH documentation using script output
node scripts/fetch-docs.js "<user query>"
# 3. ANALYZE results (if multiple URLs returned)
cat llms.txt | node scripts/analyze-llms-txt.js -Scripts handle URL construction, fallback chains, and error handling automatically.
Scripts
detect-topic.js - Classify query type
- Identifies topic-specific vs general queries
- Extracts library name + topic keyword
- Returns JSON:
{topic, library, isTopicSpecific} - Zero-token execution
fetch-docs.js - Retrieve documentation
- Constructs context7.com URLs automatically
- Handles fallback: topic → general → error
- Outputs llms.txt content or error message
- Zero-token execution
analyze-llms-txt.js - Process llms.txt
- Categorizes URLs (critical/important/supplementary)
- Recommends agent distribution (1 agent, 3 agents, 7 agents, phased)
- Returns JSON with strategy
- Zero-token execution
Workflow References
Topic-Specific Search - Fastest path (10-15s)
General Library Search - Comprehensive coverage (30-60s)
Repository Analysis - Fallback strategy
References
context7-patterns.md - URL patterns, known repositories
errors.md - Error handling, fallback strategies
advanced.md - Edge cases, versioning, multi-language
Execution Principles
- Scripts first - Execute scripts instead of manual URL construction
- Zero-token overhead - Scripts run without context loading
- Automatic fallback - Scripts handle topic → general → error chains
- Progressive disclosure - Load workflows/references only when needed
- Agent distribution - Scripts recommend parallel agent strategy
Quick Start
Topic query: "How do I use date picker in shadcn?"
node scripts/detect-topic.js "<query>" # → {topic, library, isTopicSpecific}
node scripts/fetch-docs.js "<query>" # → 2-3 URLs
# Read URLs with WebFetchGeneral query: "Documentation for Next.js"
node scripts/detect-topic.js "<query>" # → {isTopicSpecific: false}
node scripts/fetch-docs.js "<query>" # → 8+ URLs
cat llms.txt | node scripts/analyze-llms-txt.js - # → {totalUrls, distribution}
# Deploy agents per recommendationEnvironment
Scripts load .env: process.env > .claude/skills/docs-seeker/.env > .claude/skills/.env > .claude/.env
See .env.example for configuration options.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

