open-websearch-maintainer

Maintain and extend the open-websearch MCP server across engine, network, tool surface, and validation categories.

Updated May 16, 2026
One-click install
npx skills add https://github.com/baiyaoshi/SmartOperationsAssistant --skill open-websearch-maintainer-baiyaoshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-websearch-maintainer
Source: https://github.com/baiyaoshi/SmartOperationsAssistant/tree/main/open-webSearch-main/skills/open-websearch-maintainer
Command: npx skills add https://github.com/baiyaoshi/SmartOperationsAssistant --skill open-websearch-maintainer-baiyaoshi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Maintain and extend 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.

Core Features & Use Cases

  • Keeps MCP tool contracts stable while evolving code paths related to engines, networking, and tests.
  • Guides risk-aware changes with focused checklists per category, minimizing unintended side effects.
  • Provides validation workflow references to ensure tests and docs stay aligned with repository behavior.

Quick Start

Start by choosing a change category (engine, network, tool surface, or validation) and load the corresponding checklist, expanding scope only when the changed code path crosses the boundary.

Frequently Asked Questions about open-websearch-maintainer

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

FAQPage Schema
How do I maintain an MCP server when updating search engines and proxy behavior?

To maintain an MCP server, apply changes only within defined categories like engine, network, or tool surface. This ensures shared networking and tool contracts remain stable while expanding scope only when the changed code path requires it.

What is the best way to extend open-websearch tool registration without breaking compatibility?

Extending tool registration requires using focused checklists for the tool surface category. This risk-aware approach minimizes unintended side effects and ensures MCP tool contracts and shared networking remain stable during live parsing behavior updates.

How do I validate MCP server changes for TLS behavior and regression?

Validating MCP server changes involves using validation workflow references to ensure tests and docs stay aligned with repository behavior. Apply changes within the validation category and expand scope only when the changed code path crosses the boundary.

Does modifying live parsing behavior in open-websearch require updating tests and docs?

Yes, modifying live parsing behavior requires updating tests and docs accordingly. Use the validation workflow references to ensure all tests and documentation stay aligned with the updated repository behavior and MCP tool contracts.

When should I not expand scope beyond the defined change categories in an MCP server?

You should not expand scope beyond defined change categories unless the changed code path requires it. Keeping changes focused within engine, network, tool surface, or validation categories minimizes unintended side effects and maintains stable MCP contracts.

Can I use risk-aware checklists to guide MCP maintenance for networking and tests?

Yes, you can use risk-aware checklists per category to guide MCP maintenance. These checklists help apply focused changes to networking and tests, ensuring MCP tool contracts and shared networking remain stable across the repository.