open-websearch

Prefer local open-websearch CLI/daemon paths for web retrieval with MCP tool compatibility.

Updated May 16, 2026
One-click install
npx skills add https://github.com/baiyaoshi/SmartOperationsAssistant --skill open-websearch-baiyaoshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-websearch
Source: https://github.com/baiyaoshi/SmartOperationsAssistant/tree/main/open-webSearch-main/skills/open-websearch
Command: npx skills add https://github.com/baiyaoshi/SmartOperationsAssistant --skill open-websearch-baiyaoshi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a single entry point for open-websearch, prioritizing a local CLI/daemon path while staying compatible with workspace-exposed MCP tools to enable focused live retrieval.

Core Features & Use Cases

  • Unified entry point for quick activation and consistent guidance across local and MCP-bound workspaces.
  • Path minimization by preferring the smallest viable runtime path (local CLI/daemon, then MCP tools) for activation.
  • Flexible retrieval supporting search, fetchWebContent, and fetchGithubReadme across local and workspace contexts.

Quick Start

Confirm a usable local open-websearch path (CLI/daemon) or workspace MCP tools, then perform a minimal smoke check to verify readiness.

Frequently Asked Questions about open-websearch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up local-first web retrieval using a CLI or daemon?

You can set up local-first web retrieval by preferring a local open-websearch CLI/daemon path, staying compatible with workspace-exposed MCP tools, and performing a minimal smoke check to verify readiness before searching.

Can I use MCP tools for web search when a local daemon is unavailable?

Yes, MCP tools support web search when a local daemon is unavailable. The Skill stays compatible with workspace-exposed MCP tools, allowing you to execute search, fetchWebContent, and fetchGithubReadme actions directly.

What is the best way to minimize runtime paths for web search and fetching?

The best way to minimize runtime paths for web search is by preferring the smallest viable local CLI/daemon path over workspace-exposed MCP tools. This path minimization enables fast validation and focused live retrieval.

What specific web retrieval actions are exposed by local CLI and MCP tools?

The specific web retrieval actions exposed by the Skill include search, fetchWebContent, and fetchGithubReadme. These allowed-tools enable focused live retrieval across local and workspace contexts.

Do I need a local open-websearch path to fetch GitHub READMEs and web content?

No, you do not need a local open-websearch path if your environment provides workspace-exposed MCP tools. The setup enables fetchGithubReadme and fetchWebContent across both local and MCP-bound workspaces.

Why does my web search setup require a smoke check before live retrieval?

A smoke check is required before live retrieval to verify that a usable local open-websearch path or workspace MCP tools exist. This ensures minimal risk, clear capability states, and explicit activation for fetch actions.