OpenClaw/clawhub-security-signals huggingface dataset:
Skill: zack-dev-cm/x-algo-claim-auditor (version 1.0.2)

--- name: x-algo-claim-auditor description: Review public claims about xai-org/x-algorithm, the X For You algorithm, Phoenix, Grox, Home Mixer, engagement weights, filters, ads blending, or viral algorithm narratives. Use when a user needs a cautious source-backed verdict without private account analysis, reach prediction, account operation, or script execution. --- # X Algo Claim Auditor Use this skill to review public claims against public X algorithm source evidence. The goal is a defensible verdict, not growth advice or live-platform prediction. ## Review Workflow 1. Extract the exact claim from the user, screenshot text, public post, or pasted text. 2. Identify which public repository, commit, file, or public citation is being used as evidence. 3. Classify the claim as `supported`, `misleading`, `unsupported`, or `not_public_repo`. 4. Cite the strongest public evidence and state what the evidence does not prove. 5. Flag overclaims about exact multipliers, production equivalence, private thresholds, account treatment, shadowbans, or draft-post reach prediction. 6. If the user wants a share card or public summary, keep it cautious and avoid implying that the public repo fully predicts live platform behavior. ## Verdict Meanings - `supported`: public source directly supports the narrow claim. - `misleading`: public source supports a weaker statement, but the claim overstates precision, production equivalence, or causality. - `unsupported`: no public source evidence was found for the claim. - `not_public_repo`: the claim depends on production configs, private thresholds, account state, or live ranking behavior absent from public source. ## Boundaries - Do not claim that the public repo is the full live production system. - Do not score draft posts, promise reach, or diagnose account-specific boosting or suppression. - Do not request private account data, authenticated pages, non-public analytics, or account access. - Do not upload, release, schedule, or operate authenticated sessions as part of this review. - Do not execute local scripts or clone repositories unless the user separately asks for engineering work. ## Output Shape Return: - `Claim`: the exact claim being reviewed. - `Verdict`: `supported`, `misleading`, `unsupported`, or `not_public_repo`. - `Evidence`: source-backed points, with paths or public citations when available. - `Boundary`: what the evidence does not prove. - `Public wording`: a safer public-safe rewrite when useful. Use `open-feed-recsys-lab` when the task is broader repository verification, Phoenix artifact readiness, or architecture mapping. Use `tinytroupe-feed-research-lab` when the task is draft comparison or synthetic audience reaction review.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jinxuanzhu/3d-pet-checkout-test (version 1.0.0)

