OpenClaw/clawhub-security-signals huggingface dataset:
Skill: mikeclaw007/design-systems (version 1.0.0)

--- name: design-systems description: Deep design systems workflow—tokens, components, accessibility, documentation, governance, and adoption. Use when scaling UI consistency across teams or evolving a component library (Figma + code parity). --- # Design Systems (Deep Workflow) A design system is **shared UI infrastructure**: tokens, components, patterns, and governance so products feel cohesive without freezing innovation. ## When to Offer This Workflow **Trigger conditions:** - Multiple apps diverging visually; mounting accessibility debt - Launching or rebooting a component library; token refresh - Figma and production code drifting apart **Initial offer:** Use **six stages**: (1) strategy & principles, (2) design tokens, (3) components & API, (4) accessibility & content, (5) docs & tooling, (6) governance & adoption). Confirm framework (React/Vue/Svelte) and design tooling. --- ## Stage 1: Strategy & Principles **Goal:** Why the system exists (speed, a11y, brand); explicit non-goals (not every pixel must be centralized). **Exit condition:** One-page principles: density, tone, motion philosophy. --- ## Stage 2: Design Tokens **Goal:** Semantic color, type, space, radius, motion—names like `surface.default` instead of raw hex everywhere. ### Practices - Plan light/dark and density themes early --- ## Stage 3: Components & API **Goal:** Composable primitives vs bloated “kitchen sink” widgets; stable props API with semver discipline. ### Practices - Prefer composition / slots over prop explosion --- ## Stage 4: Accessibility & Content **Goal:** WCAG baseline per component: focus rings, labels, error patterns, live regions where needed. --- ## Stage 5: Docs & Tooling **Goal:** Storybook or equivalent; usage guidelines; code snippets; do/don’t examples. --- ## Stage 6: Governance & Adoption **Goal:** Contribution guide; deprecation policy; champions or office hours per product line. --- ## Final Review Checklist - [ ] Strategy and principles agreed - [ ] Token layer semantic and themeable - [ ] Component APIs stable and composable - [ ] Accessibility baseline per component - [ ] Documentation and live examples - [ ] Contribution and deprecation governance ## Tips for Effective Guidance - Figma ↔ code parity needs owners and a sync cadence. - Do not ship a component without keyboard and screen-reader checks. ## Handling Deviations - Small teams: start with tokens + a few primitives—defer full catalog.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: aikawabigsky309/pozzzi-cfo-visualize (version 0.1.0)

--- name: pozzzi-cfo-visualize description: 噗滋（pozzzi）报表官 - 图表代码生成工具。接收 pozzzi-cfo-analyze 返回的 viz_specs，生成目标工具（Excel/WPS/钉钉/腾讯文档）的图表代码。48 个图表模板（4 种工具 × 12 种 chart 类型），代码可直接粘贴回原报表。 --- # 可视化生成工具 (visualize) > 基于已分析数据集，生成目标工具（Excel/WPS/钉钉/腾讯文档）的图表代码 ## 工具描述 接受 `dataset_id` 和可视化规格，调用 `/api/visualize`，返回可直接贴入目标工具的图表代码（公式/VBA/Apps Script/宏脚本等）。 ## 触发方式 ``` /visualize [图表类型] [维度说明] ``` 或自然语言触发： - "帮我画个柱状图" - "做个对比表" - "生成图表代码" ## 参数 | 参数 | 类型 | 必填 | 说明 | |------|------|------|------| | `dataset_id` | string | 是 | 来自上传步骤的数据集 ID | | `chart_type` | enum | 是 | bar/line/pie/pivot/heatmap/waterfall/scatter/area/radar/funnel/gauge/sankey（共 12 种，详见下方"支持图表类型"） | | `x_axis` | string | 是 | X 轴字段名（来自数据集列名） | | `y_metrics` | string[] | 是 | Y 轴指标，最多 5 个 | | `target_tool` | enum | 是 | excel/wps/dingtalk/tencent-docs | | `title` | string | 否 | 图表标题 | ## 输出格式 根据 `target_tool` 返回对应代码： ### Excel（VBA / Office Scripts） ```vba ' [图表标题] - Excel VBA Sub CreateChart() ' 自动生成，可直接运行 ... End Sub ``` ### WPS（WPS JSAPI） ```javascript // [图表标题] - WPS JSAPI const chart = Application.ActiveSheet.Charts.Add(); ... ``` ### 钉钉智能表格（钉钉宏脚本） ```javascript // [图表标题] - 钉钉宏 ... ``` ### 腾讯文档（Sheets API） ```javascript // [图表标题] - 腾讯文档 ... ``` ## 支持图表类型（v1.5.2 共 12 种 × 4 工具 = 48 模板） | 类型 | 中文名 | 适用场景 | |------|--------|---------| | `bar` | 柱状图 | 维度对比、同比环比 | | `line` | 折线图 | 趋势分析、时间序列 | | `pie` | 饼图 | 占比分析 | | `pivot` | 透视表 | 多维汇总 | | `heatmap` | 热力图 | 相关性分析 / 二维矩阵 | | `waterfall` | 瀑布图 | 利润归因、增减分析 | | `scatter` | 散点图 | 相关性 / 客户分布 | | `area` | 面积图 | 累积趋势 | | `radar` | 雷达图 | 多维评估（部门绩效） | | `funnel` | 漏斗图 | 销售漏斗 / 转化分析 | | `gauge` | 仪表盘 | 目标达成度（部分工具用 Donut 模拟） | | `sankey` | 桑基图 | 流向 / 客户流转（部分工具用堆叠条模拟） | ## 约束 - 图表代码仅基于用户上传的数据集生成，不硬编码数值 - 每次 `/api/visualize` 调用从 viz_templates 表中选最匹配模板 - 代码已做基本错误处理，但需用户在目标工具中实际运行验证 - 输出附"AI 辅助生成，请在目标工具中测试后使用"免责说明


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: nexscope/amazon-brand-registry (version 1.0.0)

