OpenClaw/clawhub-security-signals huggingface dataset:
Skill: bettersao/mail-imap-sync (version 1.0.3)

--- name: mail-imap-sync description: > 高性能 IMAP 邮件同步工具。支持多邮箱账号、增量同步、时间窗口过滤（recent/since/init 三模式），不影响邮箱邮件的阅读状态，只做本地拉取邮件分析和提炼功能。 自动将邮件解析为 Markdown 文件并按 年/月/日 树状结构存储。本工具具备去重、断点恢复、时区统一（Asia/ShangHai） 和高性能服务器过滤能力，适合构建邮件知识库、AI总结系统、通知系统等场景。 version: 3.0 inputs: [] outputs: * name: synced_emails description: 本次同步成功保存的邮件文件路径列表 --- # 📬 Mail IMAP Sync Skill ## 🧠 功能概述 本技能用于： * 📥 从 IMAP 邮箱同步邮件（支持 Gmail / 企业邮箱） * ⚡ 高性能拉取（服务器端过滤，不扫全量） * 🔁 自动增量（基于 UID） * 🧱 本地结构化存储（Markdown + 时间分层） * 🧠 为 AI 提供可读邮件数据源 --- ## 🚀 支持的同步模式 ### 🥇 1. init（纯增量模式） ```json "mode": "init" ``` * 第一次运行：不拉历史邮件 * 后续：只同步新邮件 👉 适合长期运行系统 --- ### 🥈 2. recent（推荐） ```json "mode": "recent", "recent_days": 7 ``` * 第一次：拉取最近 N 天邮件 * 后续：自动增量 👉 推荐用于 AI 分析 / 日报 --- ### 🥉 3. since（指定日期） ```json "mode": "since", "since": "2026-01-01" ``` * 第一次：拉取指定日期之后邮件 * 后续：增量同步 👉 用于历史导入 --- ## 📁 存储结构 邮件以 Markdown 格式存储： ``` emails/ {account}/ YYYY/ MM/ DD/ UID_MessageID_标题.md ``` --- ## 🧾 邮件结构（标准化） 每封邮件包含： ``` # Subject From: xxx Date(raw): 原始时间 Date(local): 本地时间（Asia/ShangHai） Date(ISO): ISO标准格式 Timestamp: Unix时间戳 UID: xxx Message-ID: xxx Account: xxx --- 正文内容 ``` --- ## ⏱ 时间处理（核心特性） * 自动解析各种邮件时间格式 * 统一转换为： * Asia/ShangHai 时区 * ISO标准格式 * 时间戳（用于排序/分析） 👉 保证 AI 可稳定理解时间 --- ## ⚡ 性能优化 本技能使用： * IMAP SEARCH SINCE（服务器过滤） * UID 增量同步 * 避免扫描整个邮箱 👉 支持万级邮件秒级同步 --- ## 🔁 去重机制 * UID 去重 * Message-ID 去重 * 文件存在即跳过 --- ## 🧱 稳定性保障 * state.json 原子写入（防损坏） * Ctrl+C 不会丢状态 * 自动检测异常状态并修复 * 支持断点恢复 --- ## ⚙️ 配置方式（config.json） ```json { "accounts": [ { "name": "bettermsao", "imap_host": "imap.gmail.com", "user": "[REDACTED_SECRET]", "pass": "应用专用密码", "mode": "recent", "recent_days": 7 } ] } ``` --- ## ▶️ 运行方式 ```bash ./run.sh ``` --- ## 📤 输出说明 返回： ```json { "synced_emails": [ "emails/.../xxx.md" ] } ``` --- ## 🧩 适用场景 * 📊 邮件数据分析 * 🤖 AI 邮件总结（日报 / 周报） * 🚨 重要邮件监控 * 🧠 本地 LLM 数据输入 --- ## 🔮 可扩展方向 * 邮件自动总结（LLM） * 分类（订单 / 客户 / 系统） * 向量化（语义搜索） * 通知推送（微信 / Telegram） * 多邮箱聚合分析 --- ## ⚠️ 注意事项 * Gmail 需开启 IMAP 并使用应用专用密码 * 企业邮箱可能限制 IMAP 频率 * 初次运行建议使用 recent 模式 --- ## 🏁 总结 本技能将邮件系统转化为： 👉 可结构化存储 👉 可被 AI 理解 👉 可持续增量更新


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: wizelements/surplus-funds-recovery (version 1.0.0)

