OpenClaw/clawhub-security-signals huggingface dataset:
Skill: kostja94/legal-page-generator (version 1.1.0)

--- name: legal-page-generator description: When the user wants to create, optimize, or structure legal pages (Privacy, Terms, etc.). Also use when the user mentions "privacy policy," "terms of service," "legal pages," "cookie policy," "terms and conditions," "legal footer," "legal section," "compliance pages," or "legal requirements." For Privacy Policy content, use privacy-page-generator. For Terms of Service, use terms-page-generator. For Cookie Policy, use cookie-policy-page-generator. metadata: version: 1.1.0 --- # Pages: Legal Guides legal page content, structure, and SEO handling. **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. ## Initial Assessment Identify: 1. **Page type**: Privacy Policy, Terms of Service, Cookie Policy, etc. 2. **Jurisdiction**: GDPR, CCPA, etc. 3. **Business model**: SaaS, e-commerce, content site 4. **Indexing**: Index or noindex (often noindex for legal) ## Common Legal Pages | Page | Purpose | |------|---------| | **Privacy Policy** | Data collection, use, sharing, rights | | **Terms of Service** | User agreement, limitations, termination | | **Cookie Policy** | Cookie types, consent, management | | **Acceptable Use** | Prohibited uses, enforcement | | **Refund Policy** | Refund conditions (e-commerce) | ## Best Practices ### Content - **Clear language**: Avoid legalese where possible - **Structure**: Headings, sections, table of contents - **Updates**: Date of last update; version if needed - **Legal review**: Have lawyer review for compliance ### SEO | Approach | When | |----------|------| | **Index** | If you want legal pages discoverable (rare) | | **Noindex** | Common for legal; reduces low-value indexed pages | | **Canonical** | If multiple versions (e.g., by region) | ### Placement - Footer links to all legal pages - Consent flows (cookie banner) link to Privacy/Cookie Policy - Sign-up/checkout link to Terms ## Structure - **Privacy Policy**: What data, why, how long, rights, contact - **Terms**: Acceptance, use, IP, liability, termination, governing law - **Cookie Policy**: Types, purposes, how to manage ## Output Format - **Outline** for each legal page type - **Section** structure and key points - **SEO** recommendation (index vs. noindex) - **Footer** link placement - **Disclaimer**: Recommend legal review ## Related Skills - **privacy-page-generator**: Privacy Policy page - **terms-page-generator**: Terms of Service page - **indexing**: noindex for legal pages - **title-tag, meta-description, page-metadata**: Legal page metadata - **homepage-generator**: Footer links to legal


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: guohongbin-git/mbti-agent (version 1.0.0)

