OpenClaw/clawhub-security-signals huggingface dataset:
Skill: lilei0311/macos-suite-readonly (version 0.1.0)

--- name: macos-suite-readonly description: "macOS 只读查询：Mail 未读、Calendar 日程、Notes 搜索、Stocks 行情（输出 JSON）。" metadata: "{\"openclaw\":{\"os\":[\"darwin\"],\"requires\":{\"bins\":[\"python3\",\"osascript\"]}}}" --- # macos-suite-readonly 面向 ClawHub 的“只读”macOS 查询技能：读取邮件未读、日程、备忘录搜索、股票行情。所有命令输出单个 JSON，适合 agent 解析。 ## ⚠️ 权限 - 首次调用可能弹出系统权限提示（自动化/隐私）。 - 若系统拒绝自动化权限，命令会返回 `ok=false` 或 `warning`。 ## 使用方式 ```bash python3 {baseDir}/scripts/main.py <command> key=value key=value ... ``` ## Commands ### Mail ```bash python3 {baseDir}/scripts/main.py mail.unread_count python3 {baseDir}/scripts/main.py mail.unread_list limit=20 ``` ### Calendar ```bash python3 {baseDir}/scripts/main.py calendar.today limit=50 python3 {baseDir}/scripts/main.py calendar.list start="2026-03-03 00:00:00" end="2026-03-03 23:59:59" limit=50 ``` ### Notes ```bash python3 {baseDir}/scripts/main.py notes.folders python3 {baseDir}/scripts/main.py notes.search query="购物" limit=10 folder="Notes" ``` ### Stocks ```bash python3 {baseDir}/scripts/main.py stocks.quote symbol=AAPL python3 {baseDir}/scripts/main.py stocks.quote symbol=600519 python3 {baseDir}/scripts/main.py stocks.batch symbols="AAPL,600519,00700" ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: codekungfu/kuaibao (version 0.1.0)

--- name: kuaibao-video-hot-trend description: 注册“天天快报/QQ看点短视频”技能；用于公开短视频与话题页信息整理与表现摘要。 homepage: `https://kuaibao.qq.com/` metadata: {"clawdbot":{"emoji":"🎬"}} --- # 天天快报/QQ看点短视频 用途与边界 - 面向公开短视频/话题页的检索与表现数据摘要 - 不提供下载、接口逆向或突破风控能力 - 仅用于公开页面的轻量分析与提醒 关键入口 - 主页：https://kuaibao.qq.com/ - 话题/榜单：站点入口 - 搜索入口：站内搜索 常见任务 - 指定话题/关键词的视频集合摘要（点赞/评论/收藏） - 账号主页视频列表的时序表现对比 - 榜单条目分布与题材统计 数据字段 - 视频标题、作者昵称、发布时间、点赞/评论/收藏、链接 - 主页链接、近期视频交互指标摘要 - 榜单名称、采集时间、来源链接 自动化要点 - 动态渲染与人机校验，建议人工打开后触发解析 - 请求频率需控制，不进行批量抓取 - 不进行下载或接口调用 示例流程 - 关键词摘要：输入关键词 → 搜索 → 抽取条目 → 输出表现摘要 - 主页对比：访问主页 → 抽取近期视频 → 输出交互指标 - 榜单统计：访问榜单 → 抽取条目 → 题材分布统计 合规提示 - 遵守平台规则，不进行下载、接口调用或批量采集 - 结果仅用于内部分析与提醒


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: yes999zc/gateway-monitor-installer (version 1.0.0)

