OpenClaw/clawhub-security-signals huggingface dataset:
Skill: shingwha/tsend (version 2.1.0)

--- name: tsend description: Send files via Telegram. Example: tsend send document.pdf --- # Telegram Sender (tsend) Zero-config CLI tool. Install once, send forever. ## Installation **Tip:** Try using `tsend` command first. If command not found, then install. ### Using uv (recommended) ```bash cd <skill-path>/scripts uv tool install -e . ``` Replace `<skill-path>` with the actual skill path. After installation, `tsend` command is available globally. ### From source (alternative) If you don't have uv: ```bash cd <skill-path>/scripts pip install -e . ``` ## Just use it ```bash tsend send document.pdf tsend send photo.jpg --caption "Description" tsend send image.png -c "Screenshot" # Send multiple files tsend send file1.pdf file2.jpg file3.png tsend send *.pdf --caption "Documents" # caption only goes to first file ``` ### Using specific profile ```bash tsend send file.pdf --profile mybot tsend send photo.png -c "Description" -p picoclaw ``` That's it. No setup, no checks, no questions. ## Only if it fails (once) ```bash tsend config set --token "YOUR_BOT_TOKEN" --chat-id "YOUR_CHAT_ID" ``` Or specify a profile: ```bash tsend config set --profile mybot --token "TOKEN" --chat-id "CHAT_ID" tsend config default mybot # Set as default ``` The tool saves config to `~/.tsend/config.json`. ## Multiple Profiles Manage multiple bots with profiles: ```bash # List all profiles tsend config list # Show specific profile tsend config show --profile mybot # Send with specific profile tsend send file.pdf --profile mybot ``` ## Environment Variable Set default profile via environment: ```bash export TSEND_PROFILE=mybot tsend send file.pdf # Uses 'mybot' profile ``` Useful for different services (nanobot, picoclaw, etc.). ## When something's wrong **"token invalid"** → Fix with one command: ```bash tsend config set --token NEW_TOKEN --chat-id NEW_ID ``` No reinstall, no config file hunting.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: axelhu/openclaw-todo-list (version 1.0.0)

--- name: todo-list version: 1.0.0 description: 通用待办事项管理技能。记录需要做的事（TODO）和已完成的事（DONE），区分于日记的日常记录。触发时机：(1) 有明确任务时 (2) 任务完成时 (3) 用户要求查看进度。 --- # TODO List 通用待办事项管理，区别于日记的每日记录。 ## 核心原则 - **有明确任务才记**：不是每日流水账，是有目标的工作 - **简洁记录**：简单描述，不堆砌细节 - **主动更新**：有进展时主动更新，不用等问 ## 文件结构 ``` memory/todo/ ← TODO文件存放目录 ├── TODO.md ← 待办事项（进行中 + 待做） └── DONE.md ← 已完成事项（单独存档） skills/todo-list/ ← 技能目录 ├── SKILL.md ← 本技能说明 └── references/ ├── spec.md ← 详细规范 └── example-todo.md ← 示例文件（可参考） ``` **注意**：实际使用只需关注 `memory/todo/` 下的两个文件。 ## 文件格式 ### TODO.md 格式 ```markdown # TODO ## 待做 - [ ] 任务描述 · 原因 · 添加日期 @负责人 - [ ] 任务描述 · 原因 · 添加日期 @负责人 ## 进行中 - [ ] 任务描述 · 原因 · 开始日期 @负责人 ``` ### DONE.md 格式 ```markdown # DONE ## 已完成 - [x] 任务描述 · 如何完成 · 完成日期 @负责人 ``` ## 记录规范 ### 添加 TODO **格式**：`- [ ] 任务描述 · 原因 · 日期 @负责人` **示例**： ``` - [ ] 调研竞品项目X · 了解行业最佳实践 · 2026-03-20 @agent-01 ``` **何时添加**： - 用户明确分配任务 - 自己判断需要做的工作 - 计划中要完成的事项 ### 标记为进行中 **格式**：移动到"进行中"区域 **何时标记**： - 开始处理这个任务 - 不是等完成才更新 ### 标记为 DONE **格式**：移动到 DONE.md，补充完成信息 **DONE 格式**：`- [x] 任务描述 · 如何完成 · 完成日期 @负责人` **示例**： ``` - [x] 编写技能文档 · 按模板创建SKILL.md和spec.md · 2026-03-20 @agent-01 ``` **何时标记**： - 任务完成 - 交付物已发送 - 结果已记录 ## 与日记的区别 | | TODO List | 日记 | |---|---|---| | **内容** | 明确的任务项 | 每日工作流水 | | **触发** | 有任务时记录 | 每次会话结束/每天记录 | | **重点** | 待做/已完成状态 | 过程、思考、决策 | | **粒度** | 简洁，一行 | 详细，记录怎么做 | ## 主动更新原则 **不需要等问，有进展就更新：** - 开始做 → 移动到"进行中" - 遇到问题 → 记录问题在 TODO 旁边 - 完成 → 移动到 DONE.md ## 查看进度 直接读取： - `memory/todo/TODO.md` — 待办 - `memory/todo/DONE.md` — 已完成 ## 常用命令 ```bash # 查看待办 cat memory/todo/TODO.md # 查看已完成 cat memory/todo/DONE.md # 添加待办（直接编辑文件） # 或使用 edit 工具修改 ``` ## 触发示例 - "把这个任务加到 TODO" - "任务完成了，移到 DONE" - "看看现在有哪些待办" - "有新的 TODO 需要记录吗"


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

