# Open Websearch

Single entry skill for open-websearch setup and focused live retrieval, preferring...

- Repository: https://github.com/Aas-ee/open-webSearch (1892 stars)
- Category: AI and agents
- License: Apache-2.0
- Last updated: 2026-10-08
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Aas-ee/open-webSearch --skill open-websearch -g -a claude-code -y`
Codex: `npx skills add Aas-ee/open-webSearch --skill open-websearch -g -a codex -y`
Cursor: `npx skills add Aas-ee/open-webSearch --skill open-websearch -g -a cursor -y`
Gemini CLI: `npx skills add Aas-ee/open-webSearch --skill open-websearch -g -a gemini-cli -y`

## Description

Single entry skill for open-websearch setup and focused live retrieval, preferring local CLI/daemon paths while remaining compatible with workspace-exposed MCP tools.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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

1. First determine whether `open-websearch` is already usable through a local CLI/daemon path or through workspace-exposed MCP tools.
2. If either path is available, use the retrieval rules below and prefer the smallest working path.
3. 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.
4. 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.
5. 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

When capability is missing, follow this order:

The rest: https://github.com/Aas-ee/open-webSearch/blob/HEAD/skills/open-websearch/SKILL.md