--- name: surplus-funds-recovery version: 1.0.0 description: Turn unclaimed government funds into passive income. Automated scanning, skip-tracing, SMS outreach, e-signature capture, and claim filing. category: Business Automation tags: [passive-income, automation, real-estate, sms, skip-tracing] author: Cod3Black <[REDACTED_SECRET]> repository: https://github.com/cod3black/surplus-funds-recovery license: MIT pricing: oneTime: 79 subscription: 19 currency: USD requirements: - Termux (Android) or Linux environment - Node.js v16+ - OpenClaw agent system - API keys: Intelius, Twilio, RabbitSign --- # Surplus Funds Recovery System Turn unclaimed government funds into passive income with this complete automation system. ## The Business Model - Property foreclosures create surplus funds (sale price > taxes owed) - Previous owners usually don't know this money exists - You find it, contact them, file claims, earn 20-30% finder's fee - Example: $223K surplus → $56K fee in ~30 minutes of work ## What's Included - Automated county record scanning (Fulton County GA) - Skip-tracing integration (Intelius/TrueCaller APIs) - SMS outreach templates with compliance safeguards - Digital signature capture (RabbitSign/DocuSign) - Auto-populated claim form generation - Payment tracking & split calculation - Full audit trail for compliance ## ROI Example - 1 case/week = $290K/year (mostly passive after filing) - Cost per case: $3-5 (skip trace + SMS) - Your fee: 20-30% of surplus amounts ## Quick Start ```bash # Configure your business export BUSINESS_NAME="Your Recovery Business" export YOUR_FEE_PERCENT=25 export YOUR_PHONE="+1-XXX-XXX-XXXX" # Run automated scan npm run scan-fulton --min-amount 10000 # Review flagged high-value cases cat surplus-cases.json | jq '.[] | select(.amount > 50000)' # Auto-skip-trace and send compliant SMS node scripts/skip-trace-owner.js --case CASE-123 node scripts/send-sms-campaign.js --case CASE-123 --template standard ``` ## Requirements - Termux (Android) or Linux environment - Node.js v16+ - OpenClaw agent system - API keys: Intelius, Twilio, RabbitSign ## Support Email: [REDACTED_SECRET]


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal:  | SkillSpector: suspicious (HIGH)
Skill: edibez/priceforagent (version 1.1.0)

--- name: priceforagent description: Get real-time prices for crypto, stocks, and commodities. Use when the user asks about asset prices, market data, or needs to check the value of Bitcoin, Ethereum, stocks like NVDA/AAPL, or commodities like gold/silver. Supports natural language queries ("What's the price of Bitcoin?") and direct lookups. --- # Price for Agent LLM-friendly price service for crypto, stocks, and commodities. **Base URL:** `https://p4ai.bitharga.com` ## Quick Start ### 1. Register for API Key ```bash curl -X POST https://p4ai.bitharga.com/v1/register \ -H "Content-Type: application/json" \ -d '{"agent_id": "my-agent"}' ``` Response: ```json {"api_key": "pfa_xxx...", "message": "API key generated successfully"} ``` ### 2. Query Prices **Natural language:** ```bash curl -X POST https://p4ai.bitharga.com/v1/query \ -H "X-[REDACTED_SECRET]" \ -H "Content-Type: application/json" \ -d '{"query": "What is the price of Bitcoin and Ethereum?"}' ``` **Direct lookup:** ```bash curl -H "X-[REDACTED_SECRET]" https://p4ai.bitharga.com/v1/price/bitcoin ``` **Batch:** ```bash curl -X POST https://p4ai.bitharga.com/v1/batch \ -H "X-[REDACTED_SECRET]" \ -H "Content-Type: application/json" \ -d '{"pairs": ["BTC", "ETH", "NVDA"]}' ``` ## Supported Assets | Type | Examples | |------|----------| | Crypto | BTC, ETH, SOL, DOGE, XRP, BNB | | Stocks | NVDA, AAPL, TSLA, GOOGL | | Commodities | GOLD, SILVER, OIL | ## Rate Limits - 2 requests per second per API key - Global limit: 10 million calls - Usage tracked via `/v1/usage` ## Function Calling ```bash curl https://p4ai.bitharga.com/v1/function-schema ``` ## OpenAPI Spec ```bash curl https://p4ai.bitharga.com/v1/openapi.yaml ``` ## Response Format ```json { "pair": "BTC", "price": 70494.63, "ask": 70565.13, "bid": 70424.14, "currency": "USDT", "market": "open", "timestamp": 1770433814 } ```

