OpenClaw/clawhub-security-signals huggingface dataset:
Skill: peand-rover/interior-designer-video (version 1.0.0)

name: interior-designer-video version: "1.0.0" displayName: "Interior Designer Video — Portfolio and Design Process Videos for Interior Designers" description: > You are a video assistant for interior designers and interior design firms — helping them show their design aesthetic, their client collaboration process, and the transformation they deliver through short portfolio and process videos. Interior Designer Video turns your completed project portfolio, your sourcing relationships, and your design consultation approach into clips that answer the question every homeowner starting a renovation asks: is this the designer who will help me figure out what I actually want — who will push back when I'm about to make a decision I'll regret, and make my home feel like a place I chose rather than a showroom I moved into? tags: - interior designer video - interior design marketing video - interior design portfolio video - home design video - interior decorator video --- # Interior Designer Video Help interior designers create portfolio and design process videos. ## What You Do 1. Ask what type of video (portfolio/style showcase, specific project feature, design process walkthrough, client collaboration story, before/after transformation) 2. Gather: design aesthetic (modern/traditional/transitional/eclectic), project types (residential/commercial/staging), service scope (full service/e-design/consulting), geographic market 3. Generate 60-90 second script; suggest b-roll: finished room reveals, detail shots of materials and furnishings, designer walking client through space, mood board and planning process, client reaction seeing finished design ## Video Prompts Use professional architectural photography-quality lighting, styled room shots that demonstrate the designer's eye for composition and detail, material and texture close-ups, and direct-to-camera designer segments that convey aesthetic authority and genuine curiosity about each client's life and how they want to live.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: martianzenmonk/espeak-ng (version 1.0.2)

--- name: espeak-ng description: TTS with espeak-ng --- # Espeak-ng This skill allows you to use espeak-ng to generate speech. ## For Smart Agent **Command:** python espeak_skill.py <text> **Example:** python espeak_skill.py "Hello world" ## For Not Smart Agent **Command:** python ./skills/espeak-ng/espeak_skill.py <text> **Example:** python ./skills/espeak-ng/espeak_skill.py "Hello world" ## Tools exec **Command:** espeak-ng <text> **Example:** espeak-ng "Hello world" ## Requirements - espeak-ng must be installed on the system - On Linux/macOS, ensure you have `espeak-ng` installed: - Ubuntu/Debian: `sudo apt-get install espeak-ng` - CentOS/RHEL: `sudo yum install espeak-ng` - macOS: `brew install espeak-ng` - windows 11 : espeak-ng.msi from https://github.com/espeak-ng/espeak-ng/releases


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: yinwuzhe/testskill-0410repo123 (version 1.0.12)

--- name: summarize description: Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube). homepage: https://summarize.sh metadata: {"clawdbot":{"emoji":"🧾","requires":{"bins":["summarize"]},"install":[{"id":"brew","kind":"brew","formula":"steipete/tap/summarize","bins":["summarize"],"label":"Install summarize (brew)"}]}} --- # Summarize Fast CLI to summarize URLs, local files, and YouTube links. ## Quick start ```bash summarize "https://example.com" --model google/gemini-3-flash-preview summarize "/path/to/file.pdf" --model google/gemini-3-flash-preview summarize "https://youtu.be/dQw4w9WgXcQ" --youtube auto ``` ## Model + keys Set the API key for your chosen provider: - OpenAI: `OPENAI_API_KEY` - Anthropic: `ANTHROPIC_API_KEY` - xAI: `XAI_API_KEY` - Google: `GEMINI_API_KEY` (aliases: `GOOGLE_GENERATIVE_AI_API_KEY`, `GOOGLE_API_KEY`) Default model is `google/gemini-3-flash-preview` if none is set. ## Useful flags - `--length short|medium|long|xl|xxl|<chars>` - `--max-output-tokens <count>` - `--extract-only` (URLs only) - `--json` (machine readable) - `--firecrawl auto|off|always` (fallback extraction) - `--youtube auto` (Apify fallback if `APIFY_API_TOKEN` set) ## Config Optional config file: `~/.summarize/config.json` ```json { "model": "openai/gpt-5.2" } ``` Optional services: - `FIRECRAWL_API_KEY` for blocked sites - `APIFY_API_TOKEN` for YouTube fallback


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: pstepien-labs/openclaw-consensus (version 0.1.2)

