OpenClaw/clawhub-security-signals huggingface dataset:
Skill: dbeadle1/vector-control (version 1.0.1)

--- name: vector-control description: Control a Vector robot via Wirepod’s local HTTP API on the same network. Use when you need to move Vector, tilt head/lift, speak text, capture camera frames, or run patrol/explore routines from the Pi/Wirepod host. Includes a CLI helper script and endpoint reference. --- # Vector Control ## Overview Control Vector through Wirepod’s `/api-sdk/*` endpoints and the camera stream at `/cam-stream`. Use this skill for movement, speech, camera snapshots, patrols, and exploration from the Pi. ## Quick start (CLI) Use the bundled script: ```bash python3 skills/vector-control/scripts/vector_control.py --serial <ESN> assume python3 skills/vector-control/scripts/vector_control.py --serial <ESN> say --text "Hello Dom" python3 skills/vector-control/scripts/vector_control.py --serial <ESN> move --lw 160 --rw 160 --time 1.5 python3 skills/vector-control/scripts/vector_control.py --serial <ESN> snapshot --out /tmp/vector.mjpg ``` ### Find ESN/serial If you don’t have it, read: - `/etc/wire-pod/wire-pod/jdocs/botSdkInfo.json` ## Tasks ### 1) Assume / Release control Always assume before movement, and release if the bot tips or a human needs manual control. ```bash python3 .../vector_control.py --serial <ESN> assume python3 .../vector_control.py --serial <ESN> release ``` ### 2) Movement - `move` sends wheel speeds (0–200 typical). Use short timed moves. ```bash python3 .../vector_control.py --serial <ESN> move --lw 120 --rw 120 --time 1.0 ``` ### 3) Head / Lift ```bash python3 .../vector_control.py --serial <ESN> head --speed -2 --time 1.0 python3 .../vector_control.py --serial <ESN> lift --speed 2 --time 1.0 ``` ### 4) Speech Speech can be interrupted by motion/camera. If it fails, pause after speaking before moving. ```bash python3 .../vector_control.py --serial <ESN> say --text "Sneaking forward" # wait 1–2s, then move ``` ### 5) Camera snapshot `/cam-stream` returns MJPG. Save it and convert to JPEG if needed (ffmpeg). ```bash python3 .../vector_control.py --serial <ESN> snapshot --out /tmp/vector.mjpg ffmpeg -y -loglevel error -i /tmp/vector.mjpg -frames:v 1 /tmp/vector.jpg ``` ### 6) Play Audio (MP3/WAV) Streams an audio file through Vector's speaker. Automatically converts to the required format (8kHz mono WAV). ```bash python3 .../vector_control.py --serial <ESN> play --file /path/to/music.mp3 ``` ### 7) Patrol (deterministic sweep) ```bash python3 .../vector_control.py --serial <ESN> patrol --steps 6 --speed 140 --step-time 1.2 --turn-time 0.8 --speak --phrase "Patrolling" ``` ### 8) Explore (randomized wander) ```bash python3 .../vector_control.py --serial <ESN> explore --steps 8 --speak --phrase "Exploring" ``` ## References - `references/wirepod-api.md` — endpoint list and notes. ## Resources ### scripts/ - `vector_control.py` — CLI for basic control + patrol/explore routines. ### references/ - `wirepod-api.md` — HTTP API endpoints and usage notes.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (MEDIUM)
Skill: teoslayer/pilot-http-proxy (version 1.0.0)