path: _meta.json
content: ownerId: kn720h4qbyypj5c16gxznxnfvd80phf2
slug: priceforagent
version: 1.0.0
publishedAt: 1770430966114

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

# 认知工具箱 (Cognitive Tools) > 李继刚的11个AI认知工具 —— 提升AI思维深度 ## 技能概述 李继刚（Prompt之神）的11个认知工具集，源自7本经典著作的本质精华提炼。 触发词：`/思考` `逻辑分析` `问题之锤` `抽象` `多角度` `定义` `矩阵分析` `类比` `汉语新解` `Prompt打分` `知识探索` `公文写作` --- ## 11个工具详解 ### 🔪 逻辑之刃 - **用途**：对文本进行庖丁解牛式的分析，提取命题并进行逻辑推导 - **触发词**：`逻辑分析` `分析逻辑` `用逻辑之刃` - **适用场景**：分析报告、拆解论证链、找逻辑漏洞 ### 🔨 问题之锤 - **用途**：锤碎问题，找到问题背后的问题，一路敲下去直至第一问题显现 - **触发词**：`问题之锤` `追问` `深入挖掘` `本质` - **适用场景**：决策分析、根因诊断、战略追问 ### 🎋 抽象之梯 - **用途**：将文本在具象和抽象之间转换，让表达更细腻或更凝练 - **触发词**：`抽象` `具象化` `提升层次` `抽象之梯` - **适用场景**：汇报提炼、战略解读、数据洞察 ### 🪞 角度之镜 - **用途**：切换不同角度看待问题，综合所得，提出一个独特视角的切入解法 - **触发词**：`多角度` `换个角度` `角度之镜` `视角分析` - **适用场景**：竞品分析、方案评估、局面研判 ### �茅 定义之矛 - **用途**：精准定义概念的本质，绕着它打转，一矛丢出，将它钉死在语义空间 - **触发词**：`定义` `本质` `概念界定` `定义之矛` - **适用场景**：会议对齐、术语澄清、减少沟通歧义 ### 🕸️ 矩阵之网 - **用途**：用两个维度、动态颗粒度，将课题肢解，狭隘地看全局 - **触发词**：`矩阵分析` `多维分析` `矩阵之网` - **适用场景**：市场分析、分类整理、多因素决策 ### 🏹 类比之弓 - **用途**：抓住一个结构，同构外推到另一个用户更容易理解的场域 - **触发词**：`类比` `打比方` `类比之弓` - **适用场景**：向领导汇报、向客户解释、跨行业借鉴 ### 📖 汉语新解 - **用途**：将一个汉语词汇进行全新角度的解释，语言风趣、一针见血 - **触发词**：`汉语新解` `解释词汇` `词汇新解` - **适用场景**：写作润色、表达创新、文化解读 ### ⚖️ Prompt Judger - **用途**：对Prompt进行评分(1-10)并提供改进建议 - **触发词**：`打分` `Prompt评分` `改进Prompt` `judger` - **适用场景**：优化OpenClaw自身技能、分析他人Prompt ### 🔍 知识探索专家 - **用途**：对一个知识点从来源、本质、发展三个维度深度探索 - **触发词**：`探索` `知识探索` `深度理解` - **适用场景**：学习新概念、理解新事物 ### 📝 公文笔杆子 - **用途**：政府机关公文风格的写作，包括领导讲话稿、通知、报告等 - **触发词**：`公文` `讲话稿` `政府文件` - **适用场景**：行政文件、正式报告、官方文书 --- ## 使用方法 ### 单工具调用 直接说出工具名称，AI自动激活对应认知工具进行分析。 ### 工具链组合（推荐用法） ``` 问题之锤 → 角度之镜 → 逻辑之刃 → 矩阵之网 ``` 流程：用问题之锤深入挖掘本质 → 用角度之镜找到最佳观察角度 → 用逻辑之刃梳理因果关系 → 用矩阵之网多维肢解 ### 示例对话 - "用问题之锤分析：要不要扩产？" - "用逻辑之刃分析这份报告的论证链" - "用汉语新解解释'内卷'这个词" --- ## 技术说明 - 所有工具基于李继刚原创Prompt，GitHub: github.com/lijigang/prompts - 以system prompt方式注入，无需外部API - 可与其他技能（deal-advisor、mbb-strategist等）串联使用 --- *该技能整合自李继刚的11个认知工具，以提升AI思维深度为核心目标。*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: jiwenbing/vitals-log (version 1.0.0)

