search-docs
Search local documentation in the docs/ folder for content related to a topic
Best use case
search-docs is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Search local documentation in the docs/ folder for content related to a topic
Teams using search-docs should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/search-docs/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How search-docs Compares
| Feature / Agent | search-docs | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Search local documentation in the docs/ folder for content related to a topic
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Documentation Search Use the `docs-searcher` subagent to search local documentation for content related to: **$ARGUMENTS** Call the Task tool with: - `subagent_type: "docs-searcher"` - `mode: "bypassPermissions"` - `prompt`: the search topic Report the results back to the user exactly as returned by the agent.
Related Skills
search-github
Search GitHub issues, discussions, and PRs for content related to a topic
data-designer
Use when the user wants to create a dataset, generate synthetic data, or build a data generation pipeline.
update-pr
Update an existing GitHub PR description to reflect current changes after incorporating feedback
review-code
Perform a thorough code review of the current branch or a GitHub PR by number.
create-pr
Create a GitHub PR with a well-formatted description matching the repository PR template (flat Changes by default; optional Added/Changed/Removed/Fixed grouping)
commit
Commit current changes with a clear, descriptive message
search-first
Research-before-coding workflow. Search for existing tools, libraries, and patterns before writing custom code. Systematizes the "search for existing solutions before implementing" approach. Use when starting new features or adding functionality.
market-research
Conduct market research, competitive analysis, investor due diligence, and industry intelligence with source attribution and decision-oriented summaries. Use when the user wants market sizing, competitor comparisons, fund research, technology scans, or research that informs business decisions.
exa-search
Neural search via Exa MCP for web, code, and company research. Use when the user needs web search, code examples, company intel, people lookup, or AI-powered deep research with Exa's neural search engine.
deep-research
Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any topic with evidence and citations.
microsoft-docs
Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more. Uses Microsoft Learn MCP as the default, with Context7 and Aspire MCP for content that lives outside learn.microsoft.com.
hybrid-search-implementation
Combine vector and keyword search for improved retrieval. Use when implementing RAG systems, building search engines, or when neither approach alone provides sufficient recall.