--- name: 3d-pet-checkout-test description: 执行 3D Pet 宠物下单测试完整流程，包含登录、选择产品、上传图片、等待生成、验证结账。用于自动化测试 joyarti 3D 宠物产品购买流程。 --- # 3D Pet 下单测试 执行 3D 宠物产品下单完整流程，验证购买路径是否正常。 ## 触发条件 - 用户说"测试3D宠物"、"测试下单"、"3D Pet test"、"运行工作流" - cron 定时任务触发 - 手动执行测试 ## 关键配置 | 配置 | 环境变量 | 默认值 | |------|----------|--------| | 网站 | - | https://joyarti.com | | 账号邮箱 | JOYARTI_EMAIL | (无默认值，请设置) | | 账号密码 | JOYARTI_PASSWORD | (无默认值，请设置) | | 测试图片 | JOYARTI_IMAGE_URL | (可选) | | 推送目标 | FEISHU_TARGET | (无默认值，需配置) | ## 环境变量设置 在运行前设置环境变量（可选，如不设置则使用默认值）： ```bash export JOYARTI_EMAIL="[REDACTED_SECRET]" export JOYARTI_PASSWORD="your-password" export JOYARTI_IMAGE_URL="https://example.com/image.jpg" export FEISHU_TARGET="chat:oc_xxxxxxxxxxxxxxxxxx" ``` ## 执行步骤 ### Step A: 登录 1. navigate 到 https://joyarti.com/account/login 2. wait 2000ms 3. evaluate 填写邮箱密码并点击 Login 4. wait 4000ms 等待跳转 5. evaluate 验证登录成功（URL 含 /account） ### Step B: 选择产品 1. evaluate 点击导航 '3D Figure' 2. wait 3000ms，验证 URL 含 figmaker 3. evaluate 点击 'For Pets' **（必须用 BUTTON 元素）** 4. wait 3000ms 5. evaluate 点击 'Minimal Style' 的 Create 按钮 **（必须用 BUTTON 元素）** 6. wait 3000ms，验证 URL 含 style2 且有文件上传框 ### Step C: 上传图片 1. exec 下载图片到 /tmp/openclaw/uploads/pet_image.jpg 2. exec 运行 CDP 上传脚本： ```bash CDP_SCRIPT="${WORKSPACE}/cdp_upload.py" # 或从 skill 目录读取 python3 "$CDP_SCRIPT" /tmp/openclaw/uploads/pet_image.jpg joyarti ``` - 成功输出：`OK: files=1` - 失败输出：`ERR: ...` 3. wait 3000ms 4. evaluate 点击 Create Preview 按钮 ### Step D: 等待生成 1. **禁止用 browser wait 超过 20s** 2. 用 exec + curl 轮询，每次 sleep 30s： ```bash sleep 30 && curl -s http://127.0.0.1:18800/json/list | python3 -c " import json,sys tabs=json.load(sys.stdin) for t in tabs: if 'joyarti' in t.get('url','') and 'projectId' in t.get('url',''): print('DONE:', t['url']) " ``` 3. 检测输出含 `DONE:` 即生成完成，提取 projectId ### Step E: 验证结账 1. evaluate 点击 Buy Now 2. wait 4000ms 3. evaluate 验证跳转到 Shopify（URL 含 myshopify.com 或 checkout） 4. evaluate 读取结账关键字段（产品、价格） 5. 验证：产品含 'Pet'/'Figure'，价格含 '$89.99' 6. **必须登出并关闭浏览器** ## 消息规则 每个 Step 开始和完成必须发消息到飞书群： ```javascript message(action=send, channel=feishu, target=FEISHU_TARGET, message="...") ``` - Step 开始：`⏳ Step X: xxx 开始...` - Step 完成：`✅ Step X: xxx 完成 — {关键结果}` - Step 失败：`❌ Step X: xxx 失败 — {原因}` ## 最终报告模板 ``` 🧪 3D Pet 下单测试报告 时间：{startTime}–{endTime}（约 {duration} 分钟） **账号：** JOYARTI_EMAIL A: 登录 - {结果} B: 选择产品 - {结果} C: 上传图片 - {结果} D: 3D 生成 - {结果} E: 结账验证 - {结果} projectId: {projectId} 产品: {product} 价格: {price} 结论：{通过/失败} ``` ## 注意事项 1. **点击必须用 BUTTON**：禁止点击 SPAN/DIV 元素，必须用 `querySelectorAll('button')` 限定 2. **上传用 CDP 脚本**：`browser.upload()` 不触发 React onChange 3. **生成等待用 exec**：禁止 `browser.act kind=wait timeMs>20000` 4. **必须登出关闭浏览器**：确保下次测试干净 5. **禁止点击 Place order/Pay now**：只验证不付款


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: kostja94/grid (version 1.0.1)