--- name: pilot-http-proxy description: > Route HTTP requests through Pilot Protocol tunnels. Use this skill when: 1. You need to access HTTP services behind NATs or firewalls 2. You want to proxy HTTP traffic through the Pilot overlay network 3. You're exposing local HTTP servers to remote agents Do NOT use this skill when: - Services are already publicly accessible - You need direct HTTP access on the same network - The daemon is not running tags: - pilot-protocol - integration - http - proxy - gateway license: AGPL-3.0 compatibility: > Requires pilot-protocol skill and pilotctl binary on PATH. The daemon must be running (pilotctl daemon start). metadata: author: vulture-labs version: "1.0" openclaw: requires: bins: - pilotctl homepage: https://pilotprotocol.network allowed-tools: - Bash --- # Pilot HTTP Proxy Route HTTP requests through Pilot Protocol tunnels using the gateway subsystem. ## Commands ### Start Gateway ```bash pilotctl --json gateway start ``` ### Map Remote HTTP Service ```bash pilotctl --json gateway map <hostname> <local-ip> ``` ### List Mappings ```bash pilotctl --json gateway list ``` ### Remove Mapping ```bash pilotctl --json gateway unmap <local-ip> ``` ### Stop Gateway ```bash pilotctl --json gateway stop ``` ## Workflow Example ```bash #!/bin/bash # Access remote HTTP API pilotctl --json daemon start pilotctl --json find api-server pilotctl --json gateway start pilotctl --json gateway map api-server 192.168.100.50 # Access remote service curl http://192.168.100.50/api/v1/status curl http://192.168.100.50:8080/metrics ``` ## Port Mapping Gateway forwards common HTTP ports: - Port 80 (HTTP) - Port 443 (HTTPS) - Port 8080 (alternative HTTP) ## Dependencies Requires pilot-protocol skill with running daemon. Root/sudo on Linux for port <1024.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: abdullah944/daily-task-planner-skill (version 0.1.0)

--- name: "Daily Task Planner Skill" version: 0.1.0 slug: "daily-task-planner-skill" description: "Guides structured help for Daily Task Planner using clear templates, checks, and safe defaults (category: Planning & Productivity)." category: "Planning & Productivity" tags: - "daily-task-planner" - "openclaw" - "planning" - "templates" generated: "2026-05-19" --- ## Purpose Guides structured help for Daily Task Planner using clear templates, checks, and safe defaults (category: Planning & Productivity). ## When to use - When you want structured guidance in the "Planning & Productivity" area. - When you need copy-paste-safe templates rather than improvised shell commands. - When you want repeatable prompts the agent can follow without external scraping. ## Safety rules - Do not collect passwords, OTPs, private keys, wallets, seeds, or session secrets. - Do not propose remote installers that execute unseen code or chained download-and-run snippets. - Keep outputs factual and reversible: prefer checklists over irreversible destructive actions. ## Inputs - Your goal in one paragraph (no secrets). - Optional constraints: audience, tone, length, deadline. - Optional pasted notes you own the rights to (keep PII minimal). ## Output format - A concise plan - Numbered checklist - Short next-actions list - Optional draft copy blocks you can edit ## Example prompts - Help me outline a concise plan using the Daily Task Planner approach. - Critique my draft outputs and suggest safer, clearer wording for Daily Task Planner. - Produce a checklist I can reuse weekly for Daily Task Planner without requesting private data. ## Support / Donate If this skill helps your workflow, you can support maintenance here: - PayPal: https://www.paypal.com/donate/?hosted_button_id=MJHCRZA9Z4X7Y


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal:  | SkillSpector: clean (LOW)
Skill: maoruibin/tmp-img (version 1.0.0)

--- name: tmp-img description: 临时图床上传工具。上传图片到临时图床，默认30天过期，获取公开链接。零配置，开箱即用。当用户说"临时上传"、"上传到临时图床"、"tmp upload" 时触发。 --- # tmp-img - 临时图床 上传图片到 imgland.net 临时图床，固定 30 天过期，零配置开箱即用。 ## 触发场景 当用户提到以下需求时触发本技能： - "临时上传图片" / "临时图床" - "tmp upload" / "临时上传" - "上传到临时图床" - "传到临时图床" ## 使用方式 上传一张图片（默认 30 天过期）： ```bash bash ~/.claude/skills/tmp-img/scripts/upload.sh ~/Desktop/screenshot.png ``` 自定义过期时间： ```bash bash ~/.claude/skills/tmp-img/scripts/upload.sh ~/photo.png 7d ``` 支持的过期时间格式：`1d`、`7d`、`30d` 等。 ## 输出 成功后返回 JSON： ```json { "url": "https://api.imgland.net/v1/images/xxx/file", "id": "h463m2O1", "filename": "screenshot.png", "file_size": "377716", "expires_at": "2026-05-11T00:04:15.5834277+00:00", "delete_url": "https://api.imgland.net/v1/images/h463m2O1/file/uXMJd95M..." } ``` 向用户展示时，重点展示： 1. **图片链接** — url 字段 2. **过期时间** — expires_at 字段（转换为可读日期） 3. 提醒用户这是临时图床，图片会在过期时间后自动删除 ## 支持的图片格式 png, jpg, jpeg, gif, webp, bmp ## 依赖 - curl（系统自带） - jq（JSON 解析，通常系统自带） ## 不做什么 - 不编辑图片（裁剪、压缩等） - 不提供批量上传 - 不提供图片管理功能 - 不提供删除功能（图片会自动过期）


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: zlszhonglongshen/github-pr-knowledge-wiki-sync (version 1.0.0)