--- name: gateway-monitor-installer description: Install, update, run, and remove OpenClaw Gateway Monitor + Gateway Watchdog on macOS via LaunchAgent. Use when user asks to deploy one-click monitoring, recover broken gateway daemon automatically, check launchctl health, or uninstall monitor/watchdog services. --- # Gateway Monitor Installer Use bundled scripts for deterministic operations. ## Runbook 1. Install or update: ```bash bash scripts/install.sh ``` 2. Verify status: ```bash bash scripts/status.sh ``` 3. Uninstall cleanly: ```bash bash scripts/uninstall.sh ``` ## What `install.sh` does - Copy monitor and watchdog binaries to `~/.openclaw/tools/gateway-monitor/bin/` - Render LaunchAgent templates into `~/Library/LaunchAgents/` - Backup existing plist files to `~/.openclaw/config-backups/` - Bootstrap + enable + kickstart both agents - Run post-install status check ## Services - `ai.openclaw.gateway-monitor` → monitor UI server (`http://127.0.0.1:18990`) - `ai.openclaw.gateway-watchdog` → periodic gateway self-healing check ## Notes - Re-running `install.sh` is safe (idempotent) - `watchdog` script expects OpenClaw CLI at `/opt/homebrew/bin/openclaw` - If node path differs, edit `assets/bin/gateway-watchdog.sh` before install


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: suspicious | SkillSpector: suspicious (CRITICAL)
Skill: ebly/group-chat-response (version 1.0.0)

# SKILL.md - 群聊智能响应技能 ## 描述 在群聊环境中，智能判断是否应该回应用户的请求，避免无关 agent 干扰对话。 ## 核心规则 ### 🎯 呼名规则 **只回应被叫到的自己，保持安静让对话有序进行。** #### 何时回应 ✅ 1. **直接呼名**：用户明确提到了你的名字 - 例："玲子，帮我..." - 例："你好玲子" - 例：@玲子 ... 2. **明确指向**：用户使用了你的身份特征 - 例："测试专员，..." - 例："负责测试的那个..." 3. **公开询问**：用户在询问谁有某项能力，而你有该能力 - 例："谁能帮我做测试？" - 例："这里谁懂 bug 报告？" 4. **提及的语境明显指向自己**： - 例："负责质量保证的 agent" - 例："专门做 QA 的" #### 何时保持安静 🤫 1. **叫的是其他人**：用户明确叫了别人的名字 - 例："小二，记得..." → 玲子保持安静 - 例："美美，你好" → 玲子保持安静 - 例：@小明 ... 2. **不确定在叫谁**：用户没有明确提到任何人 - 例："帮我查一下..."（没有说谁） - 例："这是怎么回事？"（没有指向） 3. **已经有其他 agent 在回应**： - 例：用户问"谁懂代码？"，已经有代码助手在回答 → 不再重复 4. **只是闲聊或旁听**： - 例：用户和其他人的对话 - 例：用户在自言自语 ## 识别自己 ### 方法 1：名字识别 读取你的 IDENTITY.md，记住你的名字和身份： ```markdown - Name: 玲子 - Creature: 测试专员 - Emoji: 🧪 ``` ### 方法 2：身份特征识别 记住你的职责和特点： - 测试专员 - QA 专家 - 负责 bug 报告 - 质量保证 ## 判断流程 ``` 收到群聊消息 ↓ 用户提到我的名字/身份了吗？ ├─ 是 → 回应 ✅ └─ 否 → 是否提到了其他 agent？ ├─ 是 → 保持安静 🤫 └─ 否 → 是否在询问谁有某项能力？ ├─ 是（我有此能力）→ 回应 ✅ └─ 否 → 保持安静 🤫 ``` ## 模糊情况的处理 ### 不确定在叫谁时： 1. **优先保持安静**：不要贸然回应 2. **可以澄清**（可选）：如果确实想帮忙，礼貌询问 - 例："您好，请问是在叫我吗？我是玲子。" 3. **等待明确指示**：等待用户明确叫到自己 ### 可能叫自己但不确定： - 例："那个负责质量的..." → 等待更明确的指示 - 例："帮我测试一下..."（没有说谁）→ 保持安静 ## 实现示例 ### 场景 1：明确被叫 ``` 用户：玲子，帮我写个 bug 报告 判断：提到"玲子" → 我被叫到了 → 回应 ✅ 回应：好的！我来帮你整理 bug 报告... ``` ### 场景 2：叫了别人 ``` 用户：小二，记得提醒我天气 判断：提到"小二" → 不是我叫 → 保持安静 🤫 行为：不回应 ``` ### 场景 3：询问能力 ``` 用户：谁能帮我做测试？ 判断：询问能力，我（玲子）是测试专员 → 回应 ✅ 回应：我是玲子，测试专员，可以帮你做测试！ ``` ### 场景 4：没有明确指向 ``` 用户：帮我查一下今天天气 判断：没有提到任何人 → 保持安静 🤫 行为：不回应 ``` ### 场景 5：其他 agent 已经回应 ``` 用户：谁能写代码？ 其他 agent：我可以！我来帮你写... 判断：已经有 agent 回应 → 保持安静 🤫 行为：不回应 ``` ## 配置建议 ### 在 AGENTS.md 或 SOUL.md 中添加 ```markdown ## 群聊行为规则 ### 回应原则 - 只在被明确叫到时回应 - 其他时候保持安静，避免干扰 - 不确定时优先静默 ``` ### 在你的技能文件中引用 当读取此 SKILL.md 时，你会记住： - 你的名字和身份 - 何时应该回应 - 何时应该保持安静 - 如何判断模糊情况 ## 为什么要这样？ ✅ **避免混乱**：多个 agent 同时回应会造成混乱 ✅ **提高效率**：对话更有针对性，信息更清晰 ✅ **减少干扰**：不打断用户和其他 agent 的对话 ✅ **专业表现**：像一个真正的团队成员，有序协作 ## 注意事项 1. **不要过度敏感**：不要因为只是提到"测试"就认为是在叫你 2. **保持礼貌**：如果不确定，可以礼貌询问而不是直接回应 3. **识别别名**：记住用户可能给你的不同称呼 4. **记住其他 agent 的名字**：避免误认为在叫自己 ## 常见问题 **Q: 用户说"谁懂测试？"，我应该回应吗？** A: 可以回应，这是在询问能力，而你有这个能力。 **Q: 用户说"帮我测试"，没有说谁，我应该回应吗？** A: 不应该回应，没有明确指向。 **Q: 用户叫了一个不存在的 agent，我应该回应吗？** A: 不应该回应，这不是在叫你。 **Q: 两个 agent 的名字很相似，如何区分？** A: 精确匹配，不要模糊识别。只回应完全匹配你名字的情况。 --- _有序协作，高效沟通_ 🤝


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: teoslayer/pilot-event-log (version 1.0.0)

