ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

open-websearch

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-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/aas-ee/open-websearch
Or

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:

  1. Detect the current state.
    • First determine whether the user needs local CLI/daemon setup, local MCP configuration, HTTP connection setup, source/build reuse, or only validation/reconnection.
  2. Choose the smallest matching path.
    • Prefer the path that reuses what already exists instead of installing a second path.
  3. Collect required inputs before doing work.
    • Confirm the target path: local CLI/daemon, existing MCP, local source/build reuse, or existing HTTP endpoint.
    • Confirm whether the environment needs npm proxy, npm mirror, or runtime proxy settings.
    • Confirm whether there is already a reusable local command, checkout, daemon, endpoint, or client config.
    • If browser-assisted mode may be needed, confirm whether Playwright, a browser binary, or a remote browser endpoint already exists.
  4. Confirm risky actions before executing them.
    • Ask before installing packages, downloading Playwright or browser binaries, editing MCP/client config, starting a long-lived daemon, or writing endpoint-related config.
Read Full Documentation on GitHub

Metadata

Author@aas-ee
Stars4473
Views0
Updated2026-05-01
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-aas-ee-open-websearch": {
      "enabled": true,
      "auto_update": true
    }
  }
}
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.

Related Skills

open-websearch

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

aas-ee 4473