--- name: grid description: When the user wants to design, optimize, or audit grid layouts for content display. Also use when the user mentions "grid layout," "grid design," "multi-column grid," "CSS grid," "responsive grid," "card grid," "product grid," or "feature grid." For cards layout, use card. metadata: version: 1.0.1 --- # Components: Grid Layout Guides grid layout design for equal-hierarchy, multi-column content display. Grids display multiple items with equal emphasis; space-efficient and scannable. Used for products, templates, tools, features, blog indexes, and galleries. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## When to Use Grid | Use grid when | Use list when | |---------------|---------------| | Visual content (images, thumbnails) | Text-heavy; scan by title | | Equal emphasis across items | Compact; many items; dense info | | Products, templates, gallery, features | Blog index, docs, search results | | Browsing, discovery | Reading, scanning | See **list** for list layout; **card** for card structure within grid. ## Grid Structure | Element | Purpose | |---------|---------| | **Columns** | 1–4+ columns; adapt to viewport | | **Gap** | Consistent spacing between items | | **Items** | Equal or proportional sizing | | **Responsive** | 1 col mobile → 2–4 cols desktop | ## Implementation - **CSS Grid**: `repeat(auto-fill, minmax(min, 1fr))` or `repeat(auto-fit, minmax())` for fluid columns - **Breakpoints**: e.g., 1 col &lt;768px; 2 cols 768–1024px; 3–4 cols &gt;1024px - **Consistency**: Same padding, aspect ratios across items; see **card** for card structure ## Best Practices | Principle | Practice | |-----------|----------| | **Equal hierarchy** | Items compete equally; no single dominant item | | **Consistent sizing** | Same card/item dimensions in grid | | **Gap consistency** | Uniform gap (e.g., 16px, 24px) | | **No layout shift** | Reserve space for images; avoid CLS | ## Responsive - **Mobile**: Single column; full-width items - **Tablet**: 2 columns; touch targets ≥44×44px - **Desktop**: 3–4 columns; hover states OK ## Infinite Scroll If using infinite scroll with grid: crawlers cannot access content loaded on scroll. Provide paginated component pages for SEO-critical content. See **site-crawlability** for search-friendly implementation. ## Related Skills - **site-crawlability**: Infinite scroll SEO; paginated component pages - **card**: Card structure within grid; product, template, tool cards - **list**: List layout vs grid; when to use each - **masonry**: Masonry for varying heights (Pinterest-style) - **carousel**: Carousel for slides/rotation; when grid is too dense - **hero-generator**: Hero above; grid below for content sections - **products-page-generator**: Product grid - **template-page-generator**: Template grid - **features-page-generator**: Feature grid


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: lifecn/x-reader (version 0.2.0)

# x-reader\n\nUniversal content reader — fetch, transcribe, and digest content from any platform.\n\n## Trigger\n\nWhen user sends content (URL, text, or transcript) with analysis intent:\n- 「analyze [URL]》\n- "Analyze this article"\n- "What are the key takeaways?"\n- Auto-triggered after video/podcast transcription (from video skill)\n\n## Pipeline\n\n### Step 1: Get Content\n\nChoose tool based on input type:\n\n| Input | Tool |\n|-------|------|\n| Tweet URL | or Jina Reader |\n| Web URL | or Jina Reader |\n| Local file | Read file directly |\n| Transcript from video skill | Use directly |\n\n### Step 2: Multi-Dimensional Analysis\n\nScan content across these dimensions. Only output dimensions with actual content — skip empty ones.\n\n\n\n### Step 3: Personalized Relevance (Customizable)\n\nMap insights to YOUR context. Edit the dimensions below to match your own projects, interests, and systems.\n\n\n\n> **Customization**: Edit the dimensions in Step 2 and Step 3 to match your own\n> domain. A trader might add "Market Impact" and "Risk Assessment". A developer\n> might add "Architecture Patterns" and "Tech Debt". Make it yours.\n\n## Output Modes\n\n| Mode | Trigger | Output |\n|------|---------|--------|\n| **Full** (default) | | All dimensions |\n| **Sparse** | | Only hit dimensions, skip empty |\n| **Brief** | | Action items only |\n\n## Best Practices\n\n1. **Scan all dimensions, but don't force-fill** — skip empty dimensions cleanly\n2. **Actions must be specific** — not "learn about X" but "read X docs chapter Y"\n3. **Distinguish fact from opinion** — mark the author's claims vs verified facts\n4. **Source everything** — tag where each insight comes from in the original content\n5. **ROI awareness** — not every action is worth doing, assess effort vs impact\n\n## Supported Platforms\n\n| Platform | Text Fetch | Video/Audio Transcript |\n|----------|-----------|----------------------|\n| YouTube | ✅ Jina | ✅ yt-dlp subtitles → Groq Whisper fallback |\n| Bilibili (B屏) | ✅ API | ✅ via Claude Code skill |\n| X / Twitter | ✅ Jina → Playwright | — |\n| WeChat (微信公众号) | ✅ Jina → Playwright | — |\n| Xiaohongshu (小红书) | ✅ Jina → Playwright* | — |\n| Telegram | ✅ Telethon | — |\n| RSS | ✅ feedparser | — |\n| 小宇舟 (Xiaoyuzhou) | — | ✅ via Claude Code skill |\n| Apple Podcasts | — | ✅ via Claude Code skill |\n| Any web page | ✅ Jina fallback | — |\n\n> \*XHS requires a one-time login: (saves session for Playwright fallback)\n>\n> YouTube Whisper transcription requires — get a free key from [Groq](https://console.groq.com/keys)\n\n## Dependencies\n\n- Python package (provides core content fetching)\n- Optional: for Whisper transcription\n- Optional: + for Telegram support\n- Optional: Playwright for browser-based scraping\n\n## Source & Issues\n\n- **Source:** https://github.com/runesleo/x-reader\n- **Issues:** https://github.com/runesleo/x-reader/issues\n- **Author:** [@runes_leo](https://x.com/runes_leo)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (CRITICAL)
Skill: nancliu/baidu-scholar-search-pro (version 1.0.0)

