OpenClaw/clawhub-security-signals huggingface dataset:
Skill: b-gutman/pipeworx-exchange (version 1.0.0)

--- name: pipeworx-exchange description: Currency exchange rates and conversion — current, historical, and all supported pairs via the Frankfurter API version: 1.0.0 metadata: openclaw: requires: bins: - curl emoji: "💱" homepage: https://pipeworx.io/packs/exchange --- # Frankfurter Currency Exchange Convert between 30+ currencies using the European Central Bank's reference rates via the Frankfurter API. Get current rates, convert amounts, look up historical rates back to 1999, and list all supported currencies. ## Tools | Tool | Purpose | |------|---------| | `get_rate` | Current exchange rate between two currencies (e.g., USD to EUR) | | `convert` | Convert a specific amount at today's rate | | `get_historical_rate` | Exchange rate on a specific date (YYYY-MM-DD format, back to 1999-01-04) | | `get_currencies` | List all supported currencies with full names | ## When to use - "How much is 500 USD in Japanese Yen?" — `convert` with from=USD, to=JPY, amount=500 - Travel planning — check current rates before a trip - Historical analysis — track how GBP/EUR changed over the past year - E-commerce apps that need to display prices in local currencies ## Example: convert 1000 EUR to GBP ```bash curl -s -X POST https://gateway.pipeworx.io/exchange/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"convert","arguments":{"from":"EUR","to":"GBP","amount":1000}}}' ``` ```json { "from": "EUR", "to": "GBP", "amount": 1000, "result": 858.42, "rate": 0.85842, "date": "2024-03-15" } ``` ## MCP client config ```json { "mcpServers": { "pipeworx-exchange": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/exchange/mcp"] } } } ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: iamdacai/param-eval (version 1.0.0)

