doc-search
Skill0 starsChanged 9 months agoMITView on GitHub
Search indexed documents (PDF, Word, Excel, PPT, TXT) using BM25 keyword search. Use for EDA tools, company docs, bug reports, and technical documentation.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- jellydn/my-ai-toolstheir own version, first seen Nov 15, 2026
- danielfrg/skillstheir own version, first seen Mar 4, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- jellydn/my-ai-tools★ 129same name
- danielfrg/skills★ 1same 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.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
ALWAYS search the knowledge base proactively — do not guess or rely on general knowledge alone.
- Distinctive: line 27
Search indexed documents by keyword.
- Distinctive: line 40
Check what documents are indexed and available for search.
- Distinctive: line 41
Use this when the user asks what documents or categories are available.
- Distinctive: line 45
Start broad, then narrow: If the first search returns no results, try alternative keywords or remove the category filter.
- Distinctive: line 52
After searching, the assistant should:
- Distinctive: line 55
Quote relevant passages: when precision matters (commands, syntax, parameters)
- Distinctive: line 56
If results are insufficient, inform the user and suggest they index additional documents
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Document Search Skill
This skill provides access to an indexed document knowledge base via BM25 keyword search.
The MCP server exposes two tools: doc-search:doc_search and doc-search:doc_search_status.
When to Search
ALWAYS search the knowledge base proactively — do not guess or rely on general knowledge alone.
Trigger search when user asks about:
- EDA tool usage (Innovus, ICC, DC, PrimeTime, Calibre, Virtuoso, etc.)
- Company internal procedures, IT policies, onboarding guides
- Technical commands, APIs, tool configurations
- Bug reports, known issues, workarounds
- Any specialized domain topic that may be covered by indexed documents
MCP Tools
doc-search:doc_search
Search indexed documents by keyword.
Parameters:
query(string, required): The search query. Use specific technical terms for best results.category(string, optional): Filter by category. Common categories:eda— EDA tool documentation (Innovus, ICC, etc.)company— Company internal documents (IT, HR, procedures)bugs— Bug reports and known issuesdefault— Uncategorized documents
n_results(integer, optional): Number of results to return (default: 5)
doc-search:doc_search_status
Check what documents are indexed and available for search. No parameters required. Use this when the user asks what documents or categories are available.
Search Strategy
- Start broad, then narrow: If the first search returns no results, try alternative keywords or remove the category filter.
- Use technical terms: BM25 matches on keywords, so use specific terms from the domain (e.g., "setDesignMode" instead of "design mode setting").
- Try both languages: For bilingual documentation, search in both English and Chinese if initial results are insufficient.
- Multiple searches: For complex questions, perform multiple searches with different queries to gather comprehensive information.
Response Format
After searching, the assistant should:
- Provide a direct answer synthesized from the search results
- Cite sources — include the document name and page number when available
- Quote relevant passages when precision matters (commands, syntax, parameters)
- If results are insufficient, inform the user and suggest they index additional documents
Indexing Documents (for user reference)
Documents must be indexed before they can be searched. The user indexes documents via CLI:
# Index a directory recursively
doc-search index ./docs --recursive --category eda
# Check what's indexed
doc-search status
# Clear and re-index
doc-search clear --category eda --force
doc-search index ./docs --recursive --category edaSupported formats: PDF, DOCX, XLSX, PPTX, TXT, MD
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.