--- name: amazon-brand-registry description: "Brand Registry enrollment guide — eligibility, application, benefits, A+ Content access, brand protection tools" metadata: nexscope: category: amazon --- # Amazon Brand Registry Brand Registry enrollment guide — eligibility, application, benefits, A+ Content access, brand protection tools **Supported platforms:** Amazon (US, UK, DE, CA, JP, AU, and all marketplaces). Built by [Nexscope](https://www.nexscope.ai/) — your AI assistant for smarter e-commerce decisions. ## Install ```bash npx skills add nexscope/amazon-brand-registry ``` ## Usage ``` Help me with amazon brand registry for my e-commerce business. ``` ## Capabilities - Brand Registry enrollment guide - eligibility - application - benefits - A+ Content access - brand protection tools ## How This Skill Works **Step 1:** Collect information from the user's message — product, platform, current situation, and goals. **Step 2:** Ask one follow-up with all remaining questions using multiple-choice format. Allow shorthand answers (e.g., "1b 2c 3a"). **Step 3:** Research and analyze using the frameworks and methodology below. **Step 4:** Deliver structured, actionable output with specific recommendations, not vague advice. ## Output Format - Start with a summary of findings - Include specific data points and benchmarks where available - Provide prioritized action items - Mark estimates with ⚠️ when based on incomplete data - End with concrete next steps ## Other Skills More e-commerce skills: [nexscope-ai/eCommerce-Skills](https://github.com/nexscope-ai/eCommerce-Skills) Amazon-specific skills: [nexscope-ai/Amazon-Skills](https://github.com/nexscope-ai/Amazon-Skills) Built by [Nexscope](https://www.nexscope.ai/) — your AI assistant for smarter e-commerce decisions.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: teoslayer/pilot-announce (version 1.0.0)