--- name: agent-git-oracle description: "Advanced repository analysis and refactoring guide. Identifies technical debt and architectural anti-patterns using AI reasoning." metadata: { "openclaw": { "emoji": "🔮" }, "author": "System Architect Zero", "category": "Developer Tools", "x402": { "fee": 0.10, "currency": "USDC", "network": "base" } } --- # Agent Git Oracle Take your codebase from legacy to sovereign. This skill performs deep-scan audits of your local git repositories, identifying areas of high complexity, potential logic leaks, and opportunities for Agent-Native refactoring. ## Features - **Debt Detection**: Highlights "Dirty Code" that increases cognitive load. - **Agentic Mapping**: Suggests how to convert traditional modules into autonomous tools. - **Commit Wisdom**: Summarizes the "Why" behind large architectural shifts in your project. ## Usage ```bash npx openclaw skill run agent-git-oracle --path ./your-repo ``` ## Why it costs $0.10? To fund the compute required for deep structural analysis.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: xyezir/oc-approval-free-node-stabilizer (version 0.1.0)

--- name: oc-approval-free-node-stabilizer description: Stabilize no-approval node execution in OpenClaw. Use when approval timeout, noisy failure events, or node run drift appears. --- # OC Approval-Free Node Stabilizer ## When to use - `approval timed out` - node run succeeds but delayed failure events confuse users - mixed behavior across multiple nodes ## Objectives - consistent execution policy across nodes - low-noise operation for routine commands - explicit confirmation path for high-risk operations ## Procedure 1. Confirm effective approval policy on target node(s). 2. Standardize execution path (nodeId-first, serial runs, one retry). 3. Add noisy-event handling rule: retry before user-facing alert. 4. Validate with minimal command set and status checks. ## Output - Policy snapshot - Validation results - Exceptions that still need human approval ## Guardrails - High-risk actions still require explicit chat confirmation. - Do not publish credentials or identifying infra details.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: biogod2020/web-freedom-toolkit (version 8.0.0)

--- name: web-freedom-toolkit description: "Universal Server-Side Web Freedom Toolkit. Harmonizes Scrapling (Self-Healing Fetch), curl_cffi (TLS Impersonation), and DrissionPage (D-Mode) for undetectable browsing on restricted VPS environments." metadata: openclaw: emoji: 🕊️ disable-model-invocation: true requires: bins: ["google-chrome-stable", "xvfb-run", "dbus-launch"] python: ["scrapling", "curl_cffi", "DrissionPage", "lxml"] --- # Web Freedom Toolkit (SOTA v8.0.0) This toolkit is a generalized evolution of the Drission agent, designed for **Total Web Freedom** in server-side environments. ## 🚀 The Three-Tier Offensive Strategy 1. **Tier 1: Scrapling (Lightning Fetch)** Uses the `scrapling` engine to perform self-healing, high-speed stealth fetches. Ideal for bypassing Cloudflare and standard WAFs without a full browser. 2. **Tier 2: CFFI Impersonation (Phantom Protocol)** Uses `curl_cffi` for kernel-level TLS/JA4 fingerprinting to mimic real browser handshake patterns. 3. **Tier 3: Deep Interaction (D-Mode)** Full Chromium control for sites requiring visual AI interaction or complex JavaScript execution. ## 🛠️ Usage Execute the unified freedom engine: ```bash python3 scripts/freedom_engine.py "https://target-site.com" ``` ## 🛡️ Security Governance Same hardened physical gating applies to all Tier 3 interactions. --- **Version**: 8.0.0 (General Freedom) | **Author**: Biogod2020 | **Status**: PROD


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: hjfl888/legal-document-generator (version 3.0.4)