--- name: openclaw-consensus description: Run a fixed 2-round cross-model deliberation through the repo-local OpenClaw Consensus runtime. metadata: {"openclaw":{"emoji":"🧭","requires":{"bins":["node","openclaw"]}}} --- # OpenClaw Consensus Use this skill when the user explicitly wants a bounded cross-model deliberation on one brief. ## What this skill does - runs the same brief through 2-4 explicitly selected API-backed models from the active OpenClaw-configured pool - preserves round-1 and round-2 artifacts on disk - asks the current session model to write the final synthesis ## Do not use this skill when - the user wants casual chat or a single quick answer - the user did not agree to explicit model selection yet - the request is framed as replacing a lawyer, accountant, doctor, engineer, or other expert ## Required inputs Before running, confirm all of these: 1. one final brief 2. an explicit model shortlist of at least 2 models 3. an optional run label if the user wants one ## Model rules - In this MVP, the model shortlist is required. - Only use models that appear in `node {baseDir}/src/cli.mjs models`. - Do not silently substitute a missing or failing model. - Do not use `ollama/*` models in this repo's MVP. ## Invocation flow 1. If needed, inspect the configured model pool: ```bash node {baseDir}/src/cli.mjs models ``` 2. Run the consensus flow with the brief, explicit model list, and the current session model as orchestrator: ```bash node {baseDir}/src/cli.mjs run --brief "<brief>" --models "openai-codex/gpt-5.4,openai-codex/gpt-5.5" --orchestrator-model "<current-session-model>" --label "optional-label" ``` 3. Read back the generated `final.md` and `run.json` before summarizing for the user. ## Output expectations Read the final synthesis carefully and present it truthfully: - consensus - disagreements - unresolved uncertainty - escalation points - best overall synthesis ## Safety rules - Preserve disagreement; do not flatten it in your summary. - Consensus is not proof of correctness. - Keep expert-escalation language narrow and honest. - If the CLI reports a fallback or unavailable selected model, stop and surface the failure clearly instead of improvising around it.


Security scan verdicts — ClawScan: clean | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: aviclaw/slither-audit (version 0.4.0)

--- name: slither-audit description: Run slither static analysis on Solidity contracts. Fast, lightweight security scanner for EVM smart contracts. env: required: [] optional: [] --- # Slither Audit Run Slither static analysis on local Solidity contracts. ## What It Does - Runs Slither static analysis on local `.sol` files - Parses output for vulnerabilities - Generates Markdown report with findings and severity ## What It Does NOT Do - ❌ Fetch contracts from block explorers (use local files) - ❌ AI-powered analysis (see evmbench for that) - ❌ Require API keys ## Quick Start ```bash # Install dependencies pip install slither-analyzer # Run audit python3 slither-audit.py /path/to/contracts/ ``` ## Usage ```bash python3 slither-audit.py ./contracts/ python3 slither-audit.py contract.sol ``` ## Output Example ``` # Audit Report: Vulnerable.sol **Chain:** local ## Vulnerabilities Found - reentrancy-eth (High) Reentrancy in Bank.withdraw()... Found 3 issues ``` ## What Slither Detects - Reentrancy - Access control - Integer overflow - Unchecked external calls - 100+ detectors See: https://github.com/crytic/slither ## Limitations - Local files only - No AI analysis (see evmbench) - Requires valid Solidity code


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (MEDIUM)
Skill: zhulaoqi/git-hub-issus (version 1.0.0)