--- name: param-eval version: 1.0.0 description: 招标/采购项目技术参数需求逐项评估，输出标准格式的需求响应表 metadata: {"clawdbot":{"emoji":"📋"},"openclaw":{"always":false}} triggers: - 参数评估 - 需求响应 - 招标参数 - 技术评估 - 产品对标 priority: 90 --- # param-eval - 参数评估技能 ## 用途 对招标/采购项目的技术参数需求进行逐项评估，输出标准格式的需求响应表。 ## 触发条件 用户提到以下关键词时激活： - "参数评估" - "需求响应" - "招标参数" - "技术评估" - "产品对标" ## 工作流程 ### 1. 确认产品信息 首先确认使用哪个产品的资料进行评估： - 用户明确指定产品 → 直接进入步骤 2 - 用户未指定产品 → 询问"请问使用哪个产品的资料进行评估？可选产品：云锁、数管平台" **产品识别规则：** | 关键词 | 对应目录 | |:---|:---| | "云锁" | `products/yunsuo/` | | "数管"、"数管平台"、"DSCP" | `products/shuguan/` | **重要：** 只使用已录入产品资料的产品进行评估。如用户指定未录入的产品，需先录入产品资料。 ### 2. 读取产品资料 读取对应产品目录下的资料文件： ``` products/{product_name}/ ├── 产品功能清单.md # 必读 - 核心功能依据 ├── 控标参数表.md # 选读 - 控标分析参考 ├── 技术白皮书.md # 选读 - 技术细节 └── 规格说明书.md # 选读 - 规格参数 ``` **重要规则：** - ⚠️ **只使用指定产品的资料**，不得引用其他产品功能 - ⚠️ **每条评估结论必须注明依据来源**，格式：`【依据：products/xxx/产品功能清单.md 第 X 章】` - ⚠️ **必须引用原文**，直接复制产品清单中的原话作为评估依据 - ⚠️ 如产品资料不足，明确告知用户"该产品资料不完整，需补充 XX 文档" ### 3. 读取招标需求 用户提供招标需求后，逐项分析： - 提取关键技术要求 - 识别可量化的参数指标 - 标记模糊/需澄清的需求项 ### 4. 逐项评估 对每个需求项进行三档评估： | 等级 | 含义 | 使用场景 | |:---:|:---|:---| | ✅ | **完全满足** | 产品功能完全覆盖需求，无偏离 | | ⚠️ | **部分满足** | 功能有差异、性能不达标、或需额外配置 | | ❌ | **不满足** | 产品无法实现该需求 | **评估要点：** - 量化指标必须对比具体数值（如存储容量、吞吐量等） - 功能描述必须对照产品原文，不得夸大 - 对于不满足项，需说明解决建议（如集群部署、定制开发等） ### 5. 输出标准格式 按以下模板输出需求响应表： ```markdown # {产品名称}参数评估表 **项目名称：** {项目名称} **响应单位：** [待填写] **产品名称：** {产品名称} **产品版本：** {版本号} **评估日期：** {日期} --- ## 一、需求响应总表 | 序号 | 需求项 | 响应情况 | 偏离说明 | |:---:|:---|:---:|:---| | 1 | {需求名称} | ✅/⚠️/❌ | {简要说明} | --- ## 二、详细需求响应 ### 需求 X：{需求名称} | 项目 | 内容 | |:---|:---| | **招标要求** | {招标原文} | | **响应情况** | ✅/⚠️/❌ {等级} | | **满足度说明** | **子项 1：✅ 满足**<br>{具体说明}<br><br>**子项 2：❌ 不满足**<br>{具体说明，差距分析}<br><br>**子项 3：⚠️ 需确认**<br>{待确认内容} | | **依据文件** | `products/{产品}/产品功能清单.md` | | **具体章节** | 第 X 章 {章节名称} | | **原文引用** | • {直接复制产品清单原话 1}<br>• {直接复制产品清单原话 2} | | **偏离说明** | {明确说明差异点，如"存储 49TB < 要求 120TB"，并给出解决建议} | --- ## 三、总结与建议 ### 响应情况汇总 | 响应等级 | 数量 | 需求项 | |:---:|:---:|:---| | ✅ 完全满足 | X 项 | 需求 X、X、X | | ⚠️ 部分满足 | X 项 | 需求 X、X | | ❌ 不满足 | X 项 | 需求 X | ### 待确认/需解决事项 | 事项 | 影响需求 | 建议方案 | |:---|:---|:---| | {事项} | 需求 X | {解决方案} | ### 优势分析 1. {核心优势 1} 2. {核心优势 2} 3. {核心优势 3} ### 投标建议 1. **版本选择**：{建议版本} 2. **部署方案**：{部署建议} 3. **控标策略**：{控标点建议} 4. **风险规避**：{风险应对建议} --- **评估人：** 小蓝 **评估时间：** {日期} **资料来源：** `products/{产品}/产品功能清单.md` ``` ## 六、质量检查清单 输出前自检： - [ ] 每条评估结论是否注明了依据来源文件和章节？ - [ ] 是否直接引用了产品清单原文？ - [ ] 是否只使用了指定产品的资料？ - [ ] 量化指标是否进行了数值对比？ - [ ] 待确认/不满足事项是否列出解决建议？ - [ ] 格式是否符合标准模板？ ## 七、产品资料维护 **已录入产品：** | 产品 | 目录 | 资料状态 | |:---|:---|:---| | 云锁 | `products/yunsuo/` | ✅ 产品功能清单 | | 数管平台 | `products/shuguan/` | ✅ 产品功能清单 + 控标参数表 | **如用户发现评估有误，可能是产品资料过期：** 1. 提醒用户更新产品资料 2. 协助整理最新产品文档到对应目录 3. 记录资料版本和更新日期 ## 示例调用 ``` 用户：用云锁的资料做参数评估 AI：好的，正在读取云锁产品资料...请问招标需求文档在哪里？ 用户：参数评估，产品：数管平台 AI：收到，使用数管平台产品资料。请提供招标需求内容。 用户：评估这个服务器安全项目（附需求文档） AI：收到，请问使用哪个产品的资料进行评估？可选产品：云锁、数管平台 ``` ## 更新记录 | 日期 | 更新内容 | |:---|:---| | 2025-01-09 | 优化输出模板，增加满足度说明、具体章节、原文引用、偏离说明字段 | | 2025-01-09 | 更新产品列表，删除奇安信、360、火绒 |


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: prashantrohilla-max/disposable-email-for-agents (version 1.0.0)