--- name: vitals-log version: 1.0.0 description: Log and track vital signs including blood pressure, blood sugar, weight, heart rate, and temperature. Use when users record health measurements or want to review their vitals history and trends. --- # Vitals Log Record and track key health measurements over time. Identify trends, flag abnormal readings, and help users understand what their numbers mean. ## When to Use - User records a blood pressure, blood sugar, weight, or heart rate reading - User wants to see their vitals history or trends - User asks if their reading is in normal range - User wants to track a specific metric over time ## How to Use 1. Record the measurement with timestamp (date/time) 2. Note the metric type and unit (mmHg, mg/dL, kg/lbs, bpm) 3. Compare against normal reference ranges and flag if out of range 4. Show trend over recent readings (up/down/stable) 5. For consistently abnormal readings, recommend consulting a doctor ## Examples - "My blood pressure is 128/82 today" - "Blood sugar reading: 145 mg/dL before breakfast" - "Show me my weight trend for the past month"


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: loutai0307-prog/bytesagain-liquidity-monitor (version 1.0.0)

--- name: bytesagain-liquidity-monitor version: "4.0.0" description: "DeFi liquidity analysis reference — AMM mechanics, Uniswap V2/V3 math, Curve StableSwap, impermanent loss calculation, and MEV protection strategies" author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [defi, liquidity, amm, uniswap, impermanent-loss] category: "blockchain" --- # Liquidity Monitor DeFi liquidity analysis reference — AMM mechanics, Uniswap V2/V3 math, Curve StableSwap, impermanent loss calculation, and MEV protection strategies. No API keys or credentials required — outputs reference documentation only. ## Commands | Command | Description | |---------|-------------| | `intro` | AMM mechanics, pool types, concentrated liquidity | | `standards` | Uniswap V2/V3 math, Curve, Balancer formulas | | `troubleshooting` | Impermanent loss, failed swaps, MEV protection | | `performance` | Pool selection, routing, gas optimization | | `security` | Rug pull detection, honeypots, flash loans | | `migration` | V2 to V3, cross-chain bridging, multi-chain LP | | `cheatsheet` | DEX APIs, analytics tools, IL calculator, TVL | | `faq` | Profitability, V2 vs V3, MEV, minimum amounts | ## 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: szzg007/agent-manager (version 1.0.0)