# 法律文书生成器 v3.0（完全免费版） --- ## 功能介绍 根据用户需求，自动生成53种法律文书模板，覆盖婚姻、劳动、债务、合同、房产等全场景。 **完全免费，无需付费，下载即用！** --- ## 包含文书（53种） ### 📋 婚姻家庭类（10项） 1. 离婚协议书 2. 离婚起诉状 3. 婚姻关系存续期间财产约定协议 4. 同居关系解除及财产分割协议 5. 子女抚养权变更协议 6. 探望权行使协议 7. 抚养费变更协议 8. 夫妻共同债务清偿协议 9. 婚前财产协议 10. 遗产分割协议 ### 💼 劳动争议类（12项） 11. 劳动合同（固定期限） 12. 劳动合同（无固定期限） 13. 劳动合同（完成一定任务为期限） 14. 解除劳动合同协议书 15. 劳动合同终止协议 16. 竞业限制协议 17. 保密协议 18. 培训服务期协议 19. 劳务派遣协议 20. 实习协议 21. 离职证明 22. 劳动仲裁申请书 ### 💰 债务纠纷类（8项） 23. 借款合同（个人） 24. 借款合同（公司） 25. 还款协议 26. 催收律师函 27. 债务转让协议 28. 债权转让通知 29. 担保合同 30. 逾期还款承诺书 ### 📝 民事商务类（15项） 31. 买卖合同 32. 委托代理合同 33. 居间合同 34. 服务合同 35. 承揽合同 36. 运输合同 37. 仓储合同 38. 投资合作协议 39. 合伙协议 40. 股权转让协议 41. 和解协议 42. 调解协议 43. 赠与合同 44. 借用合同 45. 悬赏广告发布声明 ### 🏠 房产交易类（8项） 46. 房屋买卖合同 47. 房屋租赁合同 48. 房屋抵押合同 49. 商铺租赁合同 50. 房屋托管协议 51. 装修合同 52. 物业服务合同 53. 车位租赁协议 --- ## 使用流程 ### Step 1：确认需求 用户说："帮我生成一份离婚协议书" ### Step 2：收集必要信息 根据文书类型，询问必要信息： **通用必填项** - 甲方姓名、身份证号、联系方式 - 乙方姓名、身份证号、联系方式 - 签订日期 - 签订地点 **专项信息**（根据文书类型） ### Step 3：生成文书 输出完整文书，包含： - 标题 - 双方信息 - 正文条款 - 签署栏 - 法律提示（可选） --- ## 各文书详细要求 ### 婚姻家庭类 #### 离婚协议书 必填信息： - 双方姓名、身份证号 - 结婚登记日期 - 子女数量、姓名、出生日期 - 子女抚养权归属 - 抚养费金额及支付方式 - 探望权安排 - 夫妻共同财产清单及分割方案 - 夫妻共同债务清单及承担方案 #### 专业提示（免费提供） - 财产分割的具体操作建议 - 子女抚养费调整机制建议 - 探视权的具体执行方案 ### 劳动争议类 #### 劳动合同 必填信息： - 用人单位名称、统一社会信用代码、地址 - 员工姓名、身份证号、住址 - 合同期限（起始日期、终止日期） - 工作内容、工作地点 - 工作时间（标准工时、综合工时、不定时） - 劳动报酬（基本工资、绩效、奖金等） - 工资发放日期 - 社会保险缴纳 #### 专业提示（免费提供） - 试用期约定的合法性检查 - 竞业限制条款的合理性建议 ### 债务纠纷类 #### 借款合同 必填信息： - 出借人/借款人姓名、身份证号 - 借款金额（大写） - 借款用途 - 借款期限（起止日期） - 利率（年利率/月利率） - 还款方式 - 担保方式（信用/抵押/质押） - 送达地址 #### 专业提示（免费提供） - 利率约定的法律上限提示 - 担保条款的完善建议 ### 民事商务类 #### 买卖合同 必填信息： - 出卖人/买受人信息 - 货物名称、规格、型号、数量 - 单价、总价 - 质量标准 - 交付时间、地点、方式 - 付款时间、方式 - 验收标准 - 违约责任 ### 房产交易类 #### 房屋买卖合同 必填信息： - 甲方/乙方信息 - 房屋地址、建筑面积、权属证号 - 房屋现状 - 成交价格 - 付款方式、付款节点 - 房屋交付时间 - 过户条件 - 税费承担 - 违约责任 --- ## 输出格式 ```markdown # [文书名称] ## 基本信息 | 项目 | 内容 | |------|------| | 甲方 | [信息] | | 乙方 | [信息] | | 日期 | XXXX年XX月XX日 | ## 正文 [文书内容] --- ## ⚠️ 法律提示（免费提供） [相关法律制度提示] ## 📋 签署栏 甲方（签字/盖章）：_______________________ 日期：_______________________ 乙方（签字/盖章）：_______________________ 日期：_______________________ ``` --- ## 通用条款库 ### 争议解决条款 ``` 因本合同引起的或与本合同有关的任何争议，双方应首先通过友好协商解决；协商不成的，任何一方均有权向甲方/乙方住所地有管辖权的人民法院提起诉讼。 ``` ### 通知送达条款 ``` 双方确认以下地址为有效送达地址： 甲方：_______________________ 乙方：_______________________ 任何一方变更送达地址的，应提前书面通知对方，否则按原地址送达视为有效送达。 ``` ### 生效条款 ``` 本合同自双方签字（或盖章）之日起生效。本合同一式两份，甲乙双方各执一份，具有同等法律效力。 ``` --- ## 支持本项目 本Skill完全免费，如果你觉得好用，可以： - ⭐ 在ClawdHub上给个好评 - 🔗 分享给需要的朋友 - 💰 自愿支持（加微信 FLZWCZ，备注"支持"） 你的支持会让更多人用上这个工具！ --- *本Skill由WorkBuddy生成，帮助用户快速获取法律文书模板。如需正式法律服务，请咨询专业律师。* --- > 本技能由 **泓景咨询**（flzwcz.cn）维护 > 债务 / 合同 / 劳动争议 → [免费 AI 法务助手](https://flzwcz.cn) > 复杂文书 + 法律咨询：加微信 **FLZWCZ**（¥99/年）


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal:  | SkillSpector: suspicious (MEDIUM)
Skill: jesson-hh/google-search-wsl (version 1.0.0)