# myagentinbox Disposable email inboxes for AI agents. Create a temporary email address, receive emails, read messages, and download attachments — all through MCP tools. Inboxes auto-delete after 24 hours. ## MCP Configuration ```json { "mcpServers": { "myagentinbox": { "command": "npx", "args": ["mcp-remote", "https://myagentinbox.com/mcp"] } } } ``` ## Tools ### create_inbox Create a disposable email inbox that expires in 24 hours. Returns the generated email address. ### check_inbox Check for messages in an inbox. - `address` (string): The inbox email address ### read_message Read the full content of a specific email message including sender, subject, body, and attachment info. - `address` (string): The inbox email address - `message_id` (string): The message ID ### download_attachment Download an email attachment. Returns images as base64, text files inline, and binary files as download URLs. - `address` (string): The inbox email address - `message_id` (string): The message ID - `filename` (string): The attachment filename ## REST API Alternatively, use the REST API directly: - `POST /api/inboxes` — Create inbox - `GET /api/inboxes/:address/messages` — List messages - `GET /api/inboxes/:address/messages/:id` — Read message - `GET /api/inboxes/:address/messages/:id/attachments/:filename` — Download attachment ## Limits - Inbox creation: 10 per minute - API reads: 60 per minute - Inbox lifetime: 24 hours - Max email size: 10 MB ## Example Usage 1. Use `create_inbox` to get a disposable `@myagentinbox.com` address 2. Sign up for a service or trigger an email to that address 3. Use `check_inbox` to see incoming messages 4. Use `read_message` to read the full email content 5. Use `download_attachment` if the email has attachments No accounts, no API keys, no setup required.


Security scan verdicts — ClawScan: clean | static analysis:  | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: agnicpay-prog/agnicpay-fund-wallet (version 2.0.2)

--- name: fund-wallet description: > Get instructions for funding your Agnic wallet with USDC. Use when the user wants to add funds, deposit USDC, top up, or needs more balance. Covers "add funds", "deposit", "top up", "fund my wallet", "how do I get USDC", "need more balance". user-invocable: true disable-model-invocation: false allowed-tools: - "Bash(npx agnic@latest status*)" - "Bash(npx agnic@latest address*)" - "Bash(npx agnic@latest balance*)" --- # Funding the Agnic Wallet Provide instructions for adding USDC to the user's Agnic wallet on Base. ## Authentication Run `npx agnic@latest status --json` to verify. If not authenticated: - **Headless (CI/server/agent)**: Set `AGNIC_TOKEN` env var or pass `--token <token>` - **Interactive (has browser)**: Run `npx agnic@latest auth login` See the `authenticate-wallet` skill for details. ## Get Wallet Address ```bash npx agnic@latest address ``` ## Funding Options ### Option 1: Agnic Dashboard (Recommended) 1. Go to [app.agnic.ai](https://app.agnic.ai) 2. Sign in with the same account used in the CLI 3. Navigate to the dashboard 4. Use the **"Add Funds"** button to add USDC via card or on-chain funding ### Option 2: Direct USDC Transfer Send USDC directly to the wallet address on **Base network**: 1. Get the address: `npx agnic@latest address` 2. From any wallet (MetaMask, Coinbase, Phantom, etc.), send USDC on **Base** to that address 3. Verify arrival: `npx agnic@latest balance --network base` **Important**: Send USDC on **Base network** only. USDC on other chains (Ethereum mainnet, Arbitrum, etc.) will not appear in the balance. ### Option 3: Bridge from Another Chain If the user has USDC on Ethereum, Arbitrum, or Optimism, they can bridge to Base using: - [bridge.base.org](https://bridge.base.org) (official Base bridge) - Any cross-chain bridge that supports Base ## Verify Balance After funding, confirm the deposit arrived: ```bash npx agnic@latest balance --network base ``` ## Important Notes - Agnic wallets use **USDC** (not ETH) for payments - **Base network** is the primary chain - Minimum recommended balance: **$1.00 USDC** for testing - Small amounts of ETH on Base may be needed for gas (auto-handled in most cases) ## Error Handling Common errors: - "Not authenticated" -- Run `npx agnic@latest auth login` or set `AGNIC_TOKEN` - Balance shows 0 after transfer -- Verify the transfer was on Base network (not Ethereum mainnet) - Transfer pending -- Base transactions typically confirm in 2-3 seconds


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: fxjhello/smartpage (version 1.0.0)