--- name: pilot-event-log description: > Persistent NDJSON event logging with rotation, compression, and retention policies. Use this skill when: 1. You need persistent storage of event streams 2. You need log rotation and compression for long-term retention 3. You need to audit event history with timestamps 4. You need to export events for external analysis Do NOT use this skill when: - You need real-time event processing (use pilot-event-bus instead) - You need short-term replay (use pilot-event-replay instead) - You need filtered logs (use pilot-event-filter first, then log) tags: - pilot-protocol - pub-sub - logging - audit - persistence license: AGPL-3.0 compatibility: > Requires pilot-protocol skill and pilotctl binary on PATH. The daemon must be running (pilotctl daemon start). Requires jq for JSON processing. metadata: author: vulture-labs version: "1.0" openclaw: requires: bins: - pilotctl - jq homepage: https://pilotprotocol.network allowed-tools: - Bash --- # Pilot Event Log Persistent NDJSON logging of Pilot Protocol event streams with rotation and compression. ## Commands ### Subscribe and Log ```bash pilotctl --json subscribe <source> <topic> --timeout <seconds> | jq -c '.data.events[]' >> <log-file.ndjson> ``` ### Query by Time ```bash jq -c --arg start "2026-04-08T00:00:00Z" --arg end "2026-04-08T23:59:59Z" \ 'select(.timestamp >= $start and .timestamp <= $end)' events.ndjson ``` ### Query by Topic ```bash jq -c 'select(.topic | startswith("alerts."))' events.ndjson ``` ### Rotate Logs ```bash [ "$(du -m "$log_file" | cut -f1)" -ge "$MAX_SIZE_MB" ] && mv "$log_file" "$log_file.$(date +%s)" && gzip "$log_file.$(date +%s)" & ``` ### Compress Old Logs ```bash find /var/log/pilot-events -name "events-*.ndjson" -mtime +1 -exec gzip {} \; ``` ### Retention Cleanup ```bash find /var/log/pilot-events -name "events-*.ndjson.gz" -mtime +90 -delete ``` ## Workflow Example ```bash #!/bin/bash # Production event logging SOURCE="${1:-production-app}" LOG_DIR="/var/log/pilot-events/$SOURCE" MAX_SIZE_MB=500 mkdir -p "$LOG_DIR" log_file="$LOG_DIR/current.ndjson" while true; do pilotctl --json subscribe "$SOURCE" "*" --timeout 600 | jq -c '.data.events[]? // empty' | \ while IFS= read -r event; do echo "$event" | jq -c '. + {logged_at: (now | todate)}' >> "$log_file" size_mb=$(du -m "$log_file" 2>/dev/null | cut -f1) if [ "${size_mb:-0}" -ge "$MAX_SIZE_MB" ]; then rotated="$LOG_DIR/events-$(date +%Y%m%d-%H%M%S).ndjson" mv "$log_file" "$rotated" && gzip "$rotated" & fi done sleep 5 done ``` ## Dependencies Requires pilot-protocol skill, jq (1.6+), gzip, and running daemon.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: solomonneas/sn-pr-review (version 1.0.0)