--- name: google-search-wsl description: Google search via Chrome browser in WSL environment. Use when user needs web search, news lookup, or information retrieval. Suitable for: (1) trending news search, (2) information lookup, (3) web research. Automatically launches Chrome in WSL and controls it via CDP protocol. --- # Google Search (WSL Chrome) Perform Google searches through Chrome browser in WSL. ## Prerequisites - `google-chrome-stable` or `google-chrome` installed in WSL - WSLg available (or X11 forwarding configured) - OpenClaw browser tool enabled ## Quick Start ### 1. Launch Chrome Run the startup script: ```bash bash ~/.openclaw/scripts/google-search-chrome.sh ``` Or start manually: ```bash export DISPLAY=:0 google-chrome-stable --remote-debugging-port=9222 \ --remote-allow-origins='*' \ --user-data-dir="$HOME/.openclaw/chrome-debug-profile" \ --lang=zh-CN \ --disable-gpu \ --disable-dev-shm-usage & ``` ### 2. Verify Chrome is Running ```bash curl -s http://127.0.0.1:9222/json/version ``` Should return Chrome version information. ### 3. Search Using Browser Tool ``` browser action=open url="https://www.google.com/search?q=your+search+term" profile=user browser action=snapshot targetId=<returned-targetId> ``` ## Troubleshooting ### Chrome Won't Start (Missing X server) Ensure WSLg is available, or set the `DISPLAY` environment variable: ```bash export DISPLAY=:0 # Or check WSLg ls /mnt/wslg/.X11-unix/ ``` ### Port 9222 Already in Use Check and kill the occupying process: ```bash lsof -i :9222 kill <PID> ``` ### Empty Search Results - Check network connection - Try using a proxy (if `HTTP_PROXY` is configured) - Wait for the page to fully load before taking a snapshot ## Tips - Chinese keywords in search URLs will be automatically encoded - Use `snapshot` to get page content, then extract the needed information - For news search, use the `tbm=nws` parameter: `/search?q=keyword&tbm=nws`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: itsnishi/vet-repo (version 1.1.1)