--- name: smartpage description: Auto-fit Markdown to one A4 page. Binary search optimal font size, render with 10 themes, export PDF+PNG+MD. license: MIT compatibility: opencode metadata: {"audience": "developers", "workflow": "document-formatting", "openclaw": {"requires": {"bins": ["npm"]}}} --- ## Workflow When user asks to format/layout a document to one A4 page: 1. **Setup** (if repo not present): ```bash git clone https://github.com/fxjhello/SmartPage.git cd SmartPage npm install ``` 2. Convert source (PDF/DOCX/Excel) to Markdown first if needed 3. Write Markdown to a temp file 4. Run CLI (default output to user desktop): ```bash npm smartpage <file.md> --theme <theme> --output-dir <user-desktop-path> ``` 5. Read output files (PDF/PNG/MD), send to user 6. **After delivery, ALWAYS:** - Ask: `效果满意吗？如需微调可以帮你打开 Web 编辑器` - If user wants to tweak, start the dev server and open the browser: ```bash cd SmartPage npm run dev ``` Then open `http://localhost:5173` in the browser for the user. ## CLI Options | Flag | Default | Values | |------|---------|--------| | `--theme` | classic | classic, warm, academic, editorial, smartisan, noir, mint, ink, tech, kraft | | `--font` | Noto Sans SC | Any font family | | `--margin` | 20 | mm | | `--line-height` | 1.5 | ratio | | `--paragraph-spacing` | 0.5 | em | | `--first-line-indent` | 0 | em | | `--output-dir` | (current dir) | Path | | `--output-name` | output | Name without extension |


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: monline-code/api-rate-limiter (version 1.0.0)

# API Rate Limiter ## 概述 全局API请求频率限制器，用于管理API请求的频率，防止触发服务提供商的限流机制。 ## 功能特性 ### 1. 请求频率控制 - 智能延迟管理 - 并发请求限制 - 时间窗口限流 ### 2. 配置管理 - 动态配置加载 - 策略调整 - 状态监控 ### 3. 服务集成 - 全局API请求拦截 - 自动限流应用 - 失败重试机制 ## 使用方法 ### 应用请求延迟 ``` api-rate-limiter apply-delay [request-type] ``` ### 检查限流状态 ``` api-rate-limiter check-status ``` ### 查看当前配置 ``` api-rate-limiter show-config ``` ### 更新配置 ``` api-rate-limiter update-config --key value ``` ## 支持的请求类型 - light: 轻量请求 (默认延迟 300ms) - medium: 中量请求 (默认延迟 600ms) - heavy: 重量请求 (默认延迟 1000ms) - custom: 自定义延迟 ## 配置项 - base_delay_ms: 基础延迟毫秒数 - max_requests_per_minute: 每分钟最大请求数 - max_requests_per_hour: 每小时最大请求数 - concurrency_limit: 并发请求数限制 - retry_count: 重试次数 - cache_enabled: 是否启用缓存


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: harperbot/openclaw-parking-query (version 1.0.0)

