open-websearch

SKILL.md

Open WebSearch

Use this as the single user-facing entry skill for open-websearch.

Assumption:

The preferred low-friction path is a working local open-websearch CLI/daemon setup.

A workspace that already exposes the open-websearch MCP tools such as search, fetchWebContent, and fetchGithubReadme is also a valid path and should continue to work.

If neither path is available, treat that as a missing open-websearch capability in the current workspace, not as a broken skill.

If the workspace tool exposure or current MCP configuration differs from this skill, trust the actually available tools and current workspace configuration.

Entry behavior

First determine whether open-websearch is already usable through a local CLI/daemon path or through workspace-exposed MCP tools.

If either path is available, use the retrieval rules below and prefer the smallest working path.

If neither path is available, explain the missing capability, state the consequence, ask whether the user wants to continue with setup or enablement, and then follow the smallest matching setup path.

Keep the line clear between not configured, setup completed but not active in this runtime, and already searched; do not imply live retrieval happened when it did not.

Treat open-websearch --help as the primary CLI reference. When command names, daemon flags, spawn behavior, or action parameters are unclear, check --help before guessing.

Setup and activation workflow