Search1API
Integrations

Agent skill

Install the Search1API skill so Claude knows when to search, when to crawl, and how to tune the query — not just how to call the API.

An MCP server tells an agent what it can call. A skill tells it when and how — which is the part that actually determines whether the answers are any good.

Install

npm install -g search1api-cli
npx skills add fatwang2/search1api-cli

The skill drives the s1 CLI, so the CLI has to be installed and logged in first. If it isn't, the skill will walk the user through it.

What it changes

Without the skill, an agent with web access tends to fire one default search and paste the snippets back. The skill teaches it to adapt:

  • A URL in the conversation means crawl it, not search for it.
  • A quick factual lookup gets -n 5 and no crawling. A deep research question gets -n 15, then crawls the top 3–5 for full text.
  • Words like "latest" or "today" become -t day, rather than being typed into the query.
  • It defines end-to-end workflows — deep research, URL summarization, trending deep-dives — instead of one-shot calls.
  • It always synthesizes an answer rather than dumping raw results.

That is the difference between an agent that has a search tool and one that knows how to search.

Using it

Once installed, just talk to your agent normally:

  • "search for the latest AI news"
  • "what does this link say? https://example.com"
  • "what's trending on GitHub?"
  • "research quantum computing thoroughly"

The skill picks the command, the engine, the result count and whether to crawl.

Cost

The skill calls the same API as everything else, and spends the same credits — deep research modes crawl pages, so they cost more than a plain search. See Credits and limits.

Source: github.com/fatwang2/search1api-cli/tree/master/skills/search1api

On this page