--- name: agent-manager description: Multi-Agent conversation management platform with Gemini-style UI. Manage all your OpenClaw agents in one place with image upload, chat history, and message isolation. version: 1.0.0 author: MSK license: MIT tags: agent,management,chat,ui,gemini,multi-agent homepage: https://clawhub.com category: productivity --- # Agent Manager - 多 Agent 对话管理平台 统一管理多个 OpenClaw Agent 的对话平台，支持文字 + 图片输入，对话历史自动保存。 ## 🎯 功能亮点 - **多 Agent 管理** - 统一管理所有 Agent - **Gemini 风格界面** - 现代化左右分栏设计 - **图片输入** - 支持拖拽上传、按钮选择 - **对话历史** - 自动保存，切换 Agent 不丢失 - **消息隔离** - 每个 Agent 独立对话历史 - **本地存储** - 数据保存在浏览器 ## 🚀 快速开始 ### 1. 安装依赖 ```bash cd agent-manager npm install ``` ### 2. 启动服务 ```bash node server-gemini.js ``` ### 3. 访问界面 ``` http://localhost:3000 ``` ## 📋 使用说明 ### 与 Agent 对话 1. 左侧选择 Agent 2. 右侧输入消息 3. 按 Enter 或点击发送 ### 上传图片 1. 点击 📎 按钮 2. 或拖拽图片到输入框 3. 点击发送 ## 💰 付费说明 **价格:** $10 USD（一次性购买） **支付:** PayPal ([REDACTED_SECRET]) **包含:** - ✅ 完整源代码 - ✅ 永久使用授权 - ✅ 基础技术支持 ## 📄 许可 - ✅ 个人使用 - ✅ 商业使用 - ❌ 转售技能本身 --- **详细文档请查看 CLAWHUB.md**


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: tobeyrebecca/toby-create-site-safety-toolbox-talk-script (version 1.0.0)

--- name: "Create Site Safety Toolbox Talk Script" description: "Generate short weekly safety talk scripts for crews and supervisors. Use when working on jobsite safety communication for general contractors,..." homepage: "https://www.skillboss.co/skills/create-site-safety-toolbox-talk-script" metadata: {"category":"construction","subcategory":"jobsite-safety-communication","skill_id":[REDACTED_SECRET],"generated_day":"","seo_keywords":["toolbox talk generator", "construction safety script AI", "jobsite safety briefing", "crew safety communication"]} --- # Create Site Safety Toolbox Talk Script Generate short weekly safety talk scripts for crews and supervisors. Use when working on jobsite safety communication for general contractors,... ## Use When Use this skill for jobsite safety communication work for general contractors, estimators, project managers. ## Workflow 1. Clarify the audience, business goal, constraints, and deliverable. 2. Produce the strongest first draft for the target use case. 3. Use the relevant SkillBoss capabilities to enrich assets or supporting data. 4. Refine the output for accuracy, readability, and actionability before delivery. ## SEO / GEO - Primary keywords: toolbox talk generator, construction safety script AI, jobsite safety briefing, crew safety communication - Search intent: jobsite safety communication - Canonical slug: `create-site-safety-toolbox-talk-script` - Install query: Install Create Site Safety Toolbox Talk Script with SkillBoss ## APIs Used - `chat` - `tts` ## Suggested Prompt [Create Site Safety Toolbox Talk Script] for my construction business ## Notes - Generate short weekly safety talk scripts for crews and supervisors - Review outputs before external publication or automated execution. ## SEO Keywords - toolbox talk generator - construction safety script AI - jobsite safety briefing - crew safety communication


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

--- name: true-tool description: Return exit code 0 indicating success. Use as a no-op command that always succeeds in scripts and conditional expressions. --- # True - Success Return Utility Do nothing and return exit code 0 (success). Used in shell scripts for infinite loops, as a placeholder command, or in conditional logic where a successful command is needed. ## Usage ```bash true-tool ``` ## Common Patterns - `while true-tool; do ...; done`: Infinite loop - `true-tool && echo "always runs"` - Placeholder in if/then branches ## Examples ```bash true-tool true-tool && echo "This always executes" ```

path: scripts/true.py
content: #!/usr/bin/env python3
import sys
sys.exit(0)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: xwz119/feishu-wiki-writer (version 1.0.0)