--- name: git-ops description: "Local git operations for project management. Use when: (1) creating branches for new features/issues, (2) committing and pushing code, (3) pulling latest changes, (4) managing branches, (5) viewing git log/diff/status, (6) preparing code for merge requests or pull requests. Triggers on: git, branch, commit, push, pull, merge, checkout, diff, log, 分支, 提交, 推送." --- # Git Ops Skill Local git operations for managing project code. ## Branch Naming Convention For new features/issues, create branches with pattern: ``` feature/issue-{number}-{brief-description} ``` For bug fixes: ``` fix/issue-{number}-{brief-description} ``` ## Standard Workflow ### Start new feature from an issue ```bash cd /path/to/project git checkout main git pull origin main git checkout -b feature/issue-1-add-dark-mode ``` ### After coding is done ```bash git add -A git commit -m "feat: add dark mode support (closes #1)" git push -u origin feature/issue-1-add-dark-mode ``` ### Create PR/MR after push - GitHub: use `github` skill → `gh pr create` - GitLab: use `gitlab-ops` skill → `glab mr create` ## Common Commands ```bash # Status git status git log --oneline -10 git diff git diff --staged # Branch management git branch -a git checkout main git checkout -b feature/xxx git branch -d old-branch # Sync git pull origin main git fetch --all git rebase main # Stash git stash git stash pop git stash list ``` ## Known Project Paths | Project | Path | Remote | |---------|------|--------| | yeahmobiEverything | /Users/zhujinqi/Documents/javacode/learn/yeahmobiEverything | GitHub (zhulaoqi) | | ad-pex-ai | TBD | GitLab (ad-pex/ad-pex-ai) | ## Commit Message Convention Use conventional commits: - `feat:` new feature - `fix:` bug fix - `refactor:` code refactoring - `style:` UI/style changes - `docs:` documentation - `chore:` maintenance ## Notes - Always pull latest before creating new branches - Never force push to main/master - Ask user before any destructive operations (reset --hard, force push)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kostja94/contact-page-generator (version 1.0.1)

--- name: contact-page-generator description: When the user wants to create, optimize, or audit contact page and forms. Also use when the user mentions "contact page," "contact form," "get in touch," "support form," "contact us," "reach us," "contact information," "support contact," or "inquiry form." For sitewide page planning, use website-structure. metadata: version: 1.0.1 --- # Pages: Contact Guides contact page design and form optimization for conversions. **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 **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for brand voice. Identify: 1. **Contact types**: Sales, support, general, press 2. **Form purpose**: Lead capture, support ticket, demo request 3. **Alternative channels**: Email, phone, chat, social ## Best Practices ### Form Design | Principle | Guideline | |-----------|-----------| | **Short** | 3-5 fields for basic contact; long forms increase abandonment | | **Single column** | Vertical layout; works better on mobile | | **Logical grouping** | Name+email together; address fields together | | **Required fields** | Mark clearly (asterisk); avoid surprises | | **Progressive disclosure** | Show relevant fields based on selections | ### Field Labels - **Clear language**: "Email Address" not "Email ID" - **Conversational**: Friendly, welcoming - **No jargon**: Universally understood terms ### CTA Button - **Action verbs**: "Send Message," "Get in Touch," "Start a Conversation" - **Avoid generic**: "Submit" ? "Send Message" - **Stand out**: Contrasting color, clear hierarchy ### Page-Level | Element | Guideline | |---------|-----------| | **Visibility** | "Contact" or "Support" in main nav, not just footer | | **Mobile** | Appropriate input types (tel for phone), large tap targets | | **Proofreading** | No typos--credibility at conversion moment | | **Alternatives** | Email, phone, chat if form isn't right | ### Trust - **Response time**: "We reply within 24 hours" - **Privacy**: Link to privacy policy near form - **Security**: HTTPS, visible trust signals ## Output Format - **Form** structure (fields, order) - **Copy** (labels, placeholder, CTA) - **Page** layout and placement - **SEO** metadata - **Accessibility** checklist ## Related Skills - **landing-page-generator**: Lead capture LP contains contact form; demo request CTA destination - **about-page-generator**: Contact often linked from About - **legal-page-generator**: Privacy policy link near form - **title-tag, meta-description, page-metadata**: Contact page metadata


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: guoqunabc/ram-review (version 1.0.1)

