open-websearch

Bridge local open-websearch CLI/daemon with workspace MCP tools for web retrieval.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a single, cohesive entry for performing live web search and content retrieval by harmonizing a local open-websearch CLI/daemon with workspace MCP tools, enabling seamless fallback when the local path is unavailable.

Core Features & Use Cases

  • Local CLI/daemon-first operation to start or connect a retrieval workflow with minimal friction.
  • MCP-compatible pathways to leverage workspace-exposed tools like search, fetchWebContent, and fetchGithubReadme when a local daemon is not ready.
  • Safe, guided setup with capability detection, fallback routing, and explicit activation states.

Quick Start

Run open-websearch locally or connect to the workspace MCP tools to begin focused web retrieval.

Frequently Asked Questions about open-websearch

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

FAQPage Schema
How do I perform live web search directly from my local CLI?

Live web search is performed by running the local open-websearch CLI or daemon, which enables retrieval workflows with minimal friction. The system detects local capabilities first and prefers this direct path for fetching public web content.

What happens if my local web search daemon is not running or fails to connect?

When the local daemon is unavailable, the system gracefully guides you through fallback routing to MCP-compatible pathways. It leverages workspace-exposed tools like search, fetchWebContent, and fetchGithubReadme to maintain retrieval functionality.

Can I use MCP tools to fetch a GitHub README and web content?

Yes, MCP-compatible pathways allow you to leverage workspace-exposed tools like fetchWebContent and fetchGithubReadme. This enables unified retrieval of live web results and public GitHub content when integrated within an MCP-enabled workspace.

Do I need to manually configure routing between my local daemon and MCP tools?

No manual routing configuration is needed. The system automatically enforces capability detection, validates readiness, and explicitly manages activation states to seamlessly switch between local paths and MCP tools during web retrieval.

What is the best way to unify live web search and content retrieval workflows?

The best way to unify live web search is bridging a local open-websearch CLI with workspace MCP tools. This approach harmonizes direct daemon access and MCP-exposed fetch capabilities, ensuring continuous retrieval with safe fallback routing.