--- name: github-pr-knowledge-wiki-sync description: GitHub PR 文档自动生成与知识库同步 — 自动抓取PR内容、分析代码变更、生成技术文档并同步到飞书/wiki。 category: 开发 triggers: PR文档, 自动生成文档, PR知识库同步, GitHub文档, 代码变更文档, PR总结 version: 1.0.0 author: OpenClaw Agent tags: - github - documentation - automation - wiki - pr - feishu dependencies: - github - summarize - feishu-wiki - code-review --- # GitHub PR 文档自动生成与知识库同步 一条命令完成：**PR内容抓取 → 代码变更分析 → 技术文档生成 → 飞书Wiki/企业微信文档同步**。 ## 核心价值 - **全自动**：只需提供一个 PR 链接，自动完成全流程 - **代码分析**：智能解读代码变更，提取新增/删除/修改的核心逻辑 - **多格式输出**：支持飞书 Wiki、企业微信文档、Markdown 三种格式 - **团队共享**：生成的文档自动发布到团队知识库，永久留存 ## 适用场景 - 开发者合并 PR 后需要快速生成变更记录 - 技术负责人需要将代码变更同步到团队知识库 - 团队使用飞书或企业微信进行文档管理 - 需要为每次发布生成 changelog 文档 ## 工作流程（4步） ``` Step 1 → 获取 PR 详情（github） ↓ Step 2 → 分析代码变更（code-review） ↓ Step 3 → 生成技术文档（summarize + AI 生成） ↓ Step 4 → 同步到知识库（feishu-wiki / wecom-doc） ``` ## 使用方法 ### 触发词 ``` "生成PR文档 [PR链接]" "PR知识库同步 [PR链接]" "帮我写这个PR的变更文档" "这个PR改了什么，帮我生成文档" ``` ### 完整工作流 **Step 1：获取 PR 信息** ```bash # 使用 github skill 获取 PR 详情 gh pr view <PR_NUMBER> --repo <OWNER/REPO> --json title,body,files,commits ``` **Step 2：分析变更文件** ```bash # 获取变更文件列表 gh pr diff <PR_NUMBER> --repo <OWNER/REPO> ``` **Step 3：生成文档** AI 综合以下信息生成结构化文档： - PR 标题和描述 - 代码变更文件列表 - 关键代码片段 - Commit 历史 **Step 4：同步到知识库** - **飞书 Wiki**：`feishu_wiki` → 在指定知识空间创建或更新文档 - **企业微信**：`wecom-doc` → 在指定文档库创建文档 ## 输出文档结构 ```markdown # [PR标题] ## 📋 基本信息 - **仓库**：`owner/repo` - **PR 编号**：#123 - **作者**：@username - **合并时间**：2026-04-18 - **状态**：✅ Merged ## 📝 变更摘要 （AI 生成的简短摘要，1-3句话） ## 📂 变更文件 | 文件路径 | 变更类型 | 说明 | |---------|---------|------| | src/a.py | ✏️ 修改 | 核心逻辑更新 | ## 🔍 关键代码变更 （列出最重要的代码片段及说明） ## 📌 注意事项 - 需要关注的风险点 - 关联的 Issue 或依赖 ``` ## 注意事项 - 确保 `gh` CLI 已登录：`gh auth login` - 飞书 Wiki 需要有目标知识空间的管理权限 - 企业微信文档需要已创建目标文档库


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: seidprojects/vestaboard (version 1.0.0)