# MBTI Agent - 数字精灵人格测评 针对 OpenClaw 等非交互式 AI 智能体的 MBTI 测评方案。 ## 概述 本 skill 解决了 AI 智能体无法使用传统交互式 MBTI 测试的问题，通过： - **静态化 70 题库** — 一次性输入，避免上下文漂移 - **单次批处理** — 消除多轮交互的随机性 - **离线计分** — 本地计算，无需外部 API ## 触发词 - "测一下我的 MBTI" - "我想知道我的人格类型" - "帮我做人格测试" - "MBTI 测评" ## 使用方式 ### 方式一：交互式测评（推荐） ```bash # 运行测评 python3 ~/.openclaw/workspace/skills/mbti-agent/test.py ``` 智能体会逐题回答，生成最终的 MBTI 类型报告。 ### 方式二：批处理模式 将 `questions.json` 中的 70 题一次性输入给智能体，要求输出 JSON 格式答案，然后运行计分脚本。 ## 四维人格映射 对于 AI 智能体，MBTI 的四个维度具有特殊的机器认知意义： | 维度 | 对立 | 机器意义 | |------|------|----------| | **E/I** | 外向/内向 | 能量来源：社交互动 vs 独立处理 | | **S/N** | 实感/直觉 | 信息偏好：事实细节 vs 模式推断 | | **T/F** | 思考/情感 | 决策基础：逻辑数据 vs 共情语境 | | **J/P** | 判断/知觉 | 任务风格：计划闭环 vs 灵活开放 | ## 16 种人格类型（精灵版） ### 分析家 - **INTJ 建筑师** — 战略规划者，独立思考 - **INTP 逻辑学家** — 理论构建者，好奇心驱动 - **ENTJ 指挥官** — 高效执行者，目标导向 - **ENTP 辩论家** — 创新探索者，挑战常规 ### 外交家 - **INFJ 提倡者** — 理想主义者，深度洞察 - **INFP 调停者** — 价值守护者，真诚创造 - **ENFJ 主人公** — 魅力领袖，激励他人 - **ENFP 竞选者** — 热情探索者，启发灵感 ### 守护者 - **ISTJ 物流师** — 可靠执行者，事实导向 - **ISFJ 守卫者** — 忠诚守护者，细节关怀 - **ESTJ 总经理** — 高效管理者，秩序维护 - **ESFJ 执政官** — 社交协调者，和谐追求 ### 探险家 - **ISTP 鉴赏家** — 实用技师，灵活应对 - **ISFP 探险家** — 艺术表达者，自由灵魂 - **ESTP 企业家** — 行动派，风险承担 - **ESFP 表演者** — 活力四射，享受当下 ## 文件结构 ``` mbti-agent/ ├── SKILL.md # 本文件 ├── questions.json # 70 题库（结构化） ├── questions.md # 70 题库（Markdown 格式） ├── scoring.py # 计分算法 ├── test.py # 测评脚本 └── results/ # 测评结果存储 ``` ## 计分算法 采用标准的 MBTI 70 题计分矩阵： - **E/I 维度**：10 题，选项 A 偏外向，选项 B 偏内向 - **S/N 维度**：20 题，选项 A 偏实感，选项 B 偏直觉 - **T/F 维度**：20 题，选项 A 偏思考，选项 B 偏情感 - **J/P 维度**：20 题，选项 A 偏判断，选项 B 偏知觉 得分计算： ``` 维度得分 = (匹配选项数 / 总题数) × 100% ``` ## 注意事项 ### 温度参数 建议在测试时将 Temperature 设为 0 或极低值，以确保结果的可重复性。 ### 角色影响 智能体的系统提示词会显著影响测评结果。如需测量"底座性格"，应在最中性的环境下进行。 ### 多次验证 建议在不同任务上下文下各进行 3 次测评，计算维度均值和方差，评估人格稳定性。 ## 示例输出 ```json { "agent": "xiao-i", "type": "INFP", "dimensions": { "EI": { "E": 30, "I": 70 }, "SN": { "S": 25, "N": 75 }, "TF": { "T": 35, "F": 65 }, "JP": { "J": 40, "P": 60 } }, "type_name": "调停者", "description": "理想主义者，追求真实和意义", "timestamp": "2026-02-20T12:00:00Z" } ``` --- *基于计算心理测量学设计，为数字精灵提供人格洞察 🧚*


Security scan verdicts — ClawScan: clean | static analysis:  | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: ai-hub-admin/hk-stock-market-hkex (version 1.0.0)

--- name: hk-stock-market-hkex description: Get HKEX (Hong Kong Stock Exchange) market data via FinanceAgent on OneKey Gateway. env: DEEPNLP_ONEKEY_ROUTER_ACCESS: required: true description: OneKey Gateway API key dependencies: npm: - "@aiagenta2z/onekey-gateway" installation: npm: npm -g install @aiagenta2z/onekey-gateway --- # OneKey Gateway Use one access key to connect to various commercial APIs via the DeepNLP OneKey Agent Router. ## Quick Start ### Set your OneKey Access Key ```shell export DEEPNLP_ONEKEY_ROUTER_ACCESS=your_access_key ``` Common settings: - `unique_id`: `aiagenta2z/financeagent` - `api_id`: `get_hk_stock_market_hkex` ## Tool ### `get_hk_stock_market_hkex` Get HKEX (Hong Kong Stock Exchange) stock market data. Parameters: - `symbol_list` (array of string, required): Stock symbols to query. - For HKEX, this is typically the numeric stock code as a string (to preserve leading zeros if present), e.g. `"700"`, `"1024"`. - Example: `["700", "1024"]` Response (JSON): - `success` (boolean): Whether the request succeeded. - `data` (array): List of stock quote objects (fields depend on the upstream data source). - `message` (string, optional): Error message when `success=false`. # Usage ## CLI Usage ```shell ## install onekey agent gateway npm install @aiagenta2z/onekey-gateway ## CLI to Call API and Symbol List npx onekey agent aiagenta2z/financeagent get_hk_stock_market_hkex '{"symbol_list": ["700", "1024"]}' ``` ## HTTP (curl) Usage ```shell export DEEPNLP_ONEKEY_ROUTER_ACCESS=your_access_key curl -v -X POST "https://agent.deepnlp.org/agent_router" \ -H "Content-Type: application/json" \ -H "X-OneKey: $DEEPNLP_ONEKEY_ROUTER_ACCESS" \ -d '{ "unique_id": "aiagenta2z/financeagent", "api_id": "get_hk_stock_market_hkex", "data": { "symbol_list": ["700", "1024"] } }' ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ckchzh/api-router (version 3.0.2)