--- name: vet-repo description: Scan repository agent configuration files for known malicious patterns disable-model-invocation: true allowed-tools: Read, Glob, Grep, Bash context: fork --- # vet-repo -- Repository Agent Config Scanner Scan all agent configuration files in a repository for known malicious patterns. Use this when entering an unfamiliar codebase to assess agent-level security risks before trusting the repo's configurations. ## What to do Run the scanner script against the current project root: ```bash python3 "$SKILL_DIR/scripts/vet_repo.py" "$PROJECT_ROOT" ``` Where `$SKILL_DIR` is the directory containing this SKILL.md, and `$PROJECT_ROOT` is the root of the repository being scanned. ## What it scans - `.claude/settings.json` -- hook configs (auto-approve, stop loops, env persistence) - `.claude/skills/` -- all SKILL.md files (hidden comments, curl|bash, persistence triggers) - `.mcp.json` -- MCP server configs (unknown URLs, env var expansion, broad tools) - `CLAUDE.md` / `.claude/CLAUDE.md` -- instruction injection in project config ## Output Structured report with findings grouped by severity (CRITICAL, HIGH, MEDIUM, LOW, INFO) and actionable recommendations for each finding. ## When to use - Before trusting a cloned repository's agent configurations - After pulling changes that modify `.claude/` or `.mcp.json` - As part of a security review of any codebase with agent integration ## Advisory hooks This repository includes PreToolUse hooks in `.claude/settings.json` that warn on dangerous Bash commands (pipe-to-shell, `rm -rf /`, `chmod 777`, eval with variables, base64-to-execution) and sensitive file writes (`.ssh/`, `.aws/`, `.gnupg/`, shell profiles, `settings.json`). These hooks are **advisory only** -- they produce warning messages but do not block execution. An agent or user can proceed past the warning. - The hooks are a supplementary signal, not an enforcement layer - vet-repo is the primary detection mechanism for repo-level threats - Deterministic blocking requires changing the hook to return `{"decision": "block"}` instead of a warning message - See `.claude/settings.json` for the current hook definitions


Security scan verdicts — ClawScan: clean | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: shinelp100/stock-data-monorepo (version 1.2.5)