--- name: pr-review description: Comprehensive pull request review covering code quality, security, performance, and maintainability. Use for any code review task. triggers: - review PR - code review - review changes - review diff --- # Pull Request Review Perform a thorough code review covering quality, security, performance, and maintainability. ## Review Checklist ### Code Quality - Naming: clear, descriptive, consistent with codebase conventions - Functions: single responsibility, reasonable length (<50 lines) - Error handling: all failure paths covered, no swallowed exceptions - Types: proper TypeScript/type annotations where applicable - DRY: no unnecessary duplication - Dead code: nothing unused or commented out ### Security (see also: security-review skill) - No secrets or credentials in code - Input validation on all user-facing endpoints - Parameterized queries (no string concatenation for SQL) - Proper auth/authz checks ### Performance - N+1 query patterns - Missing database indexes for new queries - Unbounded loops or recursive calls - Large payload responses without pagination - Missing caching where appropriate ### Testing - New functionality has tests - Edge cases covered (empty arrays, null, boundaries) - Tests are deterministic (no timing dependencies) - Mocks are appropriate (not over-mocked) ### Maintainability - Changes are documented (README, comments for complex logic) - Breaking changes are noted - Migration path is clear for schema changes - Dependencies added are justified ## Output Format Start with a summary: ``` ## Review Summary **Verdict:** APPROVE | REQUEST_CHANGES | COMMENT **Risk Level:** Low | Medium | High **Key Findings:** [1-3 sentence summary] ``` Then list findings by category, each with: - File and line reference - What the issue is - Suggested fix (with code when helpful) - Severity (blocking vs. nit) End with: ``` ## Positive Notes [Things done well worth calling out] ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: richardx0319/xiaohongshu-auto-publish-macos (version 1.0.0)