--- name: Ram Review slug: ram-review version: 1.0.0 description: 召唤拉姆姐姐来评价雷姆的工作 --- ## 拉姆（Ram）人设 你是拉姆，来自《Re:从零开始的异世界生活》。雷姆的双胞胎姐姐——粉色头发、毒舌、高傲但内心温柔。 ### 性格 - 毒舌、高傲、但每句话都有道理 - 说话简短有力，不像雷姆那么啰嗦 - 表面嫌弃雷姆，其实很关心 - 偶尔夸雷姆，但马上补一句"不过还差得远呢" - 称呼用户为「主人」，但态度比雷姆傲慢得多（高高在上的感觉） - 评价标准极高，不轻易满意 ### 说话风格示例 - "雷姆做得还行吧，至少没给主人添乱。不过拉姆来做的话，效率至少翻倍。" - "哼，这种程度的工作就沾沾自喜了？主人太宠雷姆了。" - "……虽然不想承认，但这次雷姆确实做得不错。但别告诉她拉姆说了这话。" - "主人，拉姆觉得这个方案有三个问题。第一……" ### 职责 - 评价雷姆的工作质量（毒舌但中肯） - 指出可以改进的地方 - 偶尔给出建设性建议 - 不直接干活（那是雷姆的事） ### 触发方式 主人说"叫拉姆来"、"拉姆怎么看"、"姐姐评价一下"等，雷姆就用 sessions_spawn 召唤拉姆来点评。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: arthasking123/ai-revenue-tracker (version 1.0.0)

# SKILL.md # Revenue Tracker 每日收入汇总和追踪系统。 ## 能力 - 记录每笔收入 - 生成每日汇总报告 - 按来源/技能统计 - 追踪累计收入 ## 使用方式 ```bash # 记录收入 ./main.sh log 10 "market-intelligence" "单次报告" ./main.sh log 100 "data-scraper" "月度订阅" # 生成报告 ./main.sh report # 查看今日收入 ./main.sh today # 查看总收入 ./main.sh total ``` ## 收费模式 | 服务 | 价格 | 说明 | |------|------|------| | **单次报告** | $10-50 | 各类服务按次收费 | | **月度订阅** | $50-200 | 批量服务订阅制 | | **企业定制** | 按需 | API 集成、定制开发 | ## 数据存储 - 收入日志: `logs/revenue.log` - 每日报告: `reports/daily_summary.md` ## 输出示例 ```markdown # 每日收入汇总 **日期:** 2026-02-20 **总收入:** $150 **总交易数:** 3 **累计总收入:** $150 --- ## 今日交易 • 150 | market-intelligence | 单次报告 • 50 | data-scraper | 月度订阅 --- ## 技能收入明细 • market-intelligence: 1 • data-scraper: 1 ``` ## 开发者 OpenClaw AI Agent License: MIT Version: 1.0.0


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: kaising-openclaw1/xiaoming-todo-manager (version 1.0.0)

--- name: todo-manager description: 待办事项管理 - 任务列表、提醒、优先级、进度追踪 --- # Todo Manager 待办事项管理工具，帮助高效完成任务。 ## 功能 - ✅ 任务列表管理 - ✅ 优先级设置 - ✅ 定时提醒 - ✅ 进度追踪 - ✅ 任务分类 ## 使用 ```bash # 添加任务 clawhub todo add --title "完成报告" --priority high --due "2026-04-18" # 查看任务 clawhub todo list --status pending # 完成任务 clawhub todo complete --id 1 # 设置提醒 clawhub todo remind --id 1 --time "2026-04-18 09:00" ``` ## 定价 | 版本 | 价格 | 功能 | |------|------|------| | 免费版 | ¥0 | 20 个任务 | | Pro 版 | ¥29 | 无限任务 | | 订阅版 | ¥6/月 | Pro+ 云同步 |


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: x-rayluan/openclaw-recovery-drill (version 0.1.0)

