Add Claude and OpenAI plugin packaging (#2)

Author: fatwang2

.claude-plugin/plugin.json

@@ -0,0 +1,22 @@
+{
+  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
+  "name": "search1api",
+  "displayName": "Search1API",
+  "version": "1.0.0",
+  "description": "Search the live web, read pages, find news, discover site links, and explore trending topics.",
+  "author": {
+    "name": "Search1API",
+    "url": "https://www.search1api.com"
+  },
+  "homepage": "https://www.search1api.com/docs",
+  "repository": "https://github.com/superagents-lab/search1api-cli",
+  "license": "MIT",
+  "keywords": [
+    "search",
+    "research",
+    "news",
+    "crawl",
+    "fetch",
+    "mcp"
+  ]
+}

.codex-plugin/plugin.json

@@ -0,0 +1,45 @@
+{
+  "name": "search1api",
+  "version": "1.0.0",
+  "description": "Search the live web, read pages, find news, discover site links, and explore trending topics.",
+  "author": {
+    "name": "Search1API",
+    "url": "https://www.search1api.com"
+  },
+  "homepage": "https://www.search1api.com/docs",
+  "repository": "https://github.com/superagents-lab/search1api-cli",
+  "license": "MIT",
+  "keywords": [
+    "search",
+    "research",
+    "news",
+    "crawl",
+    "fetch",
+    "mcp"
+  ],
+  "skills": "./skills/",
+  "mcpServers": "./.mcp.json",
+  "interface": {
+    "displayName": "Search1API",
+    "shortDescription": "Search the web, read pages, and track news",
+    "longDescription": "Research the live web across multiple search and news sources, extract readable content from URLs, discover site links, and explore trending topics.",
+    "developerName": "Search1API",
+    "category": "Productivity",
+    "capabilities": [
+      "Web search",
+      "News search",
+      "Web page retrieval",
+      "Sitemap discovery",
+      "Trending topics"
+    ],
+    "websiteURL": "https://www.search1api.com",
+    "privacyPolicyURL": "https://blog.search1api.com/pages/privacy",
+    "termsOfServiceURL": "https://blog.search1api.com/pages/terms",
+    "defaultPrompt": [
+      "Research the latest developments in a topic and cite the sources.",
+      "Read this URL and summarize the key points.",
+      "Find current news about a company or technology."
+    ],
+    "brandColor": "#007BFF"
+  }
+}

.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "search1api": {
+      "type": "http",
+      "url": "https://mcp.search1api.com/mcp"
+    }
+  }
+}

README.md

@@ -165,16 +165,25 @@ s1 update
 s1 update --force   # reinstall even if already on the latest version
 ```
 
-## Claude Code Skill
+## Agent skill and plugins
 
-This repo also includes a [Claude Code](https://claude.com/claude-code) skill that lets Claude automatically use `s1` commands when you ask it to search the web, read URLs, check news, etc.
+This repo includes an Agent Skill plus plugin manifests for Claude Code and
+ChatGPT/Codex. The plugins connect to Search1API's hosted MCP server and keep
+the `s1` CLI as a fallback, so the same research workflow works across hosts.
 
-Install the skill:
+Install the standalone skill:
 
 ```bash
 npx skills add superagents-lab/search1api-cli
 ```
 
+Developers can validate or test the plugin bundle from a local clone:
+
+```bash
+claude plugin validate . --strict
+claude --plugin-dir .
+```
+
 Once installed, you can ask Claude things like:
 - "search for the latest AI news"
 - "what does this link say? https://example.com"

skills/search1api/SKILL.md

@@ -1,17 +1,24 @@
 ---
 name: search1api
 description: >
-  Powerful web search, content crawling, news, sitemap, and trending topics via the search1api CLI (s1). This is far more capable than basic fetch or search tools — it supports 13+ search engines (Google, Bing, DuckDuckGo, Reddit, GitHub, YouTube, arXiv, Baidu, X, etc.), adapts to many websites for clean content extraction, and provides news aggregation across multiple sources. Use this skill whenever the user wants to search the web, look something up, research a topic, read or summarize a URL, check news, explore a site's links, see trending topics, or check API balance. Trigger on phrases like "search for", "look up", "find out about", "what's happening with", "any news on", "what does this link say", "read this page", "summarize this URL", "trending on GitHub", or when the user shares a bare URL. Even if the user doesn't say "search" explicitly, use this skill when they clearly need web information.
+  Live web search, page retrieval, news, sitemap discovery, and trending topics through Search1API. Use this skill whenever the user wants to search the web, look something up, research a topic, read or summarize a URL, check current news, explore a site's links, see trending topics, or check API balance. Trigger on phrases like "search for", "look up", "find out about", "what's happening with", "any news on", "what does this link say", "read this page", "summarize this URL", "trending on GitHub", or when the user shares a bare URL. Prefer the bundled Search1API MCP tools when available and fall back to the search1api CLI (`s1`).
 metadata: {"openclaw": {"requires": {"bins": ["s1"]}}}
 ---
 
-# Search1API CLI
+# Search1API
 
-Web search and content retrieval via the `s1` command-line tool (`search1api-cli`).
+Live web research through the bundled Search1API MCP server or the `s1`
+command-line tool.
 
-## Prerequisites
+## Choose the available transport
 
-Before using any command, check if `s1` is available. If not, guide the user to install it:
+1. Prefer the connected Search1API MCP tools. They may be namespaced by the
+   host, but their final tool names are `search`, `fetch`, `news`, `crawl`,
+   `sitemap`, and `trending`.
+2. If the MCP tools are unavailable, check whether `s1` is installed and use
+   the matching CLI command.
+3. If neither transport is available, ask the user to connect the bundled MCP
+   server or install the CLI:
 
 ```bash
 curl -fsSL https://cli.search1api.com/install.sh | bash