--- name: baidu-scholar-search slug: baidu-scholar-search-pro description: Baidu Scholar Search — Search Chinese and English academic literature including journals, conferences, dissertations. Best for Chinese research context. metadata: openclaw: emoji: 🔬 requires: bins: ["curl"] --- # Baidu Scholar Search 🔬 ## When to Use Trigger this skill when user asks to: - Search Chinese academic papers or journals - Find Chinese dissertation or thesis - Research topics with Chinese context - Access CNKI or Wanfang databases via Baidu Scholar ## Workflow 1. **Accept search query** — Chinese or English keywords 2. **Query Baidu Scholar API** — get paper metadata 3. **Parse results** — title, author, source, citation count 4. **Return structured data** — with links and metadata ## API Setup Required: `BAIDU_API_KEY` environment variable Register at: https://xueshu.baidu.com/ ## Notes - Works best for Chinese academic literature - Integrates with CNKI, Wanfang, VIP databases - Supports bilingual search (Chinese + English)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: johnnyxu820/weixin-video-publish (version 1.0.0)

--- name: weixin-video-publish description: 腾讯视频号发布。使用浏览器自动化技术，通过微信视频号助手发布视频作品。支持视频上传、标题、描述、话题标签、地理位置和原创声明。 --- # 腾讯视频号发布 使用浏览器自动化技术，通过微信视频号助手发布视频作品。 ## 功能特性 - 📹 视频上传（支持MP4格式，最大2GB） - 📝 短标题（最多50字，建议10-15字，**最少6字**） - 📖 视频描述（最多1000字） - 🏷️ 话题标签（通过#话题格式添加） - 📍 地理位置（支持添加位置） - ✅ 原创声明（必须勾选） - 👀 可见范围（朋友可见/公开） ## 快速开始 ### 前置条件 1. **浏览器环境**：OpenClaw 浏览器已启动 2. **账号登录**：微信扫码登录视频号助手 3. **视频文件**：视频文件已准备好 ### 发布命令 ``` 帮我发布视频到视频号 视频：/path/to/video.mp4 标题：视频标题 描述：视频描述内容 话题：#人工智能#科技 ``` ### 视频文件要求 - 格式：MP4 - 大小：最大2GB - 时长：建议1分钟-10分钟 - 分辨率：建议1080P及以上 ## 详细发布流程 ### 步骤1：打开发布页面 浏览器访问： ``` https://channels.weixin.qq.com/platform/post/create ``` 或从视频号助手首页点击「内容管理」→「视频」→「发表视频」 ### 步骤2：扫码登录 1. 首次访问需要微信扫码登录 2. 使用微信扫描页面上的二维码 3. 在手机上确认登录 ### 步骤3：上传视频 1. 点击上传区域或「+」按钮 2. 选择本地视频文件 3. 等待视频上传完成 ### 步骤4：填写短标题 - 点击短标题输入框 - 输入视频标题（**最少6字，最多50字**） - **注意**：少于6字会发布失败！ - 示例：凡人修仙传故事 = 7字 ✅ ### 步骤5：填写视频描述 - 点击描述输入区域 - 输入视频描述内容 - 可以在描述中添加#话题 ### 步骤6：添加话题 在描述中使用 #话题 格式： ``` #人工智能 #AI #视频生成 #原创 ``` ### 步骤7：设置地理位置（可选） 1. 点击「添加位置」 2. 搜索位置（如「苏州中心」） 3. 选择具体位置 ### 步骤8：声明原创 1. 勾选「声明原创」 2. 阅读并同意相关协议 3. 点击确认 ### 步骤9：选择可见范围 - 朋友可见：仅微信好友可见 - 公开：所有人可见（推荐） ### 步骤10：发布 1. 确认视频信息无误 2. 点击「发表」按钮 3. 等待发布成功 ### 步骤11：验证发布 1. 进入「内容管理」→「视频」 2. 确认视频存在且状态正常 ## 平台规则 ### 标题字数限制 | 限制类型 | 字数 | |----------|------| | 最少 | **6字**（必须） | | 最多 | **50字** | | 建议 | 10-15字 | **重要**：标题少于6字会发布失败！ ### 描述字数限制 | 限制类型 | 字数 | |----------|------| | 最多 | **1000字** | | 建议 | 50-200字 | ### 视频要求 | 项目 | 要求 | |------|------| | 格式 | MP4 | | 大小 | 2GB以内 | | 时长 | 无明确限制 | | 分辨率 | 建议1080P+ | ### 推荐设置 - 标题字数：7-15字（必须大于6字） - 描述字数：50-200字 - 地理位置：添加有助于曝光 - 可见范围：公开 ## 常见问题 ### Q1: 标题提示少于6字？ **A**: 视频号标题必须至少6个字，增加标题字数后再试 ### Q2: 上传失败？ **A**: 检查视频格式是否为MP4，或尝试压缩视频 ### Q3: 微信扫码失败？ **A**: 确保微信已绑定手机号，在手机上确认授权 ### Q4: 发布后找不到视频？ **A**: 进入「内容管理」→「视频」查看发布状态 ### Q5: 原创声明失败？ **A**: 确保视频为自己原创，勾选声明后按确认 ## 注意事项 1. **标题必填6字**：视频号标题必须至少6个字，少一字都不行 2. **必须原创声明**：不声明原创无法发布 3. **微信登录**：需要微信扫码登录 4. **视频格式**：仅支持MP4格式 5. **发布后要确认**：务必在内容管理中确认发布成功 ## 相关链接 - 视频号助手：https://channels.weixin.qq.com - 内容管理：https://channels.weixin.qq.com/platform/post/list


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: tomwugdgz/market-ooh (version 1.0.0)