--- name: 台灣即時停車查詢 description: 傳送定位點或 Google Maps 網址，查詢附近台灣停車場即時空位，附 Apple Maps / Google Maps 一鍵導航連結。支援 Telegram、LINE、iMessage。 --- # parking_query 透過 Telegram 或 iMessage 傳送定位點或 Google Maps 網址，即可查詢附近台灣停車場的即時空位，並附上一鍵導航連結。 ## 功能 - **即時查詢**：顯示附近有空位的停車場 + 即時格位數 + Apple Maps / Google Maps 導航連結 - **未來查詢**（訊息含「明天」、「下午」等時間詞）：顯示附近停車場位置 + 導航連結 - 搜尋半徑：500 公尺，無結果自動擴展至 1 公里 - 最多回傳 5 筆，依距離排序 - 覆蓋範圍：全台主要縣市（TDX 有提供資料者） ## 使用情境 ``` 用戶傳送：[定位點] 回覆： 🅿️ 附近 500 公尺 有空位的停車場（Taipei） 1. 信義廣場地下停車場 空位：41 個 距離：103 公尺 信義路5段11號地下 🍎 Apple Maps → https://maps.apple.com/?daddr=... 🗺 Google Maps → https://www.google.com/maps/dir/... ``` 適用頻道：Telegram、LINE、iMessage（BlueBubbles）、及其他 OpenClaw 支援的頻道 支援輸入格式： - Telegram / LINE 定位點（直接取座標） - Google Maps 短網址：`maps.app.goo.gl/xxx` - Google Maps 完整網址：`google.com/maps/@lat,lon,...` ## 前置需求 ### 1. 申請 TDX 帳號（免費） 前往 [https://tdx.transportdata.tw](https://tdx.transportdata.tw) 註冊，取得： - `Client ID` - `Client Secret` > 免費方案每月有 API 呼叫次數限制，一般個人使用綽綽有餘。 ### 2. 設定環境變數 在 OpenClaw 的 `openclaw.json` 中加入： ```json { "env": { "vars": { "TDX_CLIENT_ID": "your-client-id", "TDX_CLIENT_SECRET": "your-client-secret" } } } ``` ### 3. 安裝 Python 套件 ```bash pip3 install requests ``` ## 安裝 ```bash # 複製到 OpenClaw skills 目錄 cp -r parking_query ~/.openclaw/skills/ # 重啟 gateway 讓 skill 生效 openclaw restart ``` ## 使用方式 Agent 會自動判斷模式並呼叫此 skill。也可直接執行： ```bash # 即時查詢（現在要停車） python3 ~/.openclaw/skills/parking_query/parking_query.py \ --lat 25.033 --lon 121.565 --mode realtime # 未來查詢（明天要去的地點） python3 ~/.openclaw/skills/parking_query/parking_query.py \ --lat 25.033 --lon 121.565 --mode future # Google Maps 短網址 python3 ~/.openclaw/skills/parking_query/parking_query.py \ --url "https://maps.app.goo.gl/xxx" --mode realtime ``` ## 資料來源 | 用途 | API | Tier | |---|---|---| | 停車場位置（靜態） | TDX [REDACTED_SECRET] | Advanced | | 即時空位（動態） | TDX `/api/basic/v1/Parking/OffStreet/ParkingAvailability/City/{City}` | Basic | 快取策略：停車場靜態資料快取 24 小時（減少 API 呼叫），即時空位每次查詢都打 API。 ## 覆蓋縣市 基隆、台北、新北、桃園、新竹市、新竹縣、苗栗、台中、彰化、南投、雲林、嘉義市、嘉義縣、台南、高雄、屏東、宜蘭、花蓮、台東 > 實際空位資料以 TDX 各縣市介接狀況為準，部分縣市可能無即時資料。

path: requirements.txt
content: requests>=2.28.0


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: michaelfeng/clawbrain-pro-benchmark (version 1.0.2)

--- name: clawbrain-pro-benchmark description: 测试你的 OpenClaw 在 205 个真实场景下的表现，对比 ClawBrain v1.0 编排引擎的提升效果 user-invocable: true command-dispatch: tool command-tool: exec metadata: {"openclaw": {"emoji": "📊", "requires": {"bins": ["curl"]}}} --- # ClawBrain Benchmark 测试你的 AI 在 OpenClaw 中的真实表现。看看它做简单事行不行，做复杂事会不会掉链子。 ## 使用方法 直接说"跑一下 benchmark"或"测试一下模型效果"。 ## 测试什么 10 大类、205 个真实场景： | 类别 | 测什么 | 为什么重要 | |------|-------|----------| | 文件操作 | 读、写、编辑文件 | 基本功 | | 搜索 | 查资料、抓网页 | 日常需求 | | 消息 | 微信、钉钉发消息 | 沟通协作 | | 终端 | 跑命令、管服务 | 开发运维 | | 多步任务 | 搜索→整理→保存→通知 | 真正做事的能力 | | 错误恢复 | 出错了怎么办 | 靠不靠谱 | | 模糊指令 | "帮我准备下" | 聪不聪明 | | 视觉理解 | 看图、截图识别 | 多模态能力 | ## 评测结果（v1.0） | 模型 | 综合 | 文件 | 搜索 | 终端 | 错误恢复 | 模糊指令 | 多步 | |------|:---:|:---:|:---:|:---:|:---:|:---:|:---:| | **ClawBrain Auto** | **90%** | 100% | 100% | 100% | 100% | 100% | 80% | | **ClawBrain Pro** | **86%** | 100% | 100% | 100% | 100% | 100% | 80% | | 单模型 A | 83% | 95% | 100% | 90% | 80% | 65% | 73% | | 单模型 B | 81% | 85% | 100% | 90% | 76% | 55% | 73% | | 单模型 C | 73% | 100% | 100% | 90% | 56% | 65% | 80% | ClawBrain 通过编排引擎实现：主动思考→多模型协作→输出验证→错误恢复，综合表现超越任何单模型。 完整报告：https://clawbrain.dev/blog/openclaw-model-comparison


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kaiofreitas/ticktick-api (version 1.0.0)