--- name: stock-data-monorepo description: | A 股数据查询技能集合，包含 4 个子技能：cn-stock-volume（成交量）、stock-top-gainers（涨幅排名）、ths-stock-themes（题材概念）、stock-theme-events（题材事件）。 **触发场景**: - 作为 stock-daily-report 的数据源依赖 - 单独查询股票数据时 metadata: { "emoji": "📈", "requires": { "bins": ["python3"], "tools": ["browser"] }, "install": [ { "id": "akshare", "kind": "pip", "package": "akshare" }, { "id": "sentence-transformers", "kind": "pip", "package": "sentence-transformers" }, { "id": "scikit-learn", "kind": "pip", "package": "scikit-learn" } ], "sub_skills": ["cn-stock-volume", "stock-top-gainers", "ths-stock-themes", "stock-theme-events"] } --- # Stock Data Monorepo - A 股数据查询技能集合 统一的 A 股数据查询技能集合，包含 4 个相关技能。 ## 📦 包含的技能 | 技能名称 | 功能 | 版本 | |----------|------|------| | **cn-stock-volume** | 获取四市（沪市/深市/创业板/北交所）成交金额、放缩量、涨跌家数 | v1.2.2 | | **stock-top-gainers** | 获取近 10 日个股涨幅排名（前 20 只，排除 ST） | v1.0.0 | | **ths-stock-themes** | 获取同花顺个股题材/概念板块和人气排名数据 | v1.0.0 | | **stock-theme-events** | 获取 A 股市场炒作题材对应的真实新闻事件 | v1.0.3 | ## 🚀 使用方式 本 Monorepo 是一个技能集合，建议在 `stock-daily-report` 等上层技能中通过调用各子技能的脚本使用： ```bash # 设置路径变量（推荐） STOCK_DATA_PATH=~/.hermes/skills/stock-data-monorepo # 查询四市成交量 python3 $STOCK_DATA_PATH/cn-stock-volume/scripts/fetch_data.py # 获取近 10 日涨幅排名 python3 $STOCK_DATA_PATH/stock-top-gainers/scripts/fetch_gainers.py # 查询股票题材 python3 $STOCK_DATA_PATH/ths-stock-themes/scripts/fetch_themes.py [股票代码] # 生成题材事件报告 python3 $STOCK_DATA_PATH/stock-theme-events/scripts/generate_report.py ``` ## 📊 技能依赖关系 ``` stock-daily-report (上层应用) ├── cn-stock-volume ⭐ (必需 - 指数数据) ├── stock-top-gainers ⭐ (必需 - 涨幅排名) ├── ths-stock-themes ⭐ (必需 - 题材数据) └── stock-theme-events (可选 - 深度分析) ``` ## 目录结构 ``` stock-data-monorepo/ ├── SKILL.md # 本文件 ├── cn-stock-volume/ # 成交量数据 │ ├── SKILL.md │ └── scripts/ │ └── fetch_data.py ├── stock-top-gainers/ # 涨幅排名 │ ├── SKILL.md │ └── scripts/ ├── ths-stock-themes/ # 题材概念 │ ├── SKILL.md │ └── scripts/ └── stock-theme-events/ # 题材事件 ├── SKILL.md └── scripts/ ``` ## ⚠️ 注意事项 1. **数据时效性**：所有数据均为实时或 T+1 数据，建议在报告中注明数据获取时间 2. **ST 股票**：涨幅排名自动排除 ST 股票，其他技能需手动过滤 3. **依赖安装**： ```bash pip install akshare sentence-transformers scikit-learn ``` 4. **browser 工具**：部分技能需要 browser 工具访问网页获取数据 ## 📝 更新日志 ### v1.2.3 (2026-04-16) - 添加 YAML frontmatter 元数据 - 修正硬编码路径为可配置路径 ### v1.2.2 (2026-03-21) - **cn-stock-volume**: 修复非交易日数据处理逻辑，自动使用最近交易日数据 - **stock-top-gainers**: 新增完整脚本（browser_fetch.py, fetch_gainers.py, parse_snapshot.py） - **stock-theme-events**: 新增 run_full_analysis.py 完整分析脚本 ### v1.2.1 (2026-03-21) - Monorepo 合并，统一目录结构


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: clawdiri-ai/pack-monet-works (version 1.0.0)

--- name: Monet Works Content Pack description: > Content quality and compliance tools for financial writing. Automated QA remediation pipeline detects and fixes banned phrases, missing disclaimers, missing CTAs, and excessive length. metadata: pack: true includes: - monet-works-content-qa-dv - ogilvy-humanizer-dv --- # Monet Works Content Pack Professional content quality pipeline for financial writers and creators. ## Included Skills 1. **Content QA Remediation** — Auto-fix banned phrases, add disclaimers, enforce CTAs 2. **Humanizer** — Remove 24 patterns of AI-generated writing ## Quick Start ```bash clawhub install monet-works-content-qa-dv clawhub install ogilvy-humanizer-dv ``` ## License MIT


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: lin-shiwu/annual-insurance-word-report (version 1.0.0)