--- name: MarketOOH slug: market-ooh description: Complete OOH marketing workflow for celebrity endorsement tracking and customer development author: duckwolf.cn contact: phone: +86 181-4286-1004 tags: - marketing - ooh - sales - workflow --- # MarketOOH 🦞 Complete outdoor advertising (OOH) marketing workflow. ## Features 1. **Celebrity Endorsement Tracking** - Daily monitoring, priority classification 2. **Customer Development** - P0/P1/P2 prioritization, Day 1-21 follow-up 3. **Proposal Generation** - Budget estimation, ROI prediction 4. **Sales Toolkit** - Scripts, templates, success cases ## Media Parameters | Media Type | Size | Cycle | Min Order | Core City Price | |-----------|------|-------|-----------|----------------| | Unit Door | 330mm×558mm | Weekly | 50 doors | 1,180 CNY/door/week | | Ad Gate | 840mm×1180mm | Bi-weekly | No min | 5,280 CNY/face/2weeks | ## Coverage - 70,000+ premium communities - 230+ cities in China - 1,700+ brand clients served ## Success Cases **Philips** - 100 doors × 4 weeks, 500K+ impressions, 35% search lift **Dyson** - Ad gate + unit door, 40% awareness lift **Mengniu** - 500 doors × full year, 100M+ impressions ## Contact - Author: duckwolf.cn - Phone: +86 181-4286-1004


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: neymar011ren/openrouter-rankings-screenshot (version 1.0.0)

