MCPInstall

open-websearch-maintainer

by aas-eeBackend & APIs

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.

Installs
40
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/aas-ee/open-websearch --skill open-websearch-maintainer
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads open-websearch-maintainer automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

  • Do not bypass the shared HTTP request builder for a one-off engine fix.
  • Do not silently fork proxy behavior in a single engine unless the repository explicitly adopts that policy.
  • Do not widen insecure TLS behavior beyond the narrow code path that requires it.
  • Do not change tool contracts without checking tests, config handling, and README files.
  • Do not touch shared networking code if the change is only about result parsing or docs.

Change checklist

When adding or changing a search engine:

  • update src/config.ts
  • update src/tools/setupTools.ts
  • add or update engine tests
  • update README.md and README-zh.md

When changing network behavior:

  • prefer src/utils/httpRequest.ts
  • keep proxy: false behavior explicit for Axios
  • keep insecure TLS opt-in and scoped only where necessary

Validation

  • Run TypeScript checks first.
  • Run targeted tests for the touched area.
  • Run live tests when the change depends on real network behavior.

Review focus

  • pagination and empty-result handling
  • anti-bot / verification page detection
  • proxy interactions with USE_PROXY and PROXY_URL
  • request-mode versus Playwright-mode behavior
  • documentation drift

Read references/workflow.md when implementing changes and references/validation.md before finalizing a patch.

FAQ

What does the open-websearch-maintainer skill do?

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.

How do I install open-websearch-maintainer?

Run npx skills add https://github.com/aas-ee/open-websearch --skill open-websearch-maintainer in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/open-websearch-maintainer/ (personal) or .claude/skills/open-websearch-maintainer/ (project).

Which AI agents can use open-websearch-maintainer?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is open-websearch-maintainer safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains open-websearch-maintainer?

It is published by aas-ee in aas-ee/open-websearch. It has 40 recorded installs.

More from aas-ee/open-websearch

View all →

open-websearch

aas-ee/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.

AI & Agents2.3K installs

Popular backend & apis skills

View category →

find-skills

vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

OfficialBackend & APIs4.1M installs

entra-app-registration

microsoft/azure-skills

Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.

OfficialBackend & APIs566.7K installs

google-agents-cli-adk-code

google/agents-cli

This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).

Backend & APIs514.8K installs

embedded-captions

heygen-com/hyperframes

Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.

Backend & APIs453.3K installs

entra-agent-id

microsoft/azure-skills

Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).

OfficialBackend & APIs336.6K installs

neon

neondatabase/agent-skills

Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.

Backend & APIs237.1K installs