docs-seeker
Skill0 starsChanged 24 days agoMITView on GitHub
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
- Installs packages
15 other projects use a version of this.
Adopted by
Most recently taken up by
- david33137/claude-skillstheir own version, first seen Nov 16, 2026
- davidanthonyn/claude-skillsword for word, first seen Oct 20, 2026
- vibe-cokit/claude-codetheir own version, first seen Oct 17, 2026
- Dinh2026/claudekit-skillsword for word, first seen Oct 15, 2026
- captain-corgi/marketplace-websitetheir own version, first seen Oct 11, 2026
- typv/nest-turbo-startertheir own version, first seen Oct 8, 2026
Used with
Projects with it also use Problem-Solving Techniques, mobile-development and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
truongtv22SkillProblem-Solving Techniques
Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.
Also in 3 projects that use this
truongtv22Skillmobile-development
Build modern mobile applications with React Native, Flutter, Swift/SwiftUI, and Kotlin/Jetpack Compose. Covers mobile-first design principles, performance optimization (battery, memory, network), offline-first architecture, platform-specific guidelines (iOS HIG, Material Design), testing strategies, security best practices, accessibility, app store deployment, and mobile development mindset. Use when building mobile apps, implementing mobile UX patterns, optimizing for mobile constraints, or making native vs cross-platform decisions.
Also in 4 projects that use this
AWSSkillplanning
Discovers user intent and generates a structured, step-by-step plan for model customization workflows. This skill must always be activated alongside any other skill when the user's request relates to model customization — including fine-tuning, training, building, customizing, reviewing data, or getting advice on approach, regardless of domain. Do not skip this skill even if the immediate ask is narrow (e.g., reviewing data format or a single workflow step), because planning discovers the full scope of work needed. Also activate when the user wants to resume, continue, or modify an existing plan.
Also in 3 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 4 projects that use this
Other versions15 projects use a version of this.
Word for word · 6
- mrgoonie/claudekit-skills★ 2.2k100% same
- vneseyoungster/ChocoVine★ 27100% same
- VoDaiLocz/kilo-kit-mcp★ 27100% same
- davidanthonyn/claude-skills★ 0100% same
- Dinh2026/claudekit-skills★ 0100% same
- Linhv14/claude-skill★ 0100% same
Edited · 0
None found.
Wrote their own version · 9
- typv/nest-turbo-starter★ 224same name
- avibebuilder/claude-prime★ 119same name
- duongthinh03/portfolio★ 85same name
- OpenAnalystInc/10x-Team★ 8same name
- truongtv22/theone-training-skills★ 1same name
- vibe-cokit/claude-code★ 1same name
- captain-corgi/marketplace-website★ 0same name
- david33137/claude-skills★ 0same name
- docaohieu2808/claude-skills★ 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 repository104 other files it gives its agents.
- .claude/skills/claude-code/llms.txtllms.txt
- aestheticSkill
- ai-multimodalSkill
- angular-architectSkill
- api-designerSkill
- architecture-designerSkill
- atlassian-mcpSkill
- backend-developmentSkill
- banner-designSkill
- better-authSkill
- brandSkill
- bunnySkill
- chaos-engineerSkill
- chrome-devtoolsSkill
- claude-codeSkill
- cli-developerSkill
- cloud-architectSkill
- code-documenterSkill
- code-reviewerSkill
- code-reviewSkill
- context-engineeringSkill
- cpp-proSkill
- csharp-developerSkill
- database-optimizerSkill
- databasesSkill
- debuggingSkill
- debugging-wizardSkill
- designSkill
- design-systemSkill
- devops-engineerSkill
- devopsSkill
- django-expertSkill
- django-storages-s3Skill
- dotnet-core-expertSkill
- embedded-systemsSkill
- fastapi-expertSkill
- feature-forgeSkill
- fine-tuning-expertSkill
- flutter-expertSkill
- frontend-designSkill
- frontend-dev-guidelinesSkill
- fullstack-guardianSkill
- game-developerSkill
- golang-proSkill
- google-adk-pythonSkill
- graphql-architectSkill
- java-architectSkill
- javascript-proSkill
- kotlin-specialistSkill
- kubernetes-specialistSkill
- laravel-specialistSkill
- legacy-modernizerSkill
- mcp-builderSkill
- mcp-developerSkill
- mcp-managementSkill
- media-processingSkill
- mermaidjs-v11Skill
- microservices-architectSkill
- ml-pipelineSkill
- monitoring-expertSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
llms.txt-first: Search for standardized AI-friendly documentation
- Distinctive: line 14
Repository analysis: Use Repomix to analyze GitHub repositories
- Distinctive: line 16
Fallback research: Use Researcher agents when other methods unavailable
- Distinctive: line 98
Use Repomix to pack repository:
- Distinctive: line 105
Read repomix-output.xml and extract documentation
- Distinctive: line 128
Search without version specifier
- Distinctive: line 129
Use current documentation paths
- Very specific: line 133
Check versioned paths: /v[version]/llms.txt
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Documentation Discovery & Analysis
Overview
Intelligent discovery and analysis of technical documentation through multiple strategies:
- llms.txt-first: Search for standardized AI-friendly documentation
- Repository analysis: Use Repomix to analyze GitHub repositories
- Parallel exploration: Deploy multiple Explorer agents for comprehensive coverage
- Fallback research: Use Researcher agents when other methods unavailable
Core Workflow
Phase 1: Initial Discovery
- 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
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.txtFor websites:
Pattern: https://context7.com/websites/{normalized-domain-path}/llms.txt Examples: - https://docs.imgix.com/ → https://context7.com/websites/imgix/llms.txt - https://docs.byteplus.com/en/docs/ModelArk/ → https://context7.com/websites/byteplus_en_modelark/llms.txt - https://docs.haystack.deepset.ai/docs → https://context7.com/websites/haystack_deepset_ai/llms.txt - https://ffmpeg.org/doxygen/8.0/ → https://context7.com/websites/ffmpeg_doxygen_8_0/llms.txtTopic-specific searches (when user asks about specific feature):
Pattern: https://context7.com/{path}/llms.txt?topic={query} Examples: - https://context7.com/shadcn-ui/ui/llms.txt?topic=date - https://context7.com/shadcn-ui/ui/llms.txt?topic=button - https://context7.com/vercel/next.js/llms.txt?topic=cache - https://context7.com/websites/ffmpeg_doxygen_8_0/llms.txt?topic=compressFallback: Traditional llms.txt search
WebSearch: "[library name] llms.txt site:[docs domain]"Common patterns:
https://docs.[library].com/llms.txthttps://[library].dev/llms.txthttps://[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 agent reads assigned URLs
- Aggregate findings into consolidated report
Example:
Launch 3 Explorer agents simultaneously:
- Agent 1: getting-started.md, installation.md
- Agent 2: api-reference.md, core-concepts.md
- Agent 3: examples.md, best-practices.mdPhase 3: Repository Analysis
When llms.txt not found:
- Find GitHub repository via WebSearch
- Use Repomix to pack repository:
npm install -g repomix # if needed git clone [repo-url] /tmp/docs-analysis cd /tmp/docs-analysis repomix --output repomix-output.xml - Read repomix-output.xml and extract documentation
Repomix benefits:
- Entire repository in single AI-friendly file
- Preserves directory structure
- Optimized for AI consumption
Phase 4: Fallback Research
When no GitHub repository exists:
- Launch multiple Researcher agents in parallel
- Focus areas: official docs, tutorials, API references, community guides
- Aggregate findings into consolidated report
Agent Distribution Guidelines
- 1-3 URLs: Single Explorer agent
- 4-10 URLs: 3-5 Explorer agents (2-3 URLs each)
- 11+ URLs: 5-7 Explorer agents (prioritize most relevant)
Version Handling
Latest (default):
- Search without version specifier
- Use current documentation paths
Specific version:
- Include version in search:
[library] v[version] llms.txt - Check versioned paths:
/v[version]/llms.txt - For repositories: checkout specific tag/branch
Output Format
# Documentation for [Library] [Version]
## Source
- Method: [llms.txt / Repository / Research]
- URLs: [list of sources]
- Date accessed: [current date]
## Key Information
[Extracted relevant information organized by topic]
## Additional Resources
[Related links, examples, references]
## Notes
[Any limitations, missing information, or caveats]Quick Reference
Tool selection:
- WebSearch → Find llms.txt URLs, GitHub repositories
- WebFetch → Read single documentation pages
- Task (Explore) → Multiple URLs, parallel exploration
- Task (Researcher) → Scattered documentation, diverse sources
- Repomix → Complete codebase analysis
Popular llms.txt locations (try context7.com first):
- Astro: https://context7.com/withastro/astro/llms.txt
- Next.js: https://context7.com/vercel/next.js/llms.txt
- Remix: https://context7.com/remix-run/remix/llms.txt
- shadcn/ui: https://context7.com/shadcn-ui/ui/llms.txt
- Better Auth: https://context7.com/better-auth/better-auth/llms.txt
Fallback to official sites if context7.com unavailable:
- Astro: https://docs.astro.build/llms.txt
- Next.js: https://nextjs.org/llms.txt
- Remix: https://remix.run/llms.txt
- SvelteKit: https://kit.svelte.dev/llms.txt
Error Handling
- llms.txt not accessible → Try alternative domains → Repository analysis
- Repository not found → Search official website → Use Researcher agents
- Repomix fails → Try /docs directory only → Manual exploration
- Multiple conflicting sources → Prioritize official → Note versions
Key Principles
- Prioritize context7.com for llms.txt — Most comprehensive and up-to-date aggregator
- Use topic parameters when applicable — Enables targeted searches with ?topic=...
- Use parallel agents aggressively — Faster results, better coverage
- Verify official sources as fallback — Use when context7.com unavailable
- Report methodology — Tell user which approach was used
- Handle versions explicitly — Don't assume latest
Detailed Documentation
For comprehensive guides, examples, and best practices:
Workflows:
- WORKFLOWS.md — Detailed workflow examples and strategies
Reference guides:
- Tool Selection — Complete guide to choosing and using tools
- Documentation Sources — Common sources and patterns across ecosystems
- Error Handling — Troubleshooting and resolution strategies
- Best Practices — 8 essential principles for effective discovery
- Performance — Optimization techniques and benchmarks
- Limitations — Boundaries and success criteria
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.