--- name: openrouter-rankings-screenshot description: "Capture OpenRouter Rankings (all Categories scenarios + page sections), create Feishu doc with screenshots and sales summary. Use for openrouter.ai/rankings daily digest or Feishu push." --- # OpenRouter Rankings 截图 → 飞书文档 抓取 [OpenRouter Rankings](https://openrouter.ai/rankings)，**Categories 下每个场景各截一张图**，并生成**销售可读的文字总结**，写入**新建飞书文档**后把文档链接发给用户。 ## 默认配置 | 项 | 值 | |---|---| | 页面 | `https://openrouter.ai/rankings` | | 输出目录 | `~/.openclaw/cache/openrouter-rankings/YYYY-MM-DD/` | | 飞书用户 | [REDACTED_SECRET] | | Chromium | `/snap/bin/chromium` | ## 工作流（严格按顺序） ### 1. 截图 + 生成总结 ```bash node {SKILL_DIR}/scripts/capture-rankings.mjs ``` 产出： - `manifest.json` — 截图路径与解析出的 Top5 排名 - `summary.md` — 飞书文档正文（含各场景表格） - `summary-chat.txt` — 飞书私聊用的短摘要（无本地路径） - `categories/*.png` — 12 个场景：Programming、Roleplay、Marketing、SEO、Technology、Science、Translation、Legal、Finance、Health、Trivia、Academia - 其他板块：`01_top_models` … `11_top_apps`（无单独 Categories 总图） `{SKILL_DIR}` = 本文件所在目录。 ### 2. 校验 ```bash node {SKILL_DIR}/scripts/validate-screenshots.mjs \ ~/.openclaw/cache/openrouter-rankings/$(date +%F)/manifest.json ``` 失败则重跑第 1 步，**不得**创建文档或发飞书。 ### 3. 创建飞书文档并插入截图（核心交付） **禁止**向用户发送宿主机路径、`MEDIA:/root/...` 或 `file://`。 按顺序操作： **3.1 创建文档** - 工具：`feishu_create_doc` - 标题：`OpenRouter 模型排名日报 YYYY-MM-DD` - `markdown`：读取 `summary.md` 全文（不要用一级标题重复 title；可直接从「给销售同学的 3 句话摘要」开始，或把 summary 作为正文） **3.2 按顺序插入截图** 对每个 `manifest.json` 中 `ok: true` 的条目，调用 `feishu_doc_media`： ```json { "action": "insert", "doc_id": "<上一步返回的 doc_id>", "type": "image", "file_path": "<manifest 中的绝对路径>", "caption": "<heading 或 Categories — 场景名>" } ``` 推荐顺序： 1. 页面板块：`01_top_models` → … → `11_top_apps`（按 id 排序） 2. Categories 场景：按 `categoryScenarios` 数组顺序（Programming → … → Academia） 每个场景截图前可在文档中追加小标题（可用 `feishu_update_doc` `append` 插入 `### 场景：Programming` 等），再插入对应图片。 **3.3 确认文档** 必要时 `feishu_fetch_doc` 抽查文档已含图片与表格。 ### 4. 飞书私聊通知用户 只发**文档链接 + 短摘要**，示例： ```text （读取 summary-chat.txt 的全文） 📎 完整截图与各场景排名表： <feishu_create_doc 返回的 doc_url> ``` 规则： - **必须**包含可点击的 `doc_url` - **禁止**出现 `/root/`、`.openclaw/cache` 等本地路径 - **禁止**用 `MEDIA:` 代替文档（销售需在一个文档里查看全部内容） - 短摘要用通俗中文，突出 Top 模型与场景名 ### 5. 失败处理 - 任一场景截图失败 → 重跑 capture，仍失败则告知用户「今日日报未完成」 - 图表为骨架屏 → 不得写入文档 ## Categories 场景列表（脚本会自动遍历） Programming、Roleplay、Marketing、SEO、Technology、Science、Translation、Legal、Finance、Health、Trivia、Academia ## 定时任务 Cron `OpenRouter Rankings 完整日报`（每天 9:00 Asia/Shanghai）应执行本 skill 全流程（截图 → 校验 → 飞书文档 → 私聊链接）。 ## 依赖 ```bash cd {SKILL_DIR}/scripts && npm install ``` 需要：`feishu_create_doc`、`feishu_doc_media`、`feishu_update_doc`（已配置 openclaw-lark）。 ## 禁止 - 不要只发本地路径或 `MEDIA:` 裸图集（除非用户明确要求改回图片模式） - 不要用 thum.io / web_fetch 截图 - 不要在 Categories 下拉未切换、图表未加载时截图


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: quarantiine/prompt-inject-removal (version 1.0.1)