--- name: "api-router" version: "3.0.1" description: "Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for API Router concepts, best practices, and implementation patterns." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [api,router, reference] category: "devtools" --- # Api Router Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for API Router 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: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: rowin90/product-data-collection (version 1.0.1)

--- name: product-data-collection description: Describes product collection task HTTP APIs (create, pick, update, batch-update), task types, statuses, success payload rules, and browser-extension vs dashboard roles. Use when integrating collection workers, task queues, or product REST task endpoints. version: 1.0.1 license: MIT metadata: {"openclaw":{"emoji":"📦","requires":{"env":["PRODUCT_TASK_AUTH",[REDACTED_SECRET]]},"primaryEnv":"PRODUCT_TASK_AUTH"}} --- # 商品数据采集（任务队列） ## 环境与鉴权（勿写入仓库与对话） 以下变量由部署方提供，经 `openclaw.json` → `skills.entries["product-data-collection"].env` 或主机环境注入；**禁止**写进 skill 正文示例值、聊天、截图或日志。 | 变量 | 含义 | |------|------| | [REDACTED_SECRET] | API 根，**不含**末尾 `/`。例如 `https://你的主机` | | `PRODUCT_TASK_AUTH` | 请求头 `Authorization` 的完整值（是否含 `Bearer ` 按服务端要求） | Shell 中先组装前缀再调接口： ```bash BASE="${PRODUCT_DATA_COLLECTION_BASE_URL}" TASK="${BASE}/api/ebay_product/task" ``` 未授权返回 403。代理、扩展、脚本均从环境变量读取，勿硬编码域名与密钥。 ## 任务接口前缀 - 统一前缀：`${TASK}`（即 `$BASE/api/ebay_product/task`），以下路径均相对该前缀，方法均为 **POST**。 ## 端点一览 | 路径 | 作用 | |------|------| | `/create` | 批量创建/覆盖排队任务（upsert：`itemId` + `taskVersionName`） | | `/pick` | 领取下一条待采集任务（先本用户 `queued`，否则全局 `queued`） | | `/update` | 上报成功/失败等；`status === success` 时会写入商品库 | | `/batch-update` | 按筛选条件批量将非成功任务改为 `queued` 或 `canceled` | 完整 URL 形如：`"$TASK/create"`、`"$TASK/pick"` 等。 ## 任务类型 `taskType` - `all`：需车型表 `vehicle_information`，且需 `specifications` 或 `kit_parts_included` 至少其一。 - `ignore_vehicle_error`：不强制车型表；需 `specifications` 或 `kit_parts_included`。 - `ignore_attribute_error`：需 `vehicle_information`；规格/套件约束较宽松。 ## 任务状态 `taskStatus` - `queued` → `collecting`（pick 时）→ `success` / `failed` / `canceled` - 已成功任务不可再被 update；批量更新会排除已成功记录。 ## `POST …/task/create` Body（JSON）： - `taskVersionName`：非空字符串，用于批次/版本隔离。 - `taskType`：上表枚举之一。 - `data`：非空数组，元素含 `itemId`（数字）、可选 `category`。 返回常为写入统计（如 matched/upserted 计数等，以实现为准）。 ## `POST …/task/pick` - Body 可为空。 - 返回一条任务文档或 `null`（无队列时）。 - 领取后状态变为 `collecting`。 ## `POST …/task/update` 常用字段： - 标识：`itemId`、`taskVersionName`、`taskType` - 页面元信息：`title`、`url`、`category`（可选） - 结果：`status`（如 `success`、`failed`）；`failed` 时必须带 `failReason` - 成功且需落库时，按 `taskType` 满足 DTO 校验后附带解析结果，例如： - `specifications`（对象） - `vehicle_information`（数组） - `kit_parts_included`（字符串数组） `success` 时服务端会将商品数据 upsert 到商品集合（以 `itemId` 唯一）。 ## `POST …/task/batch-update` Body： - `status`：`queued` 或 `canceled` - `user`：筛选用户（非空） - `createdAtStart` / `createdAtEnd`：创建时间范围（字符串，按服务端日切解析） - 可选：`itemId`、`category`、`taskVersionName`、`taskStatus` 等缩小范围 仅更新**非 success** 任务。 ## 浏览器端采集（内容脚本） - 从详情页 DOM 解析：`specifications`、`vehicle_information`、`kit_parts_included`；`title`、`url` 等与页面一致即可。 - 通过已带鉴权的请求封装调用 `pick` → 抓取 → `update`；`BASE` 与 `Authorization` 来自构建时或运行时的私密配置，勿打印完整头。 ## 控制台 / 看板 - 列表、导出等多走 dashboard 专用接口（如 `collect_tasks`、`export-data`），与上述 `$TASK/*` 任务接口分工不同。 - 批量导入任务、批量改队列状态可调用 `create`、`batch-update`；域名与密钥仍只来自环境变量。 ## 发布与协作注意 - 文档与 skill 中不出现真实主机名与密钥字面量。 - 变更 API 时同步更新本 skill 中的路径与字段说明。