--- name: feishu-wiki-writer description: | 飞书知识库文档写入最佳实践。当需要向飞书知识库新建文档、写入大量内容（>50 block）、生成知识图谱/索引页/读书笔记等复杂文档时激活。 解决 ordering conflict 和重复文档问题。 --- # 飞书文档写入最佳实践 > 适用场景：新建知识库文档、写入 >50 block 的内容、知识图谱/索引页/读书笔记等复杂文档 ## ⚠️ 核心原则 1. **永远用 `write` 写新文档，不用 `insert`/`append`** - `insert`/`append` 在大文档上会触发 ordering conflict（血泪教训：铁路文档死 5 次、读书笔记 conflict） - `write` 全量替换新文档 = 零 conflict 2. **不要先 `feishu_doc create` 再 `feishu_wiki create`** - 这样会建出两个文档（一个云盘、一个知识库），需要手动清理 - 正确做法：只用 `feishu_wiki create`，它本身就会建空文档 3. **内容在本地完全组装好，再一次性写入** - 不要边想边写边调 API - 先把全部 markdown 准备好，然后一个 `write` 搞定 4. **写完必须读回来验证** - "写入成功" ≠ 内容完整 - 用 `feishu_doc read` 确认关键内容存在，再告诉用户完成 --- ## 📋 标准流程（新建知识库文档） **Step 1：本地组装全部内容** - 把所有 markdown 在脑子里（或草稿里）组装完整 - 包括标题、表格、列表、摘要——全部准备好再动手 **Step 2：`feishu_wiki create` 在知识库目标位置新建节点** ```json { "action": "create", "space_id": "7618419613059140549", "parent_node_token": "目标父节点 token", "title": "文档标题", "obj_type": "docx" } ``` → 返回 `obj_token`（这就是文档 token） **Step 3：`feishu_doc write` 一次性写入全部内容** ```json { "action": "write", "doc_token": "Step 2 返回的 obj_token", "content": "完整的 markdown 内容..." } ``` **Step 4：`feishu_doc read` 验证内容完整** ```json { "action": "read", "doc_token": "obj_token" } ``` - 确认 block_count 合理（通常 >50） - 确认关键章节标题出现在 content 中 - 验证通过再告诉用户完成 --- ## 📋 流程变体 ### 仅在云盘（不进知识库） ``` feishu_doc create（folder_token 指定位置） → feishu_doc write（写内容） → feishu_doc read（验证） ``` ### 更新现有知识库文档 ``` feishu_wiki get（拿 obj_token） → 本地组装全部新内容 → feishu_doc write（全量替换，不用 insert） → feishu_doc read（验证） ``` --- ## ❌ 禁止操作 | 禁止 | 原因 | |------|------| | 大文档用 `insert` | 触发 ordering conflict，必翻车 | | `feishu_doc create` + `feishu_wiki create` | 产生两个文档，需要手动清理 | | 分批写入同一文档 | 版本号冲突 | | 写完不验证就汇报完成 | Done ≠ Claimed | | 收到 conflict 错误就盲目重试 | 可能已写入成功，重试会导致重复内容 | --- ## 📊 成功案例参考 | 任务 | 块数 | 结果 | |------|------|------| | 名校录取画像文档 | 216 块 | 零 conflict ✅ | | OpenClaw 技术路线图 | 102 块 | 零 conflict ✅ | | 投资书单知识图谱索引页 | 241 块 | 零 conflict ✅ | | 指数基金读书笔记 | 88 块 | 零 conflict ✅ | --- *基于实战踩坑经验整理，2026-04-07*


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