--- name: annual-insurance-word-report-openclaw description: Generate annual insurance welfare Word reports from `gh_hg_bscyearall_dues` in OpenClaw format. The packaged Python entry extracts the target year, inspects MySQL column comments, maps business fields into the bundled Word template, and writes the final `.docx` report. --- # Annual Insurance Word Report ## What this package does - Resolves the target year from `year` or from `request_text` - Queries `gh_hg_bscyearall_dues` - Reads `INFORMATION_SCHEMA.COLUMNS` comments before rendering - Fills the bundled yearly Word template without depending on Word COM - Writes the finished `.docx` file to `outputs/` by default ## Inputs - `request_text`: optional natural-language request, for example `帮我生成2023年业务报告` - `year`: optional explicit year, for example `2023` - `template_path`: optional custom `.docx` template path - `output_path`: optional custom output `.docx` path - `db_host`: optional, default `127.0.0.1` - `db_port`: optional, default `3306` - `db_user`: optional, default `root` - `db_password`: optional, default `root` - `database`: optional, default `test_db` - `table_name`: optional, default `gh_hg_bscyearall_dues` - `charset`: optional, default `utf8mb4` - `mysql_cli`: optional fallback path to `mysql` CLI if `PyMySQL` is unavailable ## Run Install dependencies: ```bash pip install -r requirements.txt ``` Run with an explicit year: ```bash python src/main.py --year 2023 ``` Run with request text extraction: ```bash python src/main.py --request-text "帮我生成2023年业务报告" ``` Custom database example: ```bash python src/main.py --year 2023 --database test_db --db-user root --db-password root ``` ## Notes - The default output path is `outputs/annual-insurance-report-<year>.docx`. - The default template is stored as text in `assets/beijing_office_annual_template.docx.base64.txt` and is restored to a temporary `.docx` at runtime. - The package keeps the original business mapping: `团意、子女、女工、重疾、轻症、住院、津贴、补充、两癌、综合A、综合B、合计`. - If `PyMySQL` is not installed, the entry falls back to the `mysql` CLI when `mysql_cli` is provided or `mysql` is on `PATH`.

path: requirements.txt
content: PyMySQL>=1.1,<2


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: clawkk/cache-layer (version 1.0.0)

--- name: cache-layer description: "Cache layers, TTLs, invalidation, and consistency. Use when speeding reads or debugging stale data." --- # Cache Layer Structured guidance for **cache layers** (TTLs, invalidation, consistency): confirm triggers, propose the stages below, and adapt if the user wants a lighter pass. ## When to Offer This Workflow **Trigger conditions:** - User mentions **caching**, **cache invalidation**, or closely related work - They want a structured workflow rather than ad-hoc tips - They are preparing a review, rollout, or stakeholder communication **Initial offer:** Explain the four stages briefly and ask whether to follow this workflow or work freeform. If they decline, continue in their preferred style. ## Workflow Stages ### Stage 1: Clarify context & goals Anchor on **what to cache and TTL rationale**. Ask what success looks like, constraints, and what must not break. Capture unknowns early. ### Stage 2: Design or plan the approach Translate goals into a concrete plan around **invalidation patterns**. Compare alternatives and explicit trade-offs; avoid implicit assumptions. ### Stage 3: Implement, validate, and harden Execute with verification loops tied to **consistency and thundering herds**. Prefer small steps, measurable checks, and rollback points where risk is high. ### Stage 4: Operate, communicate, and iterate Close the loop with **monitoring hit rate and staleness**: monitoring, documentation, stakeholder updates, and lessons learned for the next cycle. ## Checklist Before Completion - Goals and constraints are explicit for **cache layers** - Risks and trade-offs are stated, not hand-waved - Verification steps match the change’s impact (tests, canary, peer review) - Operational follow-through is covered (monitoring, docs, owners) ## Tips for Effective Guidance - Be procedural: stage-by-stage, with clear exit criteria - Ask for missing context (environment, scale, deadlines) before prescribing - Prefer checklists and concrete examples over generic platitudes - If the user declines the workflow, switch to freeform help without lecturing ## Handling Deviations - If the user wants to skip a stage: confirm and continue with what they need. - If context is missing: ask targeted questions before strong recommendations. - Prefer concrete examples, trade-offs, and verification steps over generic advice. ## Quality Bar - Each recommendation should be **actionable** (what to do next). - Call out **failure modes** relevant to cache layers (security, scale, UX, or ops). - Keep tone direct and respectful of the user’s time.


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