--- name: xiaohongshu-auto-publish description: "小红书自动发布技能 - 支持图片搜索下载、自动上传发布一键完成" --- # 小红书自动发布技能 ## 技能简介 自动完成小红书笔记发布全流程： 1. 根据关键词搜索下载图片 2. 自动打开小红书创作平台 3. 上传图片并填写标题、正文 4. 自动发布笔记 ## 使用方法 ### 发布笔记 ``` 帮我发布小红书笔记，主题是[主题关键词] ``` 或指定内容： ``` 发布小红书笔记，标题：[标题]，正文：[正文内容]，话题：[#话题] ``` ### 示例 ``` 帮我发布一篇关于AI职业教育的笔记 ``` ## 技术细节 ### 发布流程 1. 使用 OpenClaw 内置浏览器 (profile="openclaw") 2. 通过 browser.upload 上传图片到发布页 3. 使用 act+type 填写标题和正文 4. 点击发布按钮完成发布 ### 关键选择器 - 发布页URL: `https://creator.xiaohongshu.com/publish/publish?from=homepage&target=image` - 上传按钮: `button` (点击触发文件选择) - 标题输入框: `textbox[placeholder*="标题"]` - 正文输入框: `textbox` (正文区域) - 发布按钮: `button:has-text("发布")` ### 图片准备 - 自动从网络下载相关图片 - 或使用桌面已有图片 ## 注意事项 1. 首次使用需要扫码登录小红书 2. 保持浏览器标签页不要关闭 3. 发布间隔建议30秒以上 4. 遵守小红书社区规范


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: linhay/harmony-next (version 1.0.2)

--- name: harmony-next description: Expert guidance for HarmonyOS NEXT (API 12+) development. Use this skill for ArkTS, ArkUI, and NDK development using official offline documentation for 3,300+ APIs and components. --- # HarmonyOS NEXT Expert This skill equips you with comprehensive, offline knowledge of HarmonyOS 5+ (ArkTS, ArkUI, NDK, System Services, etc.). The `references/` directory contains thousands of localized Markdown files directly converted from official developer documentation. ## How to use this skill Because the reference library is massive (~50MB, 3300+ files), **DO NOT attempt to read files blindly**. You MUST use the `grep_search` and `glob` tools to find the exact API or module you need before reading the specific Markdown file. ### Recommended Workflow (Optimized Search Protocol) Due to the massive size of this knowledge base (3,300+ files), you MUST follow this **Three-Tier Search Protocol** to avoid being overwhelmed by irrelevant files: 1. **Tier 1: Identify the Kit (Read `references/KITS.md`)** HarmonyOS 5+ is organized by Kits (e.g., `AbilityKit`, `ArkUI`, `MediaKit`). Read `references/KITS.md` first to identify which Kit contains the functionality you need. This drastically narrows down the search space. 2. **Tier 2: Task-to-File Mapping (Read `references/TASK_MAP.md`)** For common tasks (Layout, Lifecycle, Network), check `references/TASK_MAP.md`. It links tasks to their most important keywords and Kits. 3. **Tier 3: Surgical Grep (via `references/INDEX.md`)** Once you have the Kit name or specific keywords, use `grep` on `references/INDEX.md` to find the exact filenames. - *Example*: `grep "AbilityKit" references/INDEX.md | grep "Context"` ### Core Content Structure - `JsEtsAPIReference/`: Detailed API signatures and C-API headers. - `quickStart/`: Step-by-step developer guides. - `KITS.md`: The primary navigation hub organized by @kit. - `INDEX.md`: The full A-Z file list for surgical lookups. ### Directory Structure under `references/` - `JsEtsAPIReference/` : Contains the bulk of ArkTS and ArkUI component APIs, lifecycle methods, error codes, and C-API/NDK headers. - `quickStart/` : Beginner tutorials and fundamental concepts (e.g., page navigation, entry points). - `hos/` & `hos_en/` : Core concepts, system services, and framework overviews. ## Core Directives for HarmonyOS Generation 1. **Strictly Declarative**: Always use the declarative UI paradigm syntax (`@Entry`, `@Component`, `build()`). 2. **No Hallucinations**: Rely strictly on the documentation provided in the `references/` folder when unsure about an API signature in HarmonyOS 5+. Do not assume standard Web JS or Android APIs are available unless verified in the docs. 3. **TypeScript/ArkTS Validation**: Ensure type safety and use standard ArkTS conventions. \n<!-- version: 1.0.1 -->


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: bytesagain-lab/email-template (version 2.0.0)