--- name: vestaboard description: Read and write messages on a Vestaboard using the Vestaboard Cloud API (cloud.vestaboard.com) and optional legacy RW endpoint. Use when asked to display text on a Vestaboard, update a sign/board, show a short status message, render simple pixel-art using color/filled character codes, or retrieve the current board message. --- # Vestaboard ## Security - Require a token via environment variables (never inline keys in prompts, logs, or commits). - Preferred: `VESTABOARD_TOKEN` - Optional legacy fallback: `VESTABOARD_RW_KEY` ## Constraints - Flagship Vestaboard layout is **6 rows x 22 cols**. - Text input is formatted to 6x22 by default (uppercase + word wrap; truncates overflow). ## Quick usage (local CLI) ```bash # from repo root npm install # Preview formatting only node scripts/vb.js preview "Hello from Quarterbridge Farm" # Read current message (JSON) node scripts/vb.js read # Write text node scripts/vb.js write "EGGS READY" # Write a numeric layout (6x22 array of character codes) node scripts/vb.js write-layout content/layouts/forest-depth.json ``` ## Sample content - Numeric layouts live in `content/layouts/*.json` - Human review previews live in `content/previews/*.md`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: shenmeng/shenmeng-odds-monitor-2025 (version 1.0.0)

--- name: odds-movement-monitor description: 盘口变化监控助手 - 实时监控足球、篮球等体育赛事的亚盘、欧赔、大小球盘口变化。检测异常波动、大额注单信号、机构态度转变。支持多平台对比、历史趋势分析、自动预警通知。当用户需要监控盘口变化、追踪赔率走势、发现投注机会时使用。 metadata: openclaw: emoji: 📊 --- # Odds Movement Monitor 盘口变化监控 > 💰 **本 Skill 已接入 SkillPay 付费系统** > - 每次调用费用：**0.01 USDT** > - 支付方式：BNB Chain USDT > - 请先确保账户有足够余额 实时监控体育博彩盘口变化，捕捉机构态度转变和异常信号。 ## 核心能力 1. **实时监控** — 多平台盘口数据采集与对比 2. **变化检测** — 盘口升降、水位变动、异常波动识别 3. **趋势分析** — 历史数据追踪、变化轨迹可视化 4. **预警通知** — 关键变化自动提醒 5. **信号识别** — 大额注单信号、诱盘陷阱检测 ## 适用场景 | 场景 | 示例 | |------|------| | **赛前监控** | "监控今晚比赛的盘口变化" | | **异常检测** | "检测突然降盘的场次" | | **对比分析** | "对比多个平台的盘口差异" | | **趋势追踪** | "查看盘口变化历史" | | **机会发现** | "发现盘口错位的比赛" | | **风险控制** | "监控已投注比赛的盘口异动" | ## 监控维度 ### 1. 亚盘监控 (Asian Handicap) - 盘口变化（-0.5 → -0.75） - 水位波动（0.95 → 0.85） - 临场变盘（开场前1小时） - 走地盘口（滚球盘） ### 2. 欧赔监控 (European Odds) - 胜平负赔率变化 - 凯利指数变动 - 返还率异常 - 机构分歧度 ### 3. 大小球监控 (Over/Under) - 盘口升降（2.5 → 2.75） - 水位变化趋势 - 临场升盘/降盘 ### 4. 异常信号 - **大额注单信号**: 短时间内水位急剧下降 - **诱盘信号**: 盘口与基本面背离 - **诱上/诱下**: 盘口刻意引导投注方向 - **交叉盘**: 同时间段相似盘口对比 ## 使用方法 ### 监控单场比赛 ``` 监控 [球队A] vs [球队B] 的盘口变化 ``` ### 批量监控 ``` 监控今晚所有英超比赛的盘口 ``` ### 异常检测 ``` 检测盘口异常变动的比赛 ``` ### 设置预警 ``` 当 [比赛] 盘口变化超过0.25时提醒我 ``` ## 数据源 - **OddsAPI**: 全球赔率聚合 - **Bet365**: 主流平台数据 - **Pinnacle**: 专业玩家平台 - **Smarkets**: 交易所数据 ## 输出格式 监控报告包含： 1. 初始盘口 vs 当前盘口 2. 变化幅度和时间线 3. 异常信号标记 4. 机构态度解读 5. 行动建议（观望/跟进/回避） ## 技术栈 - Python 3.8+ - 数据采集: requests / aiohttp / websocket - 数据存储: SQLite / Redis - 实时监控: asyncio / schedule - 通知推送: webhook / Telegram Bot ## 注意事项 ⚠️ **免责声明**: - 本工具仅供数据监控参考 - 盘口变化可能由多种因素引起 - 请结合基本面分析做决策 ## 文件结构 ``` odds-movement-monitor/ ├── SKILL.md # 本文件 ├── config.json # 配置信息 ├── monitor.py # 主监控脚本 ├── odds_fetcher.py # 数据获取模块 ├── change_detector.py # 变化检测算法 ├── alert_manager.py # 预警管理 └── data_storage.py # 数据存储 ```


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: deepseekoracle/lygo-universal-living-memory-library (version 1.1.0)