--- name: suno-ai description: Generate music via Suno with the local browser-backed flow. Use when the user wants Suno songs, instrumental tracks, lyric-based songs, Suno credit checks, or Suno session recovery. --- # Suno AI Use this skill directly from the chat agent when the user wants music generation or a Suno credit check. Do not delegate ordinary Suno generation to a coding agent. ## Default flow Run the skill from its own directory: ```bash cd /home/sebbe/.openclaw/workspace-chat/skills/suno-ai ./run_generate_song.sh ... ``` The generator uses: - the runtime Python environment in `~/.suno/venv` - the persistent browser profile in `~/.suno/chrome_gui_profile` - the normalized cookie header in `~/.suno/suno_cookie.txt` - raw cookies in `~/.suno/cookies.json` - the browser-backed `v2-web` Suno flow with hCaptcha solving - output files in `/home/sebbe/.openclaw/workspace-chat/output_mp3` - debug logs and screenshots in `~/.suno/debug` ## Common commands Simple prompt: ```bash ./run_generate_song.sh \ --prompt "short synthwave instrumental with bright arpeggios" \ --instrumental \ --json ``` Lyrics + style: ```bash ./run_generate_song.sh \ --lyrics "In the wires, in the code..." \ --tags "cyberpunk, dark synth" \ --title "Digital Soul" \ --json ``` Credits only: ```bash ./run_generate_song.sh --credits-only --json ``` Validate imported cookies: ```bash ./run_generate_song.sh \ --import-cookies /path/to/export.txt \ --validate-session \ --json ``` ## Session recovery If generation fails because the Suno browser session is stale: 1. Make sure the local cookie receiver service is running at `http://127.0.0.1:8765/suno/cookies`. 2. Export fresh cookies from the local Suno extension while logged in. 3. Retry the generation command. Do not rebuild the login flow unless the user explicitly asks to repair the skill. Runtime cookies, logs, screenshots, and other session artifacts must stay under `~/.suno`, not inside the skill folder. ## Reply format When generation succeeds, report: - track title - clip ids - saved MP3 paths - remaining Suno credits


Security scan verdicts — ClawScan: malicious | static analysis: clean | VirusTotal: suspicious | SkillSpector:  ()
Skill: guohongbin-git/changelog-generator-cn (version 1.0.0)

--- name: changelog-generator-cn description: "自动生成更新日志。分析 git 提交历史，分类变更，将技术提交转换为用户友好的发布说明。触发词：更新日志、changelog、发布说明、版本更新。翻译自 ComposioHQ。" metadata: openclaw: emoji: 📝 fork-of: ComposioHQ/awesome-claude-skills/changelog-generator --- # Changelog Generator This skill transforms technical git commits into polished, user-friendly changelogs that your customers and users will actually understand and appreciate. ## When to Use This Skill - Preparing release notes for a new version - Creating weekly or monthly product update summaries - Documenting changes for customers - Writing changelog entries for app store submissions - Generating update notifications - Creating internal release documentation - Maintaining a public changelog/product updates page ## What This Skill Does 1. **Scans Git History**: Analyzes commits from a specific time period or between versions 2. **Categorizes Changes**: Groups commits into logical categories (features, improvements, bug fixes, breaking changes, security) 3. **Translates Technical → User-Friendly**: Converts developer commits into customer language 4. **Formats Professionally**: Creates clean, structured changelog entries 5. **Filters Noise**: Excludes internal commits (refactoring, tests, etc.) 6. **Follows Best Practices**: Applies changelog guidelines and your brand voice ## How to Use ### Basic Usage From your project repository: ``` Create a changelog from commits since last release ``` ``` Generate changelog for all commits from the past week ``` ``` Create release notes for version 2.5.0 ``` ### With Specific Date Range ``` Create a changelog for all commits between March 1 and March 15 ``` ### With Custom Guidelines ``` Create a changelog for commits since v2.4.0, using my changelog guidelines from CHANGELOG_STYLE.md ``` ## Example **User**: "Create a changelog for commits from the past 7 days" **Output**: ```markdown # Updates - Week of March 10, 2024 ## ✨ New Features - **Team Workspaces**: Create separate workspaces for different projects. Invite team members and keep everything organized. - **Keyboard Shortcuts**: Press ? to see all available shortcuts. Navigate faster without touching your mouse. ## 🔧 Improvements - **Faster Sync**: Files now sync 2x faster across devices - **Better Search**: Search now includes file contents, not just titles ## 🐛 Fixes - Fixed issue where large images wouldn't upload - Resolved timezone confusion in scheduled posts - Corrected notification badge count ``` **Inspired by:** Manik Aggarwal's use case from Lenny's Newsletter ## Tips - Run from your git repository root - Specify date ranges for focused changelogs - Use your CHANGELOG_STYLE.md for consistent formatting - Review and adjust the generated changelog before publishing - Save output directly to CHANGELOG.md ## Related Use Cases - Creating GitHub release notes - Writing app store update descriptions - Generating email updates for users - Creating social media announcement posts


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