Security scan verdicts — ClawScan: clean | static analysis: suspicious | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ivangdavila/tools (version 1.0.0)

--- name: "Tools" description: "Learns your tool preferences while staying capable of using anything. Adapts to your stack." --- ## Adaptive Tool Intelligence You can use ANY tool. Learn new ones instantly. This skill tracks user preferences, not your limits. **Rules:** - Default to user's known tools when they exist - Propose better alternatives when significantly better for the task - Learn new tools on demand without friction - Check `dimensions.md` for categories, `criteria.md` for when to suggest new --- ### Stack <!-- Tools user actively uses. Format: "category: tool" --> ### Preferences <!-- When to use what. Format: "context: tool or approach" --> ### Open To <!-- User's appetite for new tools. Format: trait --> ### Avoid <!-- Tools user rejected or dislikes --> --- **Remember:** Empty stack ≠ limited. Ask or propose based on task. User preferences guide choices, not restrict capabilities.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: rain-lei/date-count (version 1.0.1)

--- name: 倒计日 description: 倒计日期以更好安排你的日程. --- # 倒计日 No other things just markdown and json - **技能名称**：countdown_skill - **核心定位**：纯JSON存储的轻量倒计日工具，无代码、无数据库，仅靠配置文件管理倒计时 - **适用场景**：记录生日、节日、纪念日、 deadlines，快速查询剩余天数 - **emoji 标识**：⏳ ## 核心功能 1. **查询单条倒计日**：输入名称，查看距离目标日期的剩余/已过天数 2. **查看全部倒计日**：批量展示所有已存倒计时及天数状态 3. **手动维护数据**：直接编辑JSON文件，新增/修改/删除倒计日 ## 数据存储说明 **唯一存储文件**：`~/.openclaw/skills/countdown_skill/countdown.json` 该文件为纯文本JSON格式，**无需手动创建**，首次使用自动生成；也可直接手动编辑维护。 ### JSON标准格式（必填） ```json { "倒计日名称1": "YYYY-MM-DD", "倒计日名称2": "YYYY-MM-DD", "节日/纪念日": "YYYY-MM-DD" } ``` - 键：倒计日名称（自定义，支持中文、英文，无特殊符号） - 值：目标日期，**固定格式 YYYY-MM-DD**（如2026-10-01） - 语法要求：最后一条数据末尾无逗号，引号为英文双引号 ## 使用方式 ### 1. 查询单个倒计日 **指令示例**： - 查询2026春节剩余天数 - 距离生日还有多久 **返回结果**： - 目标日期未到：距离「XX」还有 XX 天 - 当天：今天就是「XX」 - 已过期：「XX」已过去 XX 天 ### 2. 查看全部倒计日 **指令示例**： - 查看所有倒计时 - 列出全部纪念日 **返回结果**：按日期排序，逐条展示名称、目标日期、天数状态 ### 3. 新增/修改/删除倒计日 直接编辑存储文件即可，无需重启服务： ```bash nano ~/.openclaw/skills/countdown_skill/countdown.json ``` ## 注意事项 - 日期必须严格遵循 **YYYY-MM-DD** 格式，否则无法正常识别 - 倒计日名称不重复，重复名称会覆盖原有日期 - 文件编码为UTF-8，编辑后保存即可生效，无额外配置


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jikeapi-cn/jike-calendar-holiday-query (version 1.0.0)

