# Open Websearch Maintainer

Maintain and extend the open-websearch MCP server.

- 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-maintainer -g -a claude-code -y`
Codex: `npx skills add Aas-ee/open-webSearch --skill open-websearch-maintainer -g -a codex -y`
Cursor: `npx skills add Aas-ee/open-webSearch --skill open-websearch-maintainer -g -a cursor -y`
Gemini CLI: `npx skills add Aas-ee/open-webSearch --skill open-websearch-maintainer -g -a gemini-cli -y`

## Description

Maintain and extend the open-websearch MCP server. Trigger when changing search engines, proxy or TLS behavior, tool registration, live parsing behavior, or compatibility and regression behavior inside this repository.

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

# Open WebSearch Maintainer

Use this skill when modifying the `open-websearch` codebase itself.

If this skill and the current repository behavior disagree, trust the repository code, tests, and intended change scope, then update the skill or docs before finishing.

## First classify the change

- Engine change: new engine, engine parsing, engine pagination, anti-bot handling.
- Network change: proxy, TLS, request builder, Playwright interaction, browser fallback.
- Tool surface change: MCP tool registration, schema, engine normalization, config exposure.
- Validation-only change: tests, docs, or release hygiene when no code-path behavior changes are intended.

Use this classification as the execution entrypoint. Start by choosing one category, load only the checklist that matches it, and expand scope only when the changed code path actually crosses that boundary.

## Scope discipline

- Keep fixes as local as the real failure surface allows.
- Do not turn a parsing or engine-specific issue into a shared networking refactor without evidence.
- Do not widen insecure or compatibility-relaxing behavior just to make one test pass.
- Do not change tool contracts or global behavior unless the change is intentional, verified, and documented.

## Core rules

- Keep MCP tool contracts stable unless the change explicitly requires a breaking change.
- Route Axios-based networking through the shared HTTP request builder instead of ad hoc proxy handling.
- Treat proxy, TLS, and Playwright behavior as cross-cutting concerns. Verify them explicitly after changes.
- Update tests and README files when adding engines or changing behavior.

## Do not

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