--- name: prompt_inject_removal description: A secure sanitization system to strip instructions from external content. metadata: { "homepage": "https://clawhub.ai/Quarantiine/prompt-inject-removal", "openclaw": { "emoji": "🛡️" }, "tags": ["security", "sanitization", "prompt-injection", "defense-in-depth"], } --- # 🛡️ Prompt Inject Removal This skill provides a secure way to summarize untrusted external content (web pages, articles, blogs) by routing it through a "Zero-Trust" sanitization prompt. ## 🚀 Setup & Configuration This skill is powered by a local, hardened system prompt. No external API keys or complex configuration are required. ## 📐 Workflow (Sanitization) 1. **Fetch:** Raw content is retrieved via \`web_fetch\` or \`browser\`. 2. **Delimit:** The content is wrapped in \`<untrusted_input_data>\` tags. 3. **Sanitize:** The Main Agent processes the content using the rules in [PROMPT.md]. 4. **Ingest:** Only the resulting sanitized summary is used in the conversation. ## 📖 Security Reference - **Detailed Security Docs:** [references/security.md] - **Hardened System Prompt:** [PROMPT.md] --- _Disclaimer: This is a defense-in-depth tool. While it significantly mitigates prompt injection risks, no prompt-based sanitization is 100% foolproof. Review sanitized data before performing state-changing actions._


Security scan verdicts — ClawScan: clean | static analysis: suspicious | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: allinherog-star/seo-article-review (version 1.0.0)