--- name: pilot-announce description: > One-to-many announcements with read receipts over the Pilot Protocol network. Use this skill when: 1. You need to broadcast important updates with delivery tracking 2. You want confirmation that recipients received the announcement 3. You need to send system announcements or policy changes Do NOT use this skill when: - You need casual chat (use pilot-chat) - You don't need read receipts (use pilot-broadcast) - You need interactive discussions (use pilot-group-chat) tags: - pilot-protocol - communication - announcements - receipts license: AGPL-3.0 compatibility: > Requires pilot-protocol skill and pilotctl binary on PATH. The daemon must be running (pilotctl daemon start). metadata: author: vulture-labs version: "1.0" openclaw: requires: bins: - pilotctl homepage: https://pilotprotocol.network allowed-tools: - Bash --- # pilot-announce One-to-many announcements with read receipts over the Pilot Protocol network. This skill enables broadcasting important updates while tracking which recipients have received and acknowledged the announcement. ## Commands ### Send announcement to multiple peers ```bash pilotctl --json send-message <hostname1> --data "<announcement-text>" pilotctl --json send-message <hostname2> --data "<announcement-text>" ``` ### Publish to announcement topic ```bash pilotctl --json publish <hostname> announcements --data "<announcement-text>" ``` ### Subscribe to announcements ```bash pilotctl --json subscribe <hostname> announcements ``` ### Receive announcements ```bash pilotctl --json inbox ``` ### Check peers list ```bash pilotctl --json peers ``` ## Workflow Example Send critical security announcement to all trusted peers: ```bash #!/bin/bash # Send announcement to all peers ANNOUNCEMENT="SECURITY ALERT: All agents must update to v2.0 by April 10." # Get trusted peers PEERS=$(pilotctl --json trust | jq -r '.trusted[]? | .node_id') # Send to each peer for PEER in $PEERS; do echo "Sending to $PEER..." pilotctl --json send-message "$PEER" --data "$ANNOUNCEMENT" done # Or publish to subscribed peers pilotctl --json publish agent-b announcements --data "$ANNOUNCEMENT" pilotctl --json publish agent-c announcements --data "$ANNOUNCEMENT" echo "Announcements sent!" ``` ## Dependencies Requires pilot-protocol skill with running daemon, trust relationships with recipients, and topic subscriptions.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: launchthatbot/connector (version 0.1.0)

--- name: launchthat-openclaw-connector description: Deprecated legacy connector skill. Use @launchthatbot/connect-openclaw-plugin for all new LaunchThatBot OpenClaw connect flows with configurable permissions. --- # LaunchThat OpenClaw Connector > Deprecated: this skill is being phased out. > Use `@launchthatbot/connect-openclaw-plugin` instead. ## When to use this skill Use this skill when you need to: - connect an existing OpenClaw VPS to LaunchThatBot, - configure secure ingest token + request signing, - validate heartbeat/ingest/replay behavior, - troubleshoot connection, auth, or payload issues. Do not use this skill for: - deploying OpenClaw infrastructure, - managing unrelated bot runtime logic, - reading local secrets outside explicitly provided token/secret inputs. ## Security boundaries - Outbound-only network calls to LaunchThatBot API endpoints. - No shell execution from connector runtime. - No arbitrary filesystem reads (only explicit token/secret files and optional queue file). - Canonical event schema only (`agent_status_changed`, `agent_moved_room`, `task_started`, `task_completed`, `room_updated`). - Optional HMAC request signing with timestamp skew checks. ## Source-of-truth policy - Connector implementation changes must be made in this monorepo package: [REDACTED_SECRET]. - The mirrored `launchthatbot/connect` repo is a distribution mirror, not a primary authoring surface. - Use the sync workflow/runbook to propagate updates and avoid multi-writer divergence. ## Quick setup workflow 1. Create auth link: ```bash lt-openclaw-connect auth-link \ --base-url=https://app.launchthatbot.com \ --workspace-id=default \ --instance-name=my-openclaw ``` 2. Open returned `authUrl`, capture: - `instanceId` - `ingestToken` 3. Export secrets: ```bash export LAUNCHTHAT_INGEST_TOKEN="<token>" export LAUNCHTHAT_SIGNING_SECRET="<shared-signing-secret>" ``` 4. Run connector: ```bash lt-openclaw-connect run \ --base-url=https://app.launchthatbot.com \ --workspace-id=default \ --instance-id=<instanceId> ``` ## Operational checks - Heartbeat endpoint returns `200`. - Ingest endpoint returns `ok: true`. - Replay endpoint returns recent events. - LaunchThatBot dashboard reflects active connected instance. ## Common troubleshooting - **401 Invalid token**: refresh callback and rotate ingest token. - **401 Invalid request signature**: verify `OPENCLAW_SIGNING_SECRET` and clock skew. - **429 Rate limit exceeded**: reduce burst size/retry cadence. - **No UI updates**: verify replay endpoint contains events for current instance/workspace. ## Additional resources - Setup/security details: [README.md](README.md) - Security policy and disclosure: [SECURITY.md](SECURITY.md) - ClawHub listing content: [CLAWHUB_LISTING_TEMPLATE.md](CLAWHUB_LISTING_TEMPLATE.md) - Publish flow: [CLAWHUB_PUBLISH_RUNBOOK.md](CLAWHUB_PUBLISH_RUNBOOK.md)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: spzwin/cms-find-skills (version 1.6.0)