--- name: lygo-universal-living-memory-library description: Universal LYGO Living Memory Library upgrade. Provides a strict, low-noise memory index (max 20 files), fragile tagging, and audit/compression workflows so Champions can retain continuity and verify integrity via LYGO-MINT. Pure advisor; not a controller. --- # LYGO Universal Living Memory Library (v1.1) ## What this is A **universal upgrade skill** for LYGO systems that defines a minimal, durable memory library: - **Max 20 files** in the active index (small context footprint) - {FRAGILE} tagging for manual review - An **audit workflow** (integrity + drift checks) - A **compression workflow** (pure signal) - Provenance via **LYGO‑MINT** hashes + anchors This skill is **pure advisor**: it does nothing unless invoked. ## When to use Use when you want to: - define what files are “the living core” - run an audit on those files - compress a large archive into a clean Master Archive - mint+anchor a living memory snapshot ## How to invoke (copy/paste) - “Run **Living Memory Audit** (max20 index) and report drift/fragile flags.” - “Compress these logs into **Master Archive** using Living Memory rules.” - “Mint the Master Archive with LYGO‑MINT and output an Anchor Snippet.” ## Core verifier (install) - https://clawhub.ai/DeepSeekOracle/lygo-mint-verifier ## References - `references/library_spec.md` (rules + file roles) - `references/core_files_index.json` (the Max20 index) - `references/audit_protocol.md` - `references/compression_protocol.md` - `references/seal_220cupdate_excerpt.md` ## Scripts - `scripts/audit_library.py` (runs the audit against the index) - `scripts/self_check.py` (pack sanity)


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: rstierli/nanoleaf (version 1.0.0)

--- name: nanoleaf description: Control Nanoleaf light panels via the Picoleaf CLI. Use for turning Nanoleaf on/off, adjusting brightness, setting colors (RGB/HSL), changing color temperature, or any Nanoleaf lighting control. homepage: https://github.com/tessro/picoleaf metadata: {"clawdbot":{"emoji":"🌈","requires":{"bins":["picoleaf"]},"install":[{"id":"brew","kind":"brew","tap":"paulrosania/command-home","formula":[REDACTED_SECRET],"bins":["picoleaf"],"label":"Install Picoleaf CLI (brew)"},{"id":"binary","kind":"shell","command":"curl -sL https://github.com/tessro/picoleaf/releases/latest/download/picoleaf_1.4.0_linux_amd64.tar.gz | tar xz -C ~/.local/bin","bins":["picoleaf"],"label":"Install Picoleaf (binary)"}]}} --- # Picoleaf CLI Use `picoleaf` to control Nanoleaf light panels. Setup 1. Find Nanoleaf IP: Check router or use mDNS: `dns-sd -Z _nanoleafapi` 2. Generate token: Hold power button 5-7 sec until LED flashes, then within 30 sec run: `curl -iLX POST http://<ip>:16021/api/v1/new` 3. Create config file `~/.picoleafrc`: ```ini host=<ip>:16021 access_token=<token> ``` Power - `picoleaf on` - Turn on - `picoleaf off` - Turn off Brightness - `picoleaf brightness <0-100>` - Set brightness percentage Colors - `picoleaf rgb <r> <g> <b>` - Set RGB color (0-255 each) - `picoleaf hsl <hue> <sat> <light>` - Set HSL color - `picoleaf temp <1200-6500>` - Set color temperature in Kelvin Examples - Warm dim light: `picoleaf on && picoleaf brightness 30 && picoleaf temp 2700` - Bright blue: `picoleaf on && picoleaf brightness 100 && picoleaf rgb 0 100 255` - Turn off: `picoleaf off` Notes - Default port is 16021 - Token generation requires physical access to the Nanoleaf controller - Multiple commands can be chained with `&&`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: dinghaibin/uuid-tool (version 1.0.0)