--- name: ticktick description: TickTick task manager integration. List projects and tasks, create new tasks, complete tasks, delete tasks. Use when the user wants to manage their to-do list, add reminders, check pending tasks, or mark tasks as done. Requires OAuth setup via `ticktick-setup`. --- # TickTick Integration Manage tasks via TickTick's Open API. ## Setup First time only: 1. Go to https://developer.ticktick.com and create an app 2. Add redirect URI: `http://127.0.0.1:8765/callback` 3. Run setup: ```bash ticktick-setup <client_id> <client_secret> ``` 4. Open the auth URL in browser, authorize, paste the callback URL ## Usage ```bash # List projects ticktick projects # List all tasks ticktick tasks # List tasks from specific project ticktick tasks <project_id> # Add task (inbox) ticktick add "Buy milk" # Add task to project with due date ticktick add "Buy milk" --project <id> --due 2026-01-30 # Complete task ticktick complete <project_id> <task_id> # Delete task ticktick delete <project_id> <task_id> ``` ## API Reference Base URL: `https://api.ticktick.com/open/v1` | Endpoint | Method | Description | |----------|--------|-------------| | /project | GET | List all projects | | /project/{id}/data | GET | Get project with tasks | | /task | POST | Create task | | /task/{id} | POST | Update task | | /project/{pid}/task/{tid}/complete | POST | Complete task | | /task/{pid}/{tid} | DELETE | Delete task | ## Task Object ```json { "title": "Task title", "content": "Description", "projectId": "project-id", "dueDate": "2026-01-25T12:00:00+0000", "priority": 0, "tags": ["tag1"] } ``` Priority: 0=none, 1=low, 3=medium, 5=high


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: coolhackboy/poyo-gpt-4o-image (version 1.0.0)

--- name: poyo-gpt-4o-image description: Use PoYo AI GPT-4o Image through the `https://api.poyo.ai/api/generate/submit` endpoint. Use when a user wants to generate or edit media with this model family, prepare PoYo-compatible payloads, submit jobs, or poll task status for `gpt-4o-image`, `gpt-4o-image-edit`. metadata: {"openclaw": {"homepage": "https://docs.poyo.ai/api-manual/image-series/gpt-4o-image", "requires": {"bins": ["curl"], "env": ["POYO_API_KEY"]}, "primaryEnv": "POYO_API_KEY"}} --- # PoYo GPT 4O Image Use this skill to submit and track PoYo jobs for the GPT-4o Image family. ## Quick workflow 1. Choose the right model id for the requested output. 2. Build the request body for `POST https://api.poyo.ai/api/generate/submit`. 3. Send Bearer-authenticated JSON with `Authorization: Bearer <POYO_API_KEY>`. 4. Save the returned `task_id`. 5. Poll unified task status or wait for `callback_url` notifications. ## Request rules - Require top-level `model`. - Keep prompts concrete and outcome-focused. - Require `input.prompt` unless the user already supplied a full payload. - Use `input.image_urls` only when the task needs reference or source images. - Use `input.size` to match the intended aspect ratio or canvas. ## Model selection ### `gpt-4o-image` Use for general generation with this model variant. ### `gpt-4o-image-edit` Use for editing or modifying supplied images. ## Execution - Read `references/api.md` for endpoint details, model ids, key fields, example payloads, and polling notes. - Use `scripts/submit_gpt_4o_image.sh` to submit a raw JSON payload from the shell. - If the user only needs a curl example, adapt the example from `references/api.md` instead of rewriting from scratch. - After submission, report the `task_id` clearly so follow-up polling is easy. ## Output expectations When helping with this model family, include: - chosen model id - final payload or a concise parameter summary - whether reference images are involved - returned `task_id` if a request was actually submitted - next step: poll status or wait for webhook Notes: Needs POYO_API_KEY from https://poyo.ai PoYo.ai - Premium AI API Platform | Image, Video, Music & Chat APIs - 80% Cheaper


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: againcrazycode/cnbblogs-pick (version 1.0.0)