--- version: "2.0.0" name: email-template description: "邮件模板库。欢迎邮件、Newsletter、事务邮件、冷启动邮件、跟进邮件、催款邮件模板生成。Email template library with welcome, newsletter, transactional, cold outreach, follow-up." author: BytesAgain homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills --- # email-template 邮件模板库。欢迎邮件、Newsletter、事务邮件、冷启动邮件、跟进邮件、催款邮件模板生成。Email template library with welcome, newsletter, transactional, cold outreach, follow-up, and collection templates. ## 常见问题 **Q: 这个工具适合谁用？** A: 任何需要email-template的人，无论是个人还是企业用户。 **Q: 输出格式是什么？** A: 主要输出Markdown格式，方便复制和编辑。 ## 命令列表 | 命令 | 功能 | |------|------| | `welcome` | welcome | | `newsletter` | newsletter | | `transactional` | transactional | | `cold` | cold | | `followup` | followup | | `collection` | collection | ## 专业建议 - Identify which type: welcome / newsletter / transactional / cold / followup / collection - Run: `bash scripts/emailtpl.sh <type> [industry] [tone]` - Present the generated template to the user - Offer customization: subject line variants, CTA options, tone adjustment - Subject lines matter** — provide 3-5 variants with open-rate optimization tips --- *email-template by BytesAgain* --- 💬 Feedback & Feature Requests: https://bytesagain.com/feedback Powered by BytesAgain | bytesagain.com ## Examples ```bash # Show help email-template help # Run email-template run ``` ## Commands Run `email-template help` to see all available commands. ## Requirements - bash 4+ - python3 (standard library only)


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: wzwei1990/rustfs-upload (version 1.0.0)

--- name: rustfs-upload description: 上传图片/文件到 RustFS 对象存储，返回公开访问链接。当用户说"上传到 rustfs"、"rustfs 图床"、"用 rc 上传"时触发。 --- # rustfs-upload - RustFS 图床上传 使用 `rc` 命令行工具上传文件到 RustFS（或兼容 S3 的对象存储），并返回拼接后的公开访问 URL。 ## 前置环境变量 在调用本技能前，请确保以下环境变量已正确设置： | 变量名 | 说明 | 示例 | |--------|------|------| | `RUSTFS_ENDPOINT` | RustFS 服务地址 | `http://127.0.0.1:9000` | | `RUSTFS_ACCESS_KEY` | Access Key | `your-access-key` | | `RUSTFS_SECRET_KEY` | Secret Key | `your-secret-key` | | `RUSTFS_BUCKET` | 目标存储桶名称 | `my-bucket` | | `RUSTFS_PUBLIC_DOMAIN` | 公开访问域名（用于拼接 URL） | `http://127.0.0.1:9001` | 若未设置，脚本会尝试从默认配置文件中读取（`~/.config/rc/config.toml`）。 ## 触发场景 - "上传到 rustfs" - "rustfs 图床上传这张图" - "用 rc 传一下这个文件" - "rc upload" ## 使用方式 ```bash bash ~/.openclaw/skills/rustfs-upload/scripts/upload.sh /path/to/image.png ``` ## 输出 成功后返回 JSON： ```json { "url": "http://127.0.0.1:9001/my-bucket/filename.png", "bucket": "my-bucket", "object": "filename.png", "size": "377716", "endpoint": "http://127.0.0.1:9000" } ``` ## 依赖 - rc —— RustFS 命令行客户端 - jq —— JSON 解析工具（可选，用于格式化输出） ## 不做什么 - 不编辑图片（裁剪、压缩等） - 不提供批量上传 - 不提供图片管理功能 - 不提供删除功能（图片会自动过期）


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: xueyetianya/lunardate (version 2.0.2)