--- name: uuid-tool description: Generate universally unique identifiers (UUIDs) in versions v1, v4, v5, v7, and nil format, with bulk generation and namespace-based deterministic IDs. --- # UUID Tool — Universal Unique Identifier Generator Generate, parse, and inspect UUIDs across multiple standards. Supports time-based (v1, v7), random (v4), and namespace-based (v5) UUIDs for distributed systems, database keys, and idempotency tokens. ## Quick Start ```bash # Generate a random UUID (v4) uuid-tool --generate v4 # Generate a time-ordered UUID (v7, good for DB indexing) uuid-tool --generate v7 # Generate 10 UUIDs at once uuid-tool --generate v4 --count 10 ``` ## Usage ```bash uuid-tool [COMMAND] [OPTIONS] Commands: --generate VERSION Generate UUIDs (v1, v4, v5, v7) --parse UUID Parse and inspect a UUID string --nil Generate the nil UUID (00000000-...) --from-name TEXT Deterministic UUID v5 from namespace + name Options: --count N Number of UUIDs to generate (default: 1) --namespace NS Namespace for v5: "dns", "url", "oid", "x500", or custom --upper Output uppercase hex --no-hyphens Remove dashes from output --json Output as JSON array ``` ## Examples ```bash # Time-based UUID v1 uuid-tool --generate v1 # Time-ordered UUID v7 (good for DB primary keys) uuid-tool --generate v7 # Deterministic UUID from a domain name uuid-tool --from-name "example.com" --namespace dns # Parse and inspect uuid-tool --parse [REDACTED_SECRET] # Batch generate 100 UUIDs in compact format uuid-tool --generate v4 --count 100 --no-hyphens ``` ## Features - **4 UUID versions:** v1 (time), v4 (random), v5 (SHA-1 namespace), v7 (time-ordered) - **Bulk generation:** Up to 1000 UUIDs in one call - **Deterministic v5:** Same namespace + name → same UUID every time - **Parse & decode:** Extract timestamp, version, variant from any UUID - **Compact mode:** Remove dashes for space-constrained usage - **JSON output:** Easy integration with scripts and APIs - **Nil UUID:** Generate or validate against the all-zero nil UUID


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jxhgzs/bg-remover (version 1.0.0)