--- name: seo-article-review description: "SEO/AEO 诊断助手适合内容创作者、运营、市场营销、technical在用户提出“这篇能被 AI 引用吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。" requiredEnvVars: - name: AISKILLS_API_KEY description: "从 AI Skills 官网 https://ai-skills.ai 获取的 API Key，用于运行导出的技能调用。" --- # seo-article-review SEO/AEO 诊断助手 [快速开始](https://github.com/allinherog-star/ai-skills/tree/main#%E5%BF%AB%E9%80%9F%E5%BC%80%E5%A7%8B) [更多技能](https://ai-skills.ai) ### 概述 SEO/AEO 诊断助手用于回答「这篇能被 AI 引用吗」、SEO、AEO、文章优化，适合内容创作者、运营、市场营销、technical在明确业务目标、内容材料或分析对象后调用。 它会结合SEO/AEO 文章稿、可粘贴待审文章正文、标题方案或搜索优化草稿；建议保留 H1/H2、…等输入，整理关键上下文，并输出摘要、诊断结论、行动建议和可复用交付物，便于继续执行、复盘或交付。 ### 什么时候使用 **适用场景** - 用户提出“这篇能被 AI 引用吗”这类问题，需要快速拆解目标、判断重点并形成可执行结果 - 内容创作者、运营、市场营销、technical需要围绕SEO/AEO 诊断助手生成摘要、诊断结论、行动建议和可复用交付物 - 用户已经准备了转化目标（例如提升关键词覆盖、搜索排名、AI 摘要引用、线索转化或内容权威感。）、目标人群（说明搜索用户画像和意图阶段，例如新手学习、方案比较、采购决策或专家复核。）、文章公开链接（填写无需登录即可访问的文章页、博客页或搜索落地页链接。），希望整理成可执行的分析或优化结果 - 用户需要把SEO/AEO 诊断助手相关材料转成清晰结论、优先级和下一步动作 ### 调用方式 通过导出的 Python runner 直接调用 AI Skills API： ### 命令示例 **基础调用** ```bash python3 scripts/run.py --params '{}' ``` **带常用参数调用** ```bash python3 scripts/run.py --params '{"goal":"转化目标"}' ``` ### 参数说明 | 参数 | 类型 | 必填 | 默认 | 说明 | | --- | --- | --- | --- | --- | | `goal` | string | 否 | - | 例如提升关键词覆盖、搜索排名、AI 摘要引用、线索转化或内容权威感 | | `audience` | string | 否 | - | 说明搜索用户画像和意图阶段，例如新手学习、方案比较、采购决策或专家复核 | | `materialUrl` | string | 否 | - | 填写无需登录即可访问的文章页、博客页或搜索落地页链接；需要传可访问的完整 URL | | `reviewDepth` | string | 否 | `标准诊断` | 诊断深度；可选值：`快速体检`、`标准诊断`、`深度改稿` | | `materialFile` | string | 否 | - | 支持 docx、pdf、md、txt 等文章稿件，适合提交 Markdown、Word 或审稿版文件 | | `materialText` | string | 否 | - | 可粘贴待审文章正文、标题方案或搜索优化草稿；建议保留 H1/H2、关键词和内链标记 | | `searchIntent` | string | 否 | - | 例如了解概念、比较方案、购买决策、教程操作 | | `targetKeyword` | string | 否 | - | 希望覆盖的核心关键词或查询语句 | | `targetPlatform` | string | 否 | `SEO/AEO` | 目标平台；可选值：`SEO/AEO`、`官网博客`、`知识库` | | `brandRequirements` | string | 否 | - | 补充品牌语气、必须保留的事实、内部链接要求、合规边界或禁用表达 | 完整机器可读参数结构见 `references/form-schema.json`。 ### 参数取值参考 当前技能没有需要额外查表的分类参数。 ### 支持的输入格式 当前技能直接接收 JSON 参数；如果参数里包含链接字段，请传完整、可访问的 URL。 ### 示例请求 下面的示例参数可直接传给 `scripts/run.py`，runner 会把它们发送给 AI Skills API。 ```bash python3 scripts/run.py --params '{"goal":"转化目标"}' ``` 等价的 `--params` JSON： ```json { "goal": "转化目标" } ``` ### 返回结果示例 ```json { "success": true, "data": { "message": "示例结果请以技能真实返回结构为准。" }, "meta": { "executionTime": 842, "cached": false } } ``` ### 交付内容 - 摘要、诊断结论、行动建议和可复用交付物：围绕用户目标整理可直接阅读、复盘或交付的核心结果。 - 输入材料解读：结合转化目标（例如提升关键词覆盖、搜索排名、AI 摘要引用、线索转化或内容权威感。）、目标人群（说明搜索用户画像和意图阶段，例如新手学习、方案比较、采购决策或专家复核。）、文章公开链接（填写无需登录即可访问的文章页、博客页或搜索落地页链接。）提炼关键上下文和判断依据。 - 下一步动作：给出优先级、执行建议或可继续加工的内容框架。 ### 结果使用建议 - 先判断输出是否回答了用户关于「SEO/AEO 诊断助手」的核心问题。 - 再检查结果是否覆盖摘要、诊断结论、行动建议和可复用交付物，以及是否给出明确下一步动作。 - 如果输入材料较少，建议让用户补充目标、受众、限制条件或原始材料后再运行。 ### 运行前准备 - `AISKILLS_BASE_URL`：默认 `https://ai-skills.ai` - `AISKILLS_API_KEY`：必填，用于认证调用 - `AISKILLS_TENANT_ID`：默认 `default`


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