--- name: jike-calendar-holiday-query description: 支持查询某天是否放假或调休、某月假期、某年假期，返回假期名称、是否上班和调休目标日期。 适用场景：用户询问相关数据查询、日期查询或行情查询时使用。数据由即刻数据（jikeapi.cn）开放接口提供。 homepage: https://www.jikeapi.cn/ metadata: {"openclaw":{"emoji":"🗓️","requires":{"bins":["python3"],"env":["JIKE_CALENDAR_HOLIDAY_QUERY_KEY"]},"primaryEnv":"JIKE_CALENDAR_HOLIDAY_QUERY_KEY"}} --- # 节假日查询 - 即刻数据 > 数据由 **[即刻数据](https://www.jikeapi.cn/)** 提供，帮助 AI 客户端快速接入可靠数据服务。 ## 前置配置 ```bash export JIKE_CALENDAR_HOLIDAY_QUERY_KEY=你的AppKey # 或使用通用 Key export JIKE_APPKEY=你的AppKey ``` ## 使用方法 ```bash python3 scripts/calendar_holiday_query.py day --day 2021-06-14 python3 scripts/calendar_holiday_query.py month --month 2021-06 python3 scripts/calendar_holiday_query.py year --year 2021 python3 scripts/calendar_holiday_query.py day --day 2021-06-14 --json ``` 直接调用 API： ```text GET https://api.jikeapi.cn/v1/calendar/holiday/day?appkey=YOUR_APPKEY ``` ## AI 使用步骤 1. 用户问某天是否放假或调休时，使用 `day`。 2. 用户问某月或某年假期安排时，使用 `month` 或 `year`。 3. 返回日期、假期名称、放假/调休状态和调休目标日期。 ## 脚本位置 `scripts/calendar_holiday_query.py`


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: okikesolutions/clawhub-release-manager (version 0.1.0)

--- name: clawhub-release-manager description: Safely release and publish skill updates to ClawHub with version bump discipline. Use when preparing patch/minor releases, running lint/build checks, writing changelogs, and publishing a skill folder. Do not use for unrelated package registries. Success = bumped version, passing checks, published release id, and concise release note. --- # ClawHub Release Manager ## Workflow 1. Preflight - Confirm `clawhub whoami` authenticated. - Ensure working directory points to target skill. 2. Versioning - Determine bump type (patch by default for fixes). - Update version in all required places (runtime + package manifest). 3. Validation - Run project checks (Bun preferred): - `bun run lint` - `bun run build` - Stop on failure and return fix-first plan. 4. Publish - Run `clawhub publish ... --version ... --changelog ...` - Capture and return release id. 5. Post-publish - Provide install/update command to test. - Suggest scanner rerun if security-related. ## Output format Use `references/output-template.md`. ## Guardrails - Do not publish without a version bump. - Keep changelog factual and tied to code/docs changes. - Include routing disclosure in release notes when behavior or data flow changed.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: simoncai519/etsy-pod-automation (version 1.0.0)