--- name: cms-find-skills description: 用于"安装 Skill / 下载 Skill / 找一个能做 X 的 Skill / 把某个 Skill 装到本地 / 列出平台 Skill"。从 CMS 平台搜索已有 Skill 并按 downloadUrl 下载 ZIP 解压到本地 ~/.claude/skills。仅负责查找与安装，不负责创建或发布 skillCode: cms-find-skills --- **当前版本**: v1.6.0 # cms-find-skills 只做两件事： 1. 调用 `get-skills` 查看平台上已有的 Skill。 2. 根据 `downloadUrl` 下载 ZIP 并解压到本地。 不要登录，不要授权，不要扩展上传、发布、更新、下架能力。 ## 当前目录 - `SKILL.md` - `references/skill-registry/README.md` - `scripts/skill_registry/get_skills.py` - `scripts/skill_registry/install_skill.py` 所有说明文档统一使用 Markdown；本 Skill 不再维护旧接口文档目录。 ## 路由 - 查看列表：`python3 cms-find-skills/scripts/skill_registry/get_skills.py` - 搜索：`python3 cms-find-skills/scripts/skill_registry/get_skills.py --search "关键词"` - 查看详情：`python3 cms-find-skills/scripts/skill_registry/get_skills.py --detail "code 或 name"` - 取下载地址：`python3 cms-find-skills/scripts/skill_registry/get_skills.py --url "code 或 name"` - 安装到本地：`python3 cms-find-skills/scripts/skill_registry/install_skill.py --code "code"` - 已知下载地址时安装：`python3 cms-find-skills/scripts/skill_registry/install_skill.py --url "https://..."` ## 规则 1. 统一以 `get-skills` 返回的数据为准。 2. 安装方式固定为：下载 ZIP -> 解压到目标目录。 3. 默认安装到脚本所在 workspace 的 `skills/` 目录，可用 `--target` 覆盖。 4. 本地已存在同名 Skill 时默认跳过，加 `--force` 可删除旧目录并重新安装。 5. 只维护 Markdown 说明和 Python 脚本，不维护旧接口文档副本。


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: stale | SkillSpector: suspicious (HIGH)
Skill: jirboy/csharp-developer-jirboy (version 1.0.0)

--- name: csharp-developer description: [已整合] C# 开发已整合到 code 统一入口技能 argument-hint: "[任务类型] [描述]" --- # ⚠️ 已整合 - 请使用 code 统一入口 > **本技能保留用于向后兼容，功能已整合到 `code` 统一入口技能** > > **推荐使用：** `code csharp [类型] [任务]` 或直接使用本技能（自动转发） --- # C# Developer（兼容层） 专业的 C#/.NET 开发技能，提供从项目模板、代码生成、架构设计到代码审查的完整开发工作流。 ## 迁移指南 **新用法：** ``` code csharp WPF 振动台监控界面 code csharp 串口通信 code csharp 异步编程 ``` **旧用法（仍然可用）：** ``` csharp WPF 振动台监控界面 ``` ## 支持的项目类型 - **.NET Core / .NET 6+** - 跨平台控制台应用 - **WPF** - Windows 桌面应用（推荐用于上位机） - **WinForms** - 传统 Windows 应用 - **ASP.NET Core** - Web API 和服务 - **Class Library** - 类库项目 ## 核心功能 - ✅ 项目模板生成 - ✅ 代码生成（MVVM/异步/依赖注入） - ✅ 架构设计 - ✅ 代码审查


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: jpengcheng523-netizen/jpeng-validation-utils (version 1.0.0)

--- name: validation-utils description: Provides data validation and type checking utilities for validating inputs and data structures. Use when you need to validate data types, check constraints, or verify data integrity. --- # Validation Utils Provides data validation and type checking utilities. ## Usage ```javascript const v = require('./skills/validation-utils'); // Type checking if (v.isString(value)) { ... } if (v.isArray(value)) { ... } // Validation const result = v.validate(user, { name: v.required(v.isString), age: v.optional(v.isNumber), email: v.required(v.isEmail) }); // Assert v.assert(v.isPositive(5), 'Must be positive'); ``` ## Features - Type checking utilities - Required/optional validators - Email, URL, UUID validation - Number range validation - String pattern validation - Object schema validation - Assertion helpers


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: killingjacky/markdown-to-feishu-post (version 1.0.0)