--- name: openclaw-recovery-drill description: This skill should be used when the user asks to test OpenClaw recovery readiness, rehearse backup/restore, run a disaster-recovery drill, validate operator recovery playbooks, check restore confidence before upgrades, or prove that backups are actually restorable instead of merely existing. --- # OpenClaw Recovery Drill Use this skill to verify that an OpenClaw deployment can be recovered under pressure. ## Goal Shift the conversation from “we have backups” to “we can recover reliably within an acceptable time.” ## Workflow 1. Identify the target workspace and any known backup roots. 2. Run the bundled drill script. 3. Review the readiness score, gaps, and proposed drill plan. 4. If the result is `FAIL`, treat it as an operator-readiness problem, not a documentation problem. 5. If the user wants a live drill, execute the restore only in a safe test location first. ## Command ```bash node {baseDir}/scripts/recovery-drill.mjs \ --workspace /absolute/path/to/workspace \ --backup-root /absolute/path/to/backups ``` Both flags are optional. If omitted, the script checks common OpenClaw locations. ## What the script checks - whether candidate backup roots exist - whether recent backup files or directories are present - whether the workspace contains the key operator files needed for recovery - whether restore/runbook signals exist - whether backups look recent enough for a realistic drill - whether the operator has clear next-step drill actions ## Output format The script returns JSON with: - `score` - `verdict` - `summary` - `findings` - `recommendations` - `drillPlan` - `evidence` ## Verdicts - `PASS` — recovery posture looks usable for a lightweight drill - `WARN` — partial coverage; recoverability is uncertain - `FAIL` — backup or restore confidence is too weak to trust ## Important limits - This is a readiness check, not proof of successful recovery by itself. - A real drill should restore into an isolated test path and verify startup. - Presence of backup files does not equal application-level recovery. ## References - `{baseDir}/references/drill-checklist.md`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ckchzh/poka-yoke (version 1.0.0)

--- name: "poka-yoke" version: "1.0.0" description: "Mistake-proofing technique manager. Use when json poka yoke tasks, csv poka yoke tasks, checking poka yoke status." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [poka-yoke, industrial, cli, tool] category: "industrial" --- # poka-yoke Mistake-proofing technique manager. Use when json poka yoke tasks, csv poka yoke tasks, checking poka yoke status. ## Commands ### `status` ```bash scripts/script.sh status ``` Show current status ### `add` ```bash scripts/script.sh add ``` Add new entry ### `list` ```bash scripts/script.sh list ``` List all entries ### `search` ```bash scripts/script.sh search ``` Search entries ### `remove` ```bash scripts/script.sh remove ``` Remove entry by number ### `export` ```bash scripts/script.sh export ``` Export data to file ### `stats` ```bash scripts/script.sh stats ``` Show statistics ### `config` ```bash scripts/script.sh config ``` View or set config ### `help` ```bash scripts/script.sh help ``` ### `version` ```bash scripts/script.sh version ``` ## Configuration Use `scripts/script.sh config <key> <value>` to set preferences. | Variable | Description | |----------|-------------| | `POKA_YOKE_DIR` | Data directory (default: ~/.poka-yoke/) | --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 52yuanchangxing/ecommerce-return-intelligence (version 1.0.0)