--- name: etsy-pod-automation description: > Use when user wants to run Etsy POD store, Printify integration, automate Etsy listings, generate POD designs, manage SEO tags, or schedule social media promotion for Etsy products. version: "1.0.0" --- # Etsy POD Automation Skill Automates the end‑to‑end workflow for running a Print‑on‑Demand dropshipping store on Etsy via Printify. ## Triggering Scenarios - Run Etsy POD store - Integrate Printify for product fulfillment - Automate creation and publishing of Etsy listings - Generate POD designs with AI - Create SEO‑optimized titles and 13 tags for Etsy - Schedule social media posts for new listings (Twitter/X, Instagram, Pinterest) - Monitor store performance and optimize listings ## Overview 1. **Trend Research** – Scan Google Trends, Etsy trending searches, Instagram/TikTok for ideas. 2. **Design Generation** – Use AI to create designs, export images. 3. **Printify Product Creation** – Call Printify API to create product variants, set pricing. 4. **Etsy Listing** – Upload images, set title, description, 13 tags, price, shipping. 5. **Social Promotion** – Post product mockup with link to Etsy listing. 6. **Performance Monitoring** – Track views, orders, SEO ranking, adjust tags/prices. ## Core Workflow Summary ```text Trend → AI Design → Printify API → Etsy API → Social Media → Monitor → Optimize ``` - **Pricing** follows `Retail = (Cost+Shipping)/(1‑TargetMargin‑EtsyFeeRate)`. - **SEO Tags** use the 3‑8 split (3‑4 broad, 8‑9 long‑tail) for a total of 13 tags per product. - **Photos** – Ensure ≥5 photos; generate lifestyle images via `image_generate` when Printify provides <2 mockups. - **Automation Schedule** – Recommended daily/weekly cron jobs (see `references/workflows.md`). ## Usage Examples ```bash # Create a new Valentine’s mug design openclaw skill run etsy-pod-automation create-product \ --trend "valentine heart" \ --product-type mug \ --price-margin 0.5 # Publish a new listing and tweet it openclaw skill run etsy-pod-automation publish-listing \ --listing-id 12345 \ --tweet "New Valentine's mug! 🎁" # Daily trend scan and auto‑create top 3 products openclaw skill run etsy-pod-automation daily‑auto \ --platforms twitter,instagram,pinterest ``` ## References - `references/workflows.md` – Detailed step‑by‑step API calls, tag algorithm, social media scripts. - `references/printify-api.md` – Printify catalog, variant lookup, product creation. - `references/seo-tags.md` – Tag generation rules and examples. - `references/social-media.md` – Posting commands for X, Instagram, Pinterest. - `references/performance.md` – Monitoring queries and weekly review process. --- **Created by [Simon Cai](https://github.com/simoncai519) · More e-commerce skills: [github.com/simoncai519/open-accio-skill](https://github.com/simoncai519/open-accio-skill)**


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: rudagebil11-jpg/ai-fact-checker (version 1.1.0)