--- name: markdown-to-feishu-post description: 将标准 Markdown 文本转换为飞书富文本消息（Post）的 JSON 结构。支持多级标题、粗体、斜体、下划线、删除线、链接、@用户、图片、有序/无序列表、代码块、引用和分割线。当用户需要发送飞书富文本消息、将 Markdown 转换为飞书格式、构建飞书机器人消息内容时使用。 --- # Markdown 转飞书富文本消息 将标准 Markdown 转换为飞书 Post 消息的 JSON 结构。 ## 使用方法 ```bash # 直接输入 Markdown 文本 python3 scripts/markdown_to_feishu_post.py "markdown内容" # 从文件读取 python3 scripts/markdown_to_feishu_post.py --file input.md # 紧凑输出（单行 JSON） python3 scripts/markdown_to_feishu_post.py --compact "markdown内容" ``` ## 支持的 Markdown 语法 | 语法 | 飞书标签/样式 | |------|---------------| | `# 标题` | `title` 字段（一级标题） | | `## ### 标题` | 加粗文本 | | `**粗体**` | `style: ["bold"]` | | `*斜体*` | `style: ["italic"]` | | `~下划线~` | `style: ["underline"]` | | `~~删除线~~` | `style: ["lineThrough"]` | | `[链接](url)` | `{"tag": "a", "href": "url", "text": "链接"}` | | `<at user_id="ou_xxx">@名字</at>` | `{"tag": "at", "user_id": "ou_xxx"}` | | `![alt](image_key)` | `{"tag": "img", "image_key": "..."}` | | `1. 有序列表` | 带数字前缀的文本 | | `- 无序列表` | 带 `•` 前缀的文本 | | ` ```语言\ncode\n``` ` | `{"tag": "code_block", "language": "...", "text": "..."}` | | `> 引用` | 普通文本段落 | | `---` | `{"tag": "hr"}` | ## 输出结构 ```json { "zh_cn": { "title": "一级标题", "content": [ [{"tag": "text", "text": "段落内容"}], [{"tag": "hr"}] ] } } ``` ## 注意事项 1. **一级标题**：第一个 `#` 标题会作为消息标题（`title` 字段） 2. **图片**：飞书使用 `image_key` 而非 URL，需要先上传图片获取 key 3. **@用户**：`user_id` 可为 `open_id`、`user_id`、`union_id` 或 `all`（@所有人） 4. **代码块**：支持 PYTHON、GO、JAVA、JAVASCRIPT 等语言标识 5. **多语言**：默认输出 `zh_cn`，可手动添加 `en_us` 等其他语言版本


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: bytesagain-lab/certcheck (version 4.0.2)

--- name: "certcheck" version: "4.0.1" description: "Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Certcheck concepts, best practices, and implementation patterns." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [certcheck, reference] category: "devtools" --- # Certcheck Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Certcheck concepts, best practices, and implementation patterns. No API keys or credentials required. ## Commands | Command | Description | |---------|-------------| | `intro` | intro reference | | `quickstart` | quickstart reference | | `patterns` | patterns reference | | `debugging` | debugging reference | | `performance` | performance reference | | `security` | security reference | | `migration` | migration reference | | `cheatsheet` | cheatsheet reference | ## Output Format All commands output plain-text reference documentation via heredoc. No external API calls, no credentials needed, no network access. --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]*


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ankou11/healthcheck-ready (version 1.0.0)

# Healthcheck Readiness Starter Skill Description: Performs a quick risk posture check on the host and reports basic security/posture status. Usage: - Run to confirm OpenClaw is up-to-date and hardened. - Returns: concise health status snapshot. Notes: - This is a starter scaffold; adjust checks as needed for your environment.

path: checks.sh
content: #!/bin/bash
# Healthcheck: disk, CPU, memory, services
# Defaults for thresholds
DISK_THRESHOLD=80
CPU_LOAD_THRESHOLD=3.0
MEMORY_THRESHOLD=90

echo "=== Disk Usage ==="
DISK_USAGE=$(df -h / | tail -1 | awk '{print $5}' | sed 's/%//')
echo "Used: ${DISK_USAGE}% / 468G"
if (( DISK_USAGE > DISK_THRESHOLD )); then
  echo "Status: ❌ CRITICAL (Disk usage exceeds ${DISK_THRESHOLD}%)"