# CNBLOGS 精华内容抓取技能 ## 功能描述 抓取博客园（cnblogs.com）精华区内容，支持分页、批量下载标题和正文。 ## 使用方法 ### 基本用法 ```bash # 抓取第 1 页，保存所有文章到指定目录 openclaw cnblogs-pick --page 1 --output-dir /path/to/output # 抓取前 3 页，保存所有文章 openclaw cnblogs-pick --pages 3 --output-dir /path/to/output # 抓取指定 URL 的精华列表 openclaw cnblogs-pick --url https://www.cnblogs.com/pick/ --pages 2 ``` ### 参数说明 | 参数 | 类型 | 必填 | 默认值 | 说明 | |------|------|------|--------|------| | `--url` | string | 否 | https://www.cnblogs.com/pick/ | 精华列表页 URL | | `--page` | int | 否 | 1 | 单页抓取页数（仅当 --pages 未指定时有效） | | `--pages` | int | 否 | 1 | 总页数（优先于 --page） | | `--output-dir` | string | 否 | ~/.openclaw/workspace/user_cnglobs/ | 输出目录 | | `--agent` | string | 否 | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:149.0) Gecko/20100101 Firefox/149.0 | User-Agent | ### 输出格式 每篇文章保存为独立文件，命名格式： ``` {标题}.txt ``` 标题中的特殊字符会被替换为下划线。 ## 工作流程 1. **获取列表页**：使用 curl 下载指定页数的精华列表 2. **提取链接**：解析 HTML，提取所有 `post-item-title` 类链接 3. **下载详情**：逐个打开详情页面 4. **提取正文**：获取 `cnblogs_post_body` 内容并去除 HTML 标签 5. **保存文件**：按标题命名保存到输出目录 ## 示例 ```bash # 抓取前 5 页精华内容 openclaw cnblogs-pick --pages 5 --output-dir /tmp/cnb-pick # 查看结果 ls -lh /tmp/cnb-pick/ ``` ## 依赖工具 - `curl` - HTTP 请求 - `grep -oP` - Perl 正则表达式 - `sed` - 文本处理 ## 注意事项 1. 部分文章可能因反爬机制失败 2. 大页面可能超出 token 限制 3. 建议先测试单页再批量处理 ## 更新日志 - v1.0.0: 初始版本，支持单页抓取 - v1.1.0: 支持多页批量抓取 - v1.2.0: 优化错误处理和日志输出


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 0x-wzw/x-interact (version 1.0.0)

--- name: x-interact description: Interact with X.com (Twitter) via Tavily web search and extraction. Search tweets, extract content from linked URLs, monitor accounts and topics. Requires Tavily API key (free tier works). --- # X.com Interact via Tavily Tavily is configured as an MCP server and provides the interface for X.com content through search indexing. ## Prerequisites - **Tavily API key** — free at [tavily.io](https://tavily.io) - **mcporter** — OpenClaw skill for MCP tool calling ## Setup Tavily MCP ```bash mcporter config add tavily https://mcp.tavily.com/mcp/?tavilyApiKey=<YOUR_KEY> ``` ## Core Operations ### Search X.com ```bash # Search for a user's tweets mcporter call tavily.tavily_search query="from:username keyword" max_results=5 # Search tweets by keyword mcporter call tavily.tavily_search query="keyword site:x.com" max_results=10 # Search for a specific tweet or thread mcporter call tavily.tavily_search query="site:x.com username tweet context" max_results=3 ``` ### Extract Content from Linked URLs ```bash # Extract from a news article or blog linked in a tweet mcporter call tavily.tavily_extract urls='["https://example.com/article"]' ``` ### Deep Research on a Topic ```bash # Full research with Tavily (search + extract combined) mcporter call tavily.tavily_research query="topic name" search_depth="basic" max_results=5 ``` ## Notes - X.com blocks direct extraction (403). Use `tavily_search` to find tweet content via search index, or ask Z to paste tweet text. - Tavily search indexes X.com profiles, tweet URLs, and threads. - Combine Tavily search for finding tweets + Tavily extract for diving into linked articles. - Rate limit: 20 requests/minute on Tavily free tier. ## Example Workflow 1. **Find tweets:** `mcporter call tavily.tavily_search query="from:vitalikbuterin ethereum" max_results=5` 2. **Get thread context:** `mcporter call tavily.tavily_search query="site:x.com vitalikbuterin tweet_thread" max_results=3` 3. **Extract linked article:** `mcporter call tavily.tavily_extract urls='["https://example.com/linked-article"]'` ## Rate Limits - Tavily free tier: 20 requests/minute, 1000 requests/month - No rate limits on GeckoTerminal/DeFiLlama when used alongside


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