@@ -23,9 +30,15 @@ Or via npm:
 npm install -g search1api-cli
 ```
 
-To update an existing install, the user can run `s1 update`. Only suggest this if a command fails in a way that looks version-related — don't run it as part of a normal search task.
+Do not install software or switch transports when a working Search1API tool is
+already available. To update an existing CLI install, the user can run
+`s1 update`. Only suggest this when a command fails in a version-related way.
 
-Authentication is also required. Prefer browser login:
+The remote MCP server handles authentication through the host's connection
+flow. If the host reports that authentication is required, ask the user to
+connect or re-authenticate Search1API.
+
+For CLI authentication, prefer browser login:
 
 ```bash
 s1 login
@@ -39,18 +52,20 @@ s1 config set-key <your-api-key>
 
 You can also set the environment variable `SEARCH1API_KEY`.
 
-If a command fails with "command not found" or an auth error, remind the user to install `s1` and run `s1 login` before retrying.
+If a CLI command fails with "command not found" or an auth error, remind the
+user to install `s1` and run `s1 login` before retrying.
 
 ## When to use
 
-| User intent | Command |
-|---|---|
-| Shares a URL / link → read and summarize | `s1 crawl <url>` |
-| Wants to search the web | `s1 search "<query>"` |
-| Wants news | `s1 news "<query>"` |
-| Wants to explore a site's links | `s1 sitemap <url>` |
-| Wants trending topics | `s1 trending <service>` |
-| Wants to check remaining credits | `s1 balance` |
+| User intent | MCP tool | CLI fallback |
+|---|---|---|
+| Shares a URL / link → read and summarize | `crawl` | `s1 crawl <url>` |
+| Wants to search the web | `search` | `s1 search "<query>"` |
+| Wants the full page behind a search result | `fetch` with its result `id` | `s1 crawl <url>` |
+| Wants news | `news` | `s1 news "<query>"` |
+| Wants to explore a site's links | `sitemap` | `s1 sitemap <url>` |
+| Wants trending topics | `trending` | `s1 trending <service>` |
+| Wants to check remaining credits | Not exposed | `s1 balance` |
 
 ## Dynamic tuning
 
@@ -62,7 +77,11 @@ Adapt parameters to user intent — don't just use defaults:
 - **Recency signals** ("latest", "recent", "this week") → `-t day` or `-t month`
 - **Domain-specific** ("search on Reddit", "find GitHub repos") → `-s reddit`, `-s github`, etc.
 - **Site-scoped** ("only from arxiv.org") → `--include arxiv.org`
-- **Chinese queries** → consider `-s baidu` for better results
+- **Chinese queries** → use `google`, `bing`, `wechat`, or `bilibili` according to intent
+
+For MCP calls, map the CLI flags above to their schema equivalents:
+`max_results`, `search_service`, `crawl_results`, `include_sites`,
+`exclude_sites`, and `time_range`.
 
 ## Commands
 
@@ -130,8 +149,8 @@ Shows remaining API credits.
 
 ### Deep research
 
-1. `s1 search "<topic>" -n 15` → get broad results
-2. `s1 crawl <url>` → crawl the top 3–5 most relevant URLs from results
+1. Use `search` (or `s1 search "<topic>" -n 15`) to get broad results
+2. Use `fetch` with result IDs (or `s1 crawl <url>`) for the top 3–5 relevant pages
 3. Synthesize all gathered content into a coherent answer with source citations
 
 ### URL summarization
@@ -147,9 +166,12 @@ Shows remaining API credits.
 
 ## Output handling
 
-- By default, commands produce human-readable formatted output
-- Add `--json` to any command for raw JSON (useful for programmatic processing)
-- After retrieving results, always **summarize and synthesize** the information for the user — don't just dump raw output
+- CLI commands produce human-readable output by default; add `--json` for
+  programmatic processing.
+- After retrieving results, summarize and synthesize the information instead
+  of dumping raw output.
+- Preserve source URLs and cite the relevant pages in the final answer.
+- Distinguish facts found in sources from your own inference.
 
 ## References