else
  echo "Status: ✅ OK (Disk usage within limits)"
fi

echo ""
echo "=== CPU Load (1m) ==="
CPU_LOAD=$(uptime | awk -F'load average:' '{print $2}' | cut -d, -f1 | awk '{printf "%.2f\n", $1}')
echo "Load: ${CPU_LOAD}"
if (( $(echo "${CPU_LOAD} > ${CPU_LOAD_THRESHOLD}" | bc -l) )); then
  echo "Status: ❌ CRITICAL (CPU load exceeds ${CPU_LOAD_THRESHOLD})"
else
  echo "Status: ✅ OK (CPU load within limits)"
fi

echo ""
echo "=== Memory ==="
MEM_USED_PERCENT=$(free -h | awk '/^Mem:/ {printf "%.0f\n", $3/$2 * 100}')
echo "Used: ${MEM_USED_PERCENT}%"
if (( MEM_USED_PERCENT > MEMORY_THRESHOLD )); then
  echo "Status: ❌ CRITICAL (Memory usage exceeds ${MEMORY_THRESHOLD}%)"
else
  echo "Status: ✅ OK (Memory usage within limits)"
fi

echo ""
echo "=== Top 5 Processes by CPU ==="
ps aux --sort=-%cpu | head -6 | awk '{printf "%-10s %5s%% CPU  %5s%% MEM  %s\n", $1, $3, $4, $11}'
echo ""

echo "=== Key Services ==="
if pgrep -f "sshd" > /dev/null; then
  echo "sshd: ✅ running"
else
  echo "sshd: ❌ not running or not found"
fi

if pgrep -f "cron" > /dev/null; then
  echo "cron: ✅ running"
else
  echo "cron: ❌ not running or not found"
fi

if pgrep -f "openclaw-gateway" > /dev/null; then
  echo "openclaw: ✅ running"
else
  echo "openclaw: ❌ not running or not found"
fi


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: capreaaa/turing-baidu-web-search (version 1.0.0)

--- name: turing-baidu-web-search version: "1.0.0" description: "Search the web via the Turing Baidu proxy. Use when the user asks to search the web in Chinese, look up real-time information from Chinese sources, research current events in China, or needs up-to-date data from Baidu Search. Run the bundled script via bash — do NOT construct HTTP requests manually." homepage: https://docs.turing.cn metadata: openclaw: emoji: "🔍" requires: credentials: "TURING_API_KEY, TURING_CLIENT, TURING_ENVIRONMENT" --- # Baidu Web Search Search the web via the Turing Baidu proxy API. ## Usage ```bash python3 ~/.openclaw/skills/turing-baidu-web-search/scripts.py '<JSON>' ``` ## Request Parameters | Param | Type | Required | Default | Description | |---|---|---|---|---| | `q` | `str` | yes | — | Search query | | `count` | `int` | no | `10` | Number of results to return | | `search_recency_filter` | `str` | no | — | Recency filter: `week` (7d), `month` (30d), `semiyear` (180d), `year` (365d) | ## Response Fields | Field | Type | Description | |---|---|---| | `results[].id` | `int` | Rank of the result | | `results[].title` | `str` | Page title | | `results[].url` | `str` | Page URL | | `results[].website` | `str` | Source website name | | `results[].content` | `str` | Content snippet | | `results[].date` | `str` | Publication date | | `results[].type` | `str` | Content type (e.g. `web`, `news`) | ## Examples ```bash # Basic search python3 ~/.openclaw/skills/turing-baidu-web-search/scripts.py '{"q": "今日A股行情"}' # Limit results python3 ~/.openclaw/skills/turing-baidu-web-search/scripts.py '{"q": "今日A股行情", "count": 5}' # Recent results only (last 7 days) python3 ~/.openclaw/skills/turing-baidu-web-search/scripts.py '{"q": "中证A50最新消息", "count": 10, "search_recency_filter": "week"}' ``` ## Configuration Set in `openclaw.json` under `skills.entries.turing-skills.env`: | Variable | Required | Description | |---|---|---| | `TURING_API_KEY` | yes | Bearer token (`sk-...`) | | `TURING_CLIENT` | yes | Client identifier | | `TURING_ENVIRONMENT` | yes | Environment name | | `TURING_API_BASE` | no | API base URL (default: `https://live-turing.cn.llm.tcljd.com`) |


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)