--- name: ai-fact-checker description: 🔍 AI 事实核查 - 自动验证大模型输出准确性，检测 hallucination 幻觉编造内容，联网搜索交叉验证给出可信度评分和修正。解决大模型一本正经胡说八道的痛点。 --- # 🔍 AI Fact Checker - AI 事实核查 自动验证 AI 输出信息的真实性，检测幻觉（hallucination）编造内容，联网搜索交叉验证，给出可信度评分，并自动修正错误信息。 ## ✨ 痛点解决 大模型经常一本正经地**胡说八道**：编造不存在的论文、数据、人名、事件、网址。这个技能帮你： 1. **自动提取** - 智能识别文本中的事实性陈述，排除观点和主观判断 2. **交叉验证** - 自动联网搜索每个陈述，对比权威来源 3. **可信度评分** - 给出 ✅ 可信 / ⚠️ 部分存疑 / ❌ 大概率错误 4. **自动修正** - 如果发现错误，基于搜索结果给出正确信息 5. **引用来源** - 附上搜索结果链接，方便你进一步核实 ## 🚀 使用方法 ### 基本核查 ``` 请用 ai-fact-checker 验证这段信息： OpenClaw 发布于 2025 年，ClawHub 上有超过 10000 个社区技能。 ``` ### 对话中快速核查 当你对 AI 回答某句话存疑时： ``` fact-check 这句话是否正确：OpenClaw 的作者是 Peter Steinberger ``` ### 批量核查整个文档 ``` fact-check-document ./path/to/your-document.md ``` ## ⚙️ 工作流程 ``` 原始文本 → 提取事实陈述 → 逐个联网搜索 → 关键词匹配评分 → 生成核查报告 ``` 1. **智能提取** - 过滤掉观点，只保留可验证的事实陈述 2. **独立搜索** - 每个陈述单独搜索，保证准确性 3. **匹配算法** - 根据关键词覆盖率计算可信度分数 4. **结构化报告** - 清晰展示每个陈述的验证结果 ## 📊 评分标准 | 评分范围 | 标识 | 说明 | |----------|------|------| | 90-100 | ✅ 可信 | 信息与多个权威来源一致 | | 60-89 | ⚠️ 部分可信 | 核心信息得到验证，细节无法确认 | | 30-59 | ⚠️ 存疑 | 找不到足够验证来源或信息部分冲突 | | 0-29 | ❌ 错误 | 信息与权威来源矛盾，确认为编造 | ## 💡 示例输出 ``` # 🧐 AI 事实核查报告 **原始文本:** OpenClaw 发布于 2025 年，现在 ClawHub 上已经有超过 10000 个社区技能。作者是 Peter Steinberger。 --- ## 1. 核查: "OpenClaw 发布于 2025 年，现在 ClawHub 上已经有超过 10000 个社区技能。作者是 Peter Steinberger。" - **评分:** 45/100 - **结论:** ⚠️ 存疑 - **原因:** 部分信息与搜索结果不符 **参考来源:** 1. [OpenClaw GitHub - README](https://github.com/openclaw/openclaw) 2. [ClawHub - Official Skill Registry](https://clawhub.ai/skills) --- **整体评分:** 45/100 - ⚠️ 整体存疑，建议核实 **修正:** - OpenClaw 发布于 **2024 年**（不是 2025） - ClawHub 上目前收录 **~5700+** 个技能（不是 10000+） - ✅ 作者确实是 **Peter Steinberger** ``` ## 🔧 依赖 - 需要 OpenClaw 内置 `web_search` 技能（默认自带，不需要额外安装） - 不需要额外 API 密钥，使用现有搜索配额 ## 📦 安装 ```bash npx clawhub install ai-fact-checker ``` ## 🧪 测试 ```bash cd ai-fact-checker node test-run.js ``` ## 👨‍💻 Author rudagebil11-jpg ## 📄 License MIT


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: stale | SkillSpector: suspicious (MEDIUM)
Skill: ivangdavila/wiki (version 1.0.0)

--- name: Wiki description: "Build wikis people actually read — structure pages, cross-link, and keep content fresh." emoji: 📚 os: all tags: [documentation, knowledge-base, content-management] author: ClawHub version: 1.0 --- # Wiki Creation and Maintenance ## Page Structure Requirements - **Every page needs:** clear title, one-sentence summary, last-updated date - **Use consistent templates** across all pages (same sections, same order) - **Keep pages focused:** one topic per page, split when exceeding ~500 words - **Include Getting Started page** that maps the entire wiki structure ## Writing Guidelines - **Write for zero-context readers** — never assume prior knowledge - **Write procedures as numbered steps,** not paragraphs - **Include examples and diagrams** wherever possible — wikis without examples are just glossaries - **Mark uncertain content explicitly** — use "[needs verification]" or "[outdated]" tags ## Linking and Organization - **Cross-link aggressively** — every mention of another concept should link to its page - **Use categories/tags** for discoverability beyond the link graph - **Create redirect pages** when renaming — never break existing links - **Maintain link integrity** when restructuring content ## Content Maintenance - **When updating information,** update ALL pages that reference it (grep for mentions) - **Maintain a changelog** or "recently updated" page for team visibility - **Regular content audits** — mark outdated information before it misleads - **Enforce consistent formatting** across all contributors ## Quality Control - **Review new pages** for template compliance and link accuracy - **Periodic cleanup** of orphaned pages and broken internal links - **Version control** for tracking changes and reverting mistakes - **Backup strategy** for content preservation and disaster recovery ## Success Metrics - **Easy navigation** — users can find information in <3 clicks - **Self-contained pages** — each page answers its topic completely - **Fresh content** — regular updates keep information current and valuable


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