Back to skills
SKILL.md
Vc Docs Seeker
ASecuritySearch library/framework documentation via llms.txt (context7.com). Use for API docs, GitHub repository analysis, technical documentation lookup, latest library features.
- 6 stars
- 0 votes
- 0 copies
- 2 views
- Added September 2, 2026
Works with
Security analysis
100/100Pro scans all 17 files and shows the line behind each finding
npx -y skills add opencue/cuecards --skill vc-docs-seeker --agent claude-codeAre you the author of Vc Docs Seeker?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/opencue-vc-docs-seeker)---
name: vc:docs-seeker
description: Search library/framework documentation via llms.txt (context7.com). Use for API docs, GitHub repository analysis, technical documentation lookup, latest library features.
argument-hint: "[library-name] [topic]"
metadata:
author: claudekit
version: "3.1.0"
---
# Documentation Discovery
## Overview
Use Context7 MCP as the default path for documentation lookup. The local scripts in this skill are fallback helpers for llms.txt-based discovery when Context7 does not cover the target cleanly.
## Primary Workflow
**Default workflow: Context7 first**
1. Resolve the library with Context7.
2. Query the exact API/config/setup question with Context7.
3. Only fall back to the scripts below when Context7 coverage is missing, incomplete, or the user explicitly wants llms.txt/repository-oriented discovery.
**Fallback script workflow:**
```bash
# 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](./workflows/topic-search.md)** - Fastest path (10-15s)
**[General Library Search](./workflows/library-search.md)** - Comprehensive coverage (30-60s)
**[Repository Analysis](./workflows/repo-analysis.md)** - Fallback strategy
## References
**[context7-patterns.md](./references/context7-patterns.md)** - URL patterns, known repositories
**[errors.md](./references/errors.md)** - Error handling, fallback strategies
**[advanced.md](./references/advanced.md)** - Edge cases, versioning, multi-language
## Execution Principles
1. **Context7 first** - Use Context7 MCP before any local script fallback
2. **Zero-token overhead** - Scripts run without context loading
3. **Automatic fallback** - Scripts handle topic → general → error chains
4. **Progressive disclosure** - Load workflows/references only when needed
5. **Scripts are fallback helpers** - Use them only when Context7 coverage is missing or the user wants llms.txt-style discovery
## Quick Start
**Topic query:** "How do I use date picker in shadcn?"
```bash
node scripts/detect-topic.js "<query>" # → {topic, library, isTopicSpecific}
node scripts/fetch-docs.js "<query>" # → 2-3 URLs
# Use Context7 results first; only use script-discovered URLs when you intentionally fall back
```
**General query:** "Documentation for Next.js"
```bash
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}
# Use Context7 results first; only use script-discovered URLs when fallback discovery is required
```
## Environment
Scripts load `.env`: `process.env` > `.Codex/skills/docs-seeker/.env` > `.Codex/skills/.env` > `.Codex/.env`
See `.env.example` for configuration options.
Files in this skill
- .env.example
- SKILL.md
- package.json
- references/advanced.md
- references/context7-patterns.md
- references/errors.md
- scripts/analyze-llms-txt.js
- scripts/detect-topic.js
- scripts/fetch-docs.js
- scripts/tests/run-tests.js
- scripts/tests/test-analyze-llms.js
- scripts/tests/test-detect-topic.js
- scripts/tests/test-fetch-docs.js
- scripts/utils/env-loader.js
- workflows/library-search.md
- workflows/repo-analysis.md
- workflows/topic-search.md
Attribution
Comments
Loading comments…