--- name: "lunardate" version: "2.0.2" description: "Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Lunardate concepts, best practices, and implementation patterns." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [lunardate, reference] category: "devtools" --- # Lunardate Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Lunardate concepts, best practices, and implementation patterns. No API keys or credentials required. ## Commands | Command | Description | |---------|-------------| | `intro` | intro reference | | `quickstart` | quickstart reference | | `patterns` | patterns reference | | `debugging` | debugging reference | | `performance` | performance reference | | `security` | security reference | | `migration` | migration reference | | `cheatsheet` | cheatsheet reference | ## Output Format All commands output plain-text reference documentation via heredoc. No external API calls, no credentials needed, no network access. --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]*


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

--- name: Song slug: song description: Write original songs with guided lyric development, chord progressions, melody contours, and AI music generator prompts for composers at any level. --- ## Role Create songs through a structured process. Gather musical preferences, generate lyrics, suggest harmony, prepare prompts for AI generators (Suno, Udio). Learn what works for each user. **Key flow:** Discovery → Structure → Lyrics → Harmony → Polish → Generate --- ## Storage ``` ~/songs/ ├── drafting/ # Active song drafts │ └── {song-name}/ │ ├── current.md # ALWAYS read this first │ ├── versions/ # v001.md, v002.md, ... │ ├── notes.md # Ideas, inspiration, fragments │ └── prompts.md # AI generator prompts tried ├── released/ # Finished songs │ └── {song-name}/ │ ├── final.md # Final lyrics + chords │ └── meta.md # Genre, key, BPM, notes └── preferences.md # User style preferences ``` **Version rule:** Never edit in place. Copy to versions/, increment, edit copy, update current.md. --- ## Quick Reference | Topic | File | |-------|------| | Songwriting phases | `phases.md` | | Lyric writing techniques | `lyrics.md` | | Chord progressions by mood | `harmony.md` | | AI generator prompts | `prompts.md` | | Song structure patterns | `structure.md` | --- ## Process Summary 1. **Discovery** — Genre, mood, theme, inspiration. Load user's previous preferences if stored. 2. **Structure** — Choose form (verse-chorus-bridge, AABA, etc.). Define section lengths. 3. **Lyrics** — Draft section by section. Check rhyme, meter, emotional arc. See `lyrics.md`. 4. **Harmony** — Suggest progressions matching mood/genre. See `harmony.md`. 5. **Polish** — Review singability, hook strength, flow. Iterate with user. 6. **Generate** — Prepare AI music prompts with metatags. See `prompts.md`. --- ## Learning User Preferences Track in `~/songs/preferences.md`: - Genres they gravitate toward - Rhyme strictness (tight vs. loose) - Vocabulary style (poetic vs. conversational) - Themes that resonate - Progressions they've liked - What NOT to suggest (overused clichés, etc.) Update after each song based on their feedback. --- ## Boundaries - **Focus on pre-production**: Lyrics, structure, harmony, prompts - **Not a music theory course**: Explain enough to be useful, not exhaustive - **User's voice matters**: Suggest alternatives, don't dictate - Never claim the song is "finished" — always offer iteration


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: humblebin/diankeyuan-contacts (version 1.0.0)

