← 返回 Skills 市场
dataify-server

Dataify Google Search

作者 dataify-server · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ 安全检测通过
47
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install dataify-google-search
功能描述
When the user requests "call Google Search" or "web search/SERP crawling", or explicitly mentions the web search field, the dataify-google-search skill is tr...
使用说明 (SKILL.md)

Dataify Google Search

Use this skill to turn a user's Google search request into a Dataify Scraper API call.

Required Pre-Call Confirmation

Before every real API call, follow this confirmation flow. These rules override any older workflow order in this skill.

  1. Parse the user's request into the API body fields and fixed engine value.
  2. Apply defaults only when the parameter description explicitly states a default. Do not use example YAML values, sample prompts, placeholder values, or examples such as pizza, us, en, dates, airport codes, or tokens as defaults.
  3. If a required parameter has no documented default and cannot be inferred from the user request, ask for that parameter before building the table.
  4. Show a Markdown table before calling the API. Do not include Authorization. Include the complete body field list from this skill's reference document, including engine, even when a field is currently blank.
  5. The table must have exactly these columns: 参数名, 当前值, 默认值, 说明.
  6. After the table, ask the user whether they want to modify any parameter. Do not call the API until the user explicitly confirms.
  7. If the user changes a parameter, regenerate the table and ask for confirmation again.
  8. If the token is missing, stop and tell the user to sign in at Dataify Dashboard to obtain DATAIFY_API_TOKEN.

Use the bundled preview helper whenever possible to generate the confirmation table from this skill's reference document:

python3 scripts/preview_params.py --params-json '{"q":"USER_QUERY"}'

Pass every parsed current value to preview_params.py using --params-json or matching --field value arguments. The helper reads defaults and descriptions from references/*api.md; if the helper cannot parse a default, leave the default blank rather than inventing one. 9. After confirmation and token handling, call the bundled Python script with python3 and return the API response body directly without summarizing, extracting, cleaning, translating, or reshaping it.

Workflow

  1. Parse the user's request into Dataify Google Search fields. Use q as the search query and set engine to google.
  2. If the token is missing, stop and tell the user to sign in at Dataify Dashboard to obtain DATAIFY_API_TOKEN.
  3. Build request parameters with only the fields the user requested plus required defaults. Use json: "1" unless the user asks for another output format. The script submits these parameters as form data, not a JSON request body.
  4. Run the bundled Python script with python3. Run it from this skill directory, or use the absolute path to scripts/google_search.py.
python3 scripts/google_search.py --q "OpenAI news" --gl us --hl en --json 1

For many fields, you may pass one JSON object with shell-appropriate quoting:

python3 scripts/google_search.py --params-json '{"q":"OpenAI news","gl":"us","hl":"en","json":"1"}'

If the user provided a token in the conversation instead of an environment variable, pass it with --token and avoid echoing it back in the final answer:

python3 scripts/google_search.py --token "USER_TOKEN" --q "OpenAI news" --gl us --hl en
  1. Return the script output directly to the user. Do not summarize, extract, clean, translate, or reshape the API response.

Field Mapping

Use references/google_search_api.md when you need the exact field list or examples.

Core rules:

  • Always submit the API request as form data with Content-Type: application/x-www-form-urlencoded.
  • Always force engine to google.
  • Keep request values as strings unless the script accepts and normalizes a boolean.
  • Omit optional fields that the user did not request.
  • Ask a follow-up only when the required search query q cannot be inferred.
  • If both location and uule are present, prefer the explicit uule and omit location.
  • Normalize token values in the script. A token without Bearer is accepted and prefixed automatically.

Common mappings:

  • "JSON" -> json: "1"
  • "JSON+HTML" -> json: "2"
  • "HTML" -> json: "3"
  • "Light JSON" -> json: "4"
  • country or region for Google behavior -> gl
  • interface/search language -> hl
  • country-restricted results -> cr, formatted like countryFR
  • language-restricted results -> lr, formatted like lang_fr
  • page number N -> start: String((N - 1) * 10)
  • safe search on/off -> safe: "active" or safe: "off"
  • desktop/tablet/mobile -> device
  • render JavaScript -> render_js: "true"
  • bypass cache -> no_cache: "true"
  • include AI Overview -> ai_overview: "true"
安全使用建议
Before installing, confirm you are comfortable with the skill making external search/API requests and handling any required provider token. Use scoped or revocable credentials, avoid sending sensitive queries unless needed, and watch for unintended activation on generic search prompts.
能力评估
Purpose & Capability
The reported capability is web search or SERP-style external lookup, and external API calls or token handling are coherent with that purpose when user-directed.
Instruction Scope
SkillSpector flagged the trigger description as broad, which could cause unintended activation on generic search requests, but this is an invocation-scoping issue rather than evidence of deception or unsafe behavior.
Install Mechanism
No artifact-backed evidence showed stealth installation, obfuscated setup, package tampering, or unexpected install-time execution.
Credentials
Network access and possible API credentials are proportionate for a search/crawling integration, but users should expect queries and related context to be sent to the configured provider.
Persistence & Privilege
The pre-scan noted Unicode control characters, but no concrete persistence, privilege escalation, destructive action, credential exfiltration, or hidden background behavior was verified.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install dataify-google-search
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /dataify-google-search 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.0.0
Initial release with robust Google Search API parameter confirmation flow. - Requires pre-call confirmation: parses user input, fills parameters, displays a Markdown table for review before calling the script. - Users must confirm (or modify) all parameters, shown with current value, default, and description, before proceeding. - Prevents API call if required parameters or token are missing, with clear prompts to resolve. - Always returns the raw API output directly, without modification. - Follows strict field mapping rules, including forced engine and result format handling.
元数据
Slug dataify-google-search
版本 1.0.0
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 1
常见问题

Dataify Google Search 是什么?

When the user requests "call Google Search" or "web search/SERP crawling", or explicitly mentions the web search field, the dataify-google-search skill is tr... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 47 次。

如何安装 Dataify Google Search?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install dataify-google-search」即可一键安装,无需额外配置。

Dataify Google Search 是免费的吗?

是的,Dataify Google Search 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Dataify Google Search 支持哪些平台?

Dataify Google Search 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Dataify Google Search?

由 dataify-server(@dataify-server)开发并维护,当前版本 v1.0.0。

💬 留言讨论