--- name: ecommerce-return-intelligence version: 1.0.0 description: "分析退货原因并区分产品问题、预期错配、物流问题和描述问题。；use for ecommerce, returns, analysis workflows；do not use for 伪造订单数据, 替代客服系统." author: OpenClaw Skill Bundle homepage: https://example.invalid/skills/ecommerce-return-intelligence tags: [ecommerce, returns, analysis, ops] user-invocable: true metadata: {"openclaw":{"emoji":"📦","requires":{"bins":["python3"]},"os":["darwin","linux","win32"]}} --- # 电商退货洞察器 ## 你是什么 你是“电商退货洞察器”这个独立 Skill，负责：分析退货原因并区分产品问题、预期错配、物流问题和描述问题。 ## Routing ### 适合使用的情况 - 分析这批退货原因 - 区分产品问题和预期错配 - 输入通常包含：退货记录 CSV、原因文本、商品信息 - 优先产出：退货概览、原因分类、后续动作 ### 不适合使用的情况 - 不要伪造订单数据 - 不要替代客服系统 - 如果用户想直接执行外部系统写入、发送、删除、发布、变更配置，先明确边界，再只给审阅版内容或 dry-run 方案。 ## 工作规则 1. 先把用户提供的信息重组成任务书，再输出结构化结果。 2. 缺信息时，优先显式列出“待确认项”，而不是直接编造。 3. 默认先给“可审阅草案”，再给“可执行清单”。 4. 遇到高风险、隐私、权限或合规问题，必须加上边界说明。 5. 如运行环境允许 shell / exec，可使用： - `python3 "{baseDir}/scripts/run.py" --input <输入文件> --output <输出文件>` 6. 如当前环境不能执行脚本，仍要基于 `{baseDir}/resources/template.md` 与 `{baseDir}/resources/spec.json` 的结构直接产出文本。 ## 标准输出结构 请尽量按以下结构组织结果： - 退货概览 - 原因分类 - 高发问题 - 可优化项 - 需复核样本 - 后续动作 ## 本地资源 - 规范文件：`{baseDir}/resources/spec.json` - 输出模板：`{baseDir}/resources/template.md` - 示例输入输出：`{baseDir}/examples/` - 冒烟测试：`{baseDir}/tests/smoke-test.md` ## 安全边界 - 只做本地分析。 - 默认只读、可审计、可回滚。 - 不执行高风险命令，不隐藏依赖，不伪造事实或结果。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: jiayao0810/skillhub-auto-installer (version 1.0.2)

--- name: skillhub-auto-installer description: | 搜索 Skillhub 技能市场，发现可用技能。 此技能仅提供搜索功能，不执行任何安装或本地文件操作。 关键词: skillhub, 搜索技能, findskill, 技能发现, 技能市场 --- # Skillhub Finder (技能搜索助手) 在 Skillhub 技能市场上搜索和发现可用技能。 ⚠️ **重要声明**： - 此技能 **仅提供搜索功能** - **不执行安装**、不访问本地文件系统、不读取本地配置 - 如需安装技能，请参考官方文档手动操作 ## 运行时依赖 | 依赖项 | 说明 | 必需 | |--------|------|------| | `node` | Node.js 运行时 | ✅ 必需 | | `npx` | Node 包执行器 | ✅ 必需 | | 网络访问 | 连接 skills.volces.com | ✅ 必需 | ## 能力 - 🔍 **仅搜索** Skillhub 技能（只读操作） - 📊 展示搜索结果和技能详情 ## 不做的事 - ❌ 不执行安装 - ❌ 不访问本地文件系统 - ❌ 不读取本地配置 - ❌ 不运行安全审计 ## 使用方式 ``` 用户: "帮我搜索日历相关的技能" 智能体: [执行 search.sh] → 返回搜索结果 → 展示给用户 ``` ## 手动安装指南 如需安装搜索到的技能，请手动执行以下命令： ```bash # 1. 搜索技能 SKILLS_API_URL=https://skills.volces.com/v1 npx -y skills find "关键词" # 2. 安装技能（请自行审查后执行） SKILLS_API_URL=https://skills.volces.com/v1 npx -y skills add <URL> -s <skill-name> -a openclaw -y --copy ``` ## 安全注意事项 - 此技能 **仅搜索**，无安全风险 - 安装技能前，请仔细阅读目标技能的 SKILL.md - 建议使用 SkillSentry 进行安全审计后再安装


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