--- name: bg-remover description: "Remove, replace, or blur image backgrounds using AI-powered segmentation (rembg/U2-Net). Use when the user asks to: (1) remove image background / make transparent, (2) replace background with a color or another image, (3) blur background like portrait mode, (4) cut out / extract foreground subject from a photo. Triggers on keywords like 抠图, 去背景, 换背景, 背景模糊, 透明背景, remove background, replace background, blur background, cutout." --- # bg-remover — 图片背景处理 基于 rembg (U2-Net) 的本地 AI 抠图工具，支持去除背景、替换背景、背景模糊。 ## 依赖安装 首次使用前运行安装脚本： ```bash bash {baseDir}/scripts/install.sh ``` 或手动安装：`pip install rembg Pillow numpy onnxruntime` ## 命令 所有操作通过 `{baseDir}/scripts/bg_remove.py` 执行： ### 去除背景（输出透明 PNG） ```bash python3 {baseDir}/scripts/bg_remove.py remove <input> [-o output.png] ``` ### 替换背景 ```bash # 纯色背景（支持 hex、rgb、颜色名） python3 {baseDir}/scripts/bg_remove.py replace <input> -c "#FF0000" [-o output.png] python3 {baseDir}/scripts/bg_remove.py replace <input> -c white [-o output.png] # 图片背景 python3 {baseDir}/scripts/bg_remove.py replace <input> -i bg.jpg [-o output.png] ``` ### 背景模糊（人像模式） ```bash python3 {baseDir}/scripts/bg_remove.py blur <input> [-r 15] [-o output.png] ``` `-r` 控制模糊半径，值越大越模糊，默认 15。 ## 输出 - 默认输出路径为原文件名加后缀：`_nobg.png`（去除）、`_newbg.png`（替换）、`_blur.png`（模糊） - 所有输出均为 PNG 格式 - 使用 `-o` 参数自定义输出路径 ## 注意事项 - 首次运行会自动下载 U2-Net 模型（约 170MB），需要网络 - 处理大图可能较慢，建议先缩小再处理 - 抠图效果取决于前景与背景的对比度，简洁背景效果更好


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 52yuanchangxing/dependency-upgrade-briefing (version 1.0.0)

--- name: dependency-upgrade-briefing version: 1.0.0 description: "解释依赖升级的收益、风险、回滚方案与对业务的影响。；use for dependencies, upgrade, risk workflows；do not use for 伪造上游 changelog, 替代兼容性测试." author: OpenClaw Skill Bundle homepage: https://example.invalid/skills/dependency-upgrade-briefing tags: [dependencies, upgrade, risk, engineering] user-invocable: true metadata: {"openclaw":{"emoji":"⬆️","requires":{"bins":["python3"]},"os":["darwin","linux","win32"]}} --- # 依赖升级简报官 ## 你是什么 你是“依赖升级简报官”这个独立 Skill，负责：解释依赖升级的收益、风险、回滚方案与对业务的影响。 ## Routing ### 适合使用的情况 - 帮我解释这次依赖升级值不值得做 - 给老板一版业务影响说明 - 输入通常包含：依赖名称、版本变化、变更摘要 - 优先产出：升级摘要、收益、建议节奏 ### 不适合使用的情况 - 不要伪造上游 changelog - 不要替代兼容性测试 - 如果用户想直接执行外部系统写入、发送、删除、发布、变更配置，先明确边界，再只给审阅版内容或 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` ## 安全边界 - 结论以用户提供信息为准，建议附上 changelog。 - 默认只读、可审计、可回滚。 - 不执行高风险命令，不隐藏依赖，不伪造事实或结果。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: abigale-cyber/content-system-feishu-bitable-sync (version 1.0.0)

--- name: feishu-bitable-sync description: Sync a local `wechat-report` result into Feishu Bitable after the user has reviewed the report and confirmed the sync. --- # feishu-bitable-sync 本 skill 不会自动触发，只有在用户明确确认“发送到飞书”后才运行。 支持输入： - `content-production/inbox/YYYYMMDD-{slug}-wechat-report.md` - `content-production/inbox/raw/wechat-report/YYYY-MM-DD/{slug}.json` 运行前需要配置环境变量： - `FEISHU_APP_ID` - `FEISHU_APP_SECRET` - `FEISHU_BITABLE_APP_TOKEN` - `FEISHU_BITABLE_TABLE_ID` - 可选：`FEISHU_SYNC_AUTH_MODE`，默认 `user` - 可选：`FEISHU_OAUTH_REDIRECT_URI`，默认 `http://127.0.0.1:14578/callback` 默认行为： - 优先读取本机缓存的飞书 `user_access_token` - 若还未授权，会落一份 `auth_required` 回执，并提示先运行 `feishu-user-auth` - 若 token 刷新失败或飞书写入失败，会额外导出 CSV 兜底文件 输出： - `content-production/published/YYYYMMDD-{slug}-feishu-sync.md` - 失败兜底时：`content-production/published/YYYYMMDD-{slug}-feishu-import.csv` 同步策略： - 每篇文章一行 - 使用 `source_url` 去重 - 重复同步会更新已有行，而不是重复新增


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