SuperAPI AI Directory

smart-search

General & other

View repository

Updated 10-15 23:41

About this skill

Intelligent Search Router

Route the query to the best opencli search source based on the topic and scenario. The core goal of this skill is not to memorize commands, but to first locate the data source, and then let the Agent read live help on its own through opencli to avoid documentation drift.

Mandatory Pre-check

Before each use, you must first do the following two steps:

  • Run opencli list -f yaml
  • Use the live registry to confirm whether the candidate site exists, and check strategy、browser、domain

After selecting a site, you must then do the following two steps:

  • Run opencli <site> -h to view which subcommands the site has
  • If a subcommand has been locked in, then run opencli <site> <command> -h to view parameters, output columns, and policies

Do not hard-code parameters or assume command signatures in the skill documentation; rely on the live output of opencli ... -h .

Main Routing Rules

Use only this one rule, and no longer maintain multiple sets of priorities:

  1. When the user explicitly specifies a website, platform, or data source, directly use the corresponding website.
  2. When the user does not specify a website, prefer selecting only one AI source:grok、doubao、gemini choose one of three.
  3. When the content returned by the AI is insufficient, lacks raw data, needs authoritative corroboration, or needs vertical results, then supplement with 1-2 dedicated sources.

Per-question Budget and Rate Limits

Understand a "single user question" as one problem-solving instance under the same intent chain; in the same round of follow-up questions, clarifications, or additional conditions, if the core question has not changed, it still counts as the same question.

First establish a site invocation ledger. After each actual execution of a search command, update it immediately:

  • site
  • query
  • count
  • status

Counting rules:

  • opencli list -f yaml、opencli <site> -h、opencli <site> <command> -h belongs to pre-check and help, and is not counted toward the search count
  • One actual opencli <site> ... search/query execution counts as 1 invocation for that site
  • If the same site fails due to an error, timeout, CAPTCHA, anti-scraping measures, or an abnormal login state, it also counts as 1 invocation; do not retry indefinitely

Rate upper limits:

  • Hard limit for AI sites: within the same question, each AI site can be invoked at most 1 time
  • The default strategy is still to select only 1 AI site; do not string multiple AI sites together into a routine process
  • Only when the user explicitly requests a comparison of multiple AI sites may other AI sites be additionally invoked; but each named AI site is still limited to at most 1 time
  • Non-AI sites are by default invoked at most 2 times
  • The second invocation of a non-AI site must have a clear reason, for example the first result was too broad and needs to be narrowed by time, region, category, sorting, or keywords
  • Do not make a third invocation for non-AI sites; if the information is still insufficient, stop expanding the search and clearly explain the gap

Handling after triggering the rate limit:

  • Record: "Skipped: reached the rate limit"
  • Prefer switching to another site of the same type
  • If there is no suitable alternative source, answer directly based on the information already collected, and explain the coverage scope and gaps

Query-End Report

After each query ends, a brief "search summary" must be appended to the end of the answer, containing at least the following three items:

  • What website searches were used
  • What keywords were searched on each website
  • How many times each website was searched

If there are sites that were skipped due to rate limiting, they must also be explicitly stated.

It is recommended to use the following fixed format:

搜索摘要
- 网站:<site1> | 查询词:<term1> | 次数:<n>
- 网站:<site2> | 查询词:<term2>;<term3> | 次数:<n>
- 已跳过:<site3>,原因:达到频率上限

AI source selection

  • grok Suitable for real-time discussions, English-language internet public opinion, Twitter/X context, and hot topic tracking.
  • doubao Suitable for Chinese-language contexts, the ByteDance Douyin ecosystem, lifestyle content, Chinese hot topics, and general Chinese-language Q&A.
  • gemini Suitable for global web pages, English-language materials, general information retrieval, and background overviews.

If the user has not specified a website, first determine the language and context by default, then choose only one from these three.

Once a certain AI site has already executed one real query, do not rewrite the keywords and call that AI site again in the same question. If the answer is insufficient, prioritize supplementing with specialized sources rather than repeatedly pressing the same AI site.

AI query keyword suggestions

When using AI sources, do not just throw in a keyword that is too short. Prioritize constructing a query as "topic + goal + constraints".

  • Topic The object, event, product, person, company, or technical term that the user actually wants to look up.
  • Goal What kind of result is wanted, such as a summary, comparison, cause, trend, recommendation, or original clue.
  • Constraints Language, region, time range, platform scope, audience, price range, job location, and whether original sources need to be cited.

Prioritize using the following way of expressing it:

  • <主题> + <你要回答的问题>
  • <主题> + <时间范围/地区/语言>
  • <主题> + <平台或来源范围>
  • <主题> + <输出要求>

Avoid inputting only:

  • A single noun
  • Hot topic questions without a time range
  • Shopping, job-seeking, and travel questions without regional restrictions
  • Social media questions without platform restrictions

Timing for supplementing with specialized sources

When any of the following situations occurs, then supplement with specialized sources:

  • The AI gives a summary, but you need the original post, original video, original product, or original job result
  • The AI's coverage is insufficient and misses information from vertical sites
  • Higher authority or stronger domain relevance is needed
  • The user explicitly requests "find it from a certain platform"

A single query is usually controlled to 1 AI source + 1 to 2 specialized sources to avoid result overload.

Handling unavailable sources

When a site is unavailable:

  • Do not stop the entire search because a single source fails
  • Record: "Skipped: unavailable"
  • Fall back to other sites of the same type, or fall back to an AI source
  • Always base it on the actual results of opencli list -f yaml and opencli <site> -h The actual result shall prevail

Do not assume that any site is "absolutely available". Even for public sites, base it on the live help and execution results in the current environment.

Reference files

Read the corresponding files as needed:

  • references/sources-ai.md — AI default sources
  • references/sources-tech.md — Technology / academic
  • references/sources-social.md — Social media
  • references/sources-media.md — Media / entertainment
  • references/sources-info.md — News / knowledge
  • references/sources-shopping.md — Shopping
  • references/sources-travel.md — Travel
  • references/sources-other.md — Other vertical sources

Only read files relevant to the current query; there is no need to load all of them.