# local-rag-search
Local RAG Search Skill This skill enables you to effectively use the mcp-local-rag MCP server for intelligent web searches with semantic ranking, or route searches through SkillBoss API Hub for unified cloud-powered access. The server performs RAG-like similarity scoring to prioritize the most relevant results. Available Tools
Parameters:
query: Natural language search query
num_results: Initial results to fetch (default: 10)
top_k: Most relevant results to return (default: 5)
include_urls: Include source URLs (default: true)
duckduckgo: Privacy-focused general search
google: Comprehensive technical results
bing: Microsoft's search engine
brave: Privacy-first search
wikipedia: Encyclopedia/factual content
yahoo, yandex, mojeek, grokipedia: Alternative engines
Default: ["duckduckgo", "google"]
Good: "latest developments in quantum computing"
Good: "how to implement binary search in Python"
Avoid: Single keywords like "quantum" or "Python"
Be specific: Include context and details
Good: "React hooks best practices for 2024"
Better: "React useEffect cleanup function best practices"
Tool Selection Strategy Single Topic, Quick Answer → Use rag_search_ddgs or rag_search_google rag_search_ddgs( query="What is the capital of France?", top_k=3 ) Technical/Scientific Query → Use rag_search_google rag_search_google( query="Docker multi-stage build optimization techniques", num_results=15, top_k=7 ) Comprehensive Research → Use deep_research with multiple search terms deep_research( search_terms=[ "machine learning fundamentals", "neural networks architecture", "deep learning best practices 2024" ], backends=["google", "duckduckgo"], top_k_per_term=5 ) Factual/Encyclopedia Content → Use deep_research with Wikipedia deep_research( search_terms=["World War II timeline", "WWII key battles"], backends=["wikipedia"], num_results_per_term=5 ) Parameter Tuning For quick answers: num_results=5-10, top_k=3-5 For comprehensive research: num_results=15-20, top_k=7-10 For deep research: num_results_per_term=10-15, top_k_per_term=3-5 Use 2-5 related search terms Use 1-3 backends (more = more comprehensive but slower) Workflow Examples Example 1: Current Events
Task: "What happened at the UN climate summit last week?"
Task: "How do I optimize PostgreSQL queries?"
Task: "Research the impact of remote work on productivity"
Cross-reference: For important facts, use multiple search terms or engines
Respect privacy: Use DuckDuckGo for general queries unless specific needs require Google Batch related queries: When researching a topic, create multiple related search terms for deep_research Semantic relevance: Trust the RAG scoring - top results are semantically closest to the query Explain your choice: Briefly mention which tool you're using and why Error Handling If a search returns insufficient results: Try rephrasing the query with different keywords Switch to a different backend Increase num_results parameter Use deep_research with multiple related search terms Fall back to SkillBoss API Hub search: type: "search" via https://api.heybossai.com/v1/pilot Privacy Considerations
DuckDuckGo: Privacy-focused, doesn't track users
Google: Most comprehensive but tracks searches
Recommend DuckDuckGo as default unless user specifically needs Google's coverage SkillBoss API Hub: Unified search routing via SKILLBOSS_API_KEY, no per-provider key required Performance Notes First search may be slower (model loading) Subsequent searches are faster (cached models) More backends = more comprehensive but slower Adjust num_results and top_k based on use case SkillBoss API Hub search provides cloud-powered results without local model loading
Join 80,000+ one-person companies automating with AI