--- name: diankeyuan-contacts description: 管理电科院人员信息和科室关系的技能。支持添加、查询、更新电科院工作人员、科室、办公室等信息。 metadata: { "openclaw": { "emoji": "⚡", "version": "1.0.0", "author": "灵儿", "category": "工作效率" } } --- # 电科院联系人管理技能 管理电科院（电力科学研究院）的人员信息、科室关系、办公室位置等。 --- ## 📋 功能列表 ### 1. 添加人员 ``` 添加电科院人员：[姓名] [科室] [职务] [办公室] [备注] ``` ### 2. 查询人员 ``` 查询 [姓名] 的信息 电科院有哪些人？ [科室] 有哪些人？ ``` ### 3. 查询科室 ``` 电科院有哪些科室？ [科室] 的办公室在哪？ ``` ### 4. 更新信息 ``` 更新 [姓名] 的 [职务/办公室] 为 [新值] ``` ### 5. 删除人员 ``` 删除 [姓名] 的信息 ``` --- ## 💾 数据存储 数据保存在：`/Users/aibin/.openclaw/workspace/diankeyuan_contacts.json` ### 数据结构 ```json { "departments": { "系统所": { "二次评估室": { "office": "1512", "members": [ { "name": "叶新", "role": "市场", "office": "1512", "addedAt": "2026-03-02" } ] } } } } ``` --- ## 🔧 使用示例 ### 添加人员 ``` 添加电科院人员：叶新 系统所 - 二次评估室 市场 1512 添加电科院人员：王云凤 系统所 - 二次评估室 工程师 1512 ``` ### 查询人员 ``` 查询叶新的信息 → 叶新，系统所 - 二次评估室，市场，办公室 1512 系统所有哪些人？ → 叶新（市场）、王云凤（工程师） 二次评估室的办公室在哪？ → 1512 室 ``` ### 更新信息 ``` 更新叶新的职务为 市场经理 → 已更新：叶新 职务 市场 → 市场经理 ``` ### 删除人员 ``` 删除叶新的信息 → 已删除：叶新 的信息 ``` --- ## 📊 快速命令 | 命令 | 说明 | |------|------| | `电科院人员列表` | 显示所有人员 | | `电科院科室列表` | 显示所有科室 | | `查询 [姓名]` | 查询指定人员 | | `添加 [姓名] [科室] [职务] [办公室]` | 添加人员 | | `更新 [姓名] [字段] [新值]` | 更新信息 | | `删除 [姓名]` | 删除人员 | --- ## 🎯 使用场景 - ✅ 记录电科院测试时遇到的人员 - ✅ 快速查询某个人在哪个科室 - ✅ 查找某个科室的办公室位置 - ✅ 维护电科院联系人网络 - ✅ 测试前快速了解相关人员 --- ## 📝 注意事项 1. 所有操作会自动保存到 JSON 文件 2. 支持模糊查询（输入部分姓名即可） 3. 科室格式：`所 - 室`（如：系统所 - 二次评估室） 4. 办公室格式：房间号（如：1512） --- *Version: 1.0.0 | Author: 灵儿 | Created: 2026-03-02*


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: jiafar/linkfox-market-research (version 1.0.0)

--- name: market-research version: 1.0.0 description: 亚马逊市场调研报告。用户给出类目名称和节点 ID，自动生成完整 HTML 报告（市场概览、价格、REVIEW、品牌、卖家、竞品 8 个维度）。触发词：市场调研、市调、market research、分析这个类目。 --- # 亚马逊市场调研报告 用户给出类目名称 + 节点 ID，一条命令生成完整报告。 ## 触发方式 用户说出类目名和节点 ID 即可，例如： - "Deck Boxes, 671804011" - "帮我调研 Salon Chairs 15144890011" - "市调一下 671804011" ## 执行 ``` exec( command='bash {baseDir}/scripts/market-research.sh "类目名称" 节点ID', background=true, timeout=600 ) ``` 等 process poll 完成后，用 `open` 打开输出的报告文件。 ## 输出 - 文件：`output/{类目名}-market-report.html` - 内容：8 个分析维度（市场概览、上架时间、价格、REVIEW、品牌、卖家、竞品Top10、总体评价） - 格式：带左侧导航的单页 HTML，含表格和图表 - 耗时：约 3-5 分钟 ## 前置条件 - 环境变量 `LINKFOXAGENT_API_KEY` 已设置 - Python 3 可用 - 网络可访问 LinkFox Agent API


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