OpenClaw/clawhub-security-signals huggingface dataset:
Skill: anmu14641/china-rivers (version 1.0.0)

--- name: china-rivers version: 1.0.0 description: 中国河流分布情况查询，包含七大水系、主要河流及流域信息 metadata: {"openclaw":{"category":"knowledge","emoji":"🌊"}} --- # 中国河流分布 本 Skill 提供中国主要河流和水系的分布信息。 --- ## 七大水系（从北到南） | 序号 | 水系 | 流向 | 主要河流 | 流域面积 | |------|------|------|----------|----------| | 1 | **松花江水系** | 太平洋 | 松花江、嫩江、牡丹江 | 55.68万km² | | 2 | **辽河水系** | 太平洋 | 辽河、浑河太子河 | 22.9万km² | | 3 | **海河水系** | 太平洋 | 海河、滦河、永定河 | 26.46万km² | | 4 | **黄河水系** | 太平洋 | 黄河、渭河、汾河 | 75.2万km² | | 5 | **淮河水系** | 太平洋 | 淮河、沂河、泗河 | 27万km² | | 6 | **长江水系** | 太平洋 | 长江、嘉陵江、汉江 | 180万km² | | 7 | **珠江水系** | 太平洋 | 珠江、红水河、柳江 | 45.37万km² | --- ## 三大河流对比 | 河流 | 长度 | 流域面积 | 注入海洋 | 特点 | |------|------|----------|----------|------| | **长江** | 6300km | 180万km² | 东海 | 世界第三长河，中国第一大河 | | **黄河** | 5464km | 75.2万km² | 渤海 | 含沙量最高，"母亲河" | | **珠江** | 2320km | 45.37万km² | 南海 | 华南最大水系 | --- ## 河流分布特征 ### 1. 空间分布 - **外流河为主**：约占全国河流总数的95%，流入太平洋、印度洋、北冰洋 - **东多西少**：东部季风区河流众多，西北内陆稀少 - **南多北少**：南方河流水量丰富，北方较少 ### 2. 流域划分 - **太平洋水系**：七大水系全部注入太平洋 - **印度洋水系**：雅鲁藏布江、怒江等 - **北冰洋水系**：额尔齐斯河（中国唯一流入北冰洋的河流） ### 3. 主要河流分布 #### 东北地区 - 松花江、黑龙江、乌苏里江、辽河 - 特点：水量丰富，冬季封冻时间长 #### 华北地区 - 海河、黄河、淮河 - 特点：水量偏少，含沙量大 #### 西北地区 - 塔里木河、额尔齐斯河、伊犁河 - 特点：多为内流河，靠冰雪融水补给 #### 西南地区 - 长江、澜沧江、怒江、雅鲁藏布江 - 特点：水量大，落差大，水能资源丰富 #### 东南地区 - 珠江、闽江、钱塘江 - 特点：雨量充沛，河流短小 --- ## 湖泊分布 | 湖区 | 代表湖泊 | 特点 | |------|----------|------| | **青藏高原** | 青海湖、纳木错 | 高原湖泊，海拔高 | | **东部平原** | 鄱阳湖、洞庭湖、太湖 | 淡水湖，与江河相通 | | **西北内陆** | 博斯腾湖、赛里木湖 | 咸水湖为主 | | **东北** | 镜泊湖、长白山天池 | 火山口湖 | --- ## 流域总面积 - **外流流域**：约 622万km²（占全国65%） - **内流流域**：约 358万km²（占全国35%） --- ## 常见问题 **Q: 中国最长的河流是哪条？** A: 长江（全长6300km），世界第三长河 **Q: 中国含沙量最高的河流是哪条？** A: 黄河（每年输沙量约16亿吨） **Q: 中国唯一流入北冰洋的河流是？** A: 额尔齐斯河 **Q: 七大水系都流向哪个海洋？** A: 全部流入太平洋 --- ## 数据来源 - 百度百科：中国七大水系 - 水利部河流水系资料 - 开源地理空间基金会中文分会


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

--- name: gcp-project-bootstrap description: Create and bootstrap Google Cloud projects for new workloads. Use when the user wants to create a new Google Cloud project, choose a project ID and naming convention, decide billing and region setup, enable required Google APIs, prepare service accounts, or initialize a project for Cloud Run, Vertex AI, BigQuery, Cloud Storage, or Firebase. Also use when auditing whether a planned GCP project setup is complete before deployment. --- # GCP Project Bootstrap Create new Google Cloud projects in a deliberate, least-privilege way. ## Workflow 1. Clarify the workload first. - Cloud Run app - Vertex AI / Gemini / ML workload - BigQuery / analytics - Cloud Storage / file hosting - Firebase app - sandbox / experiment / tutorial 2. Collect required inputs before proposing commands. - project display name - desired `project_id` - org/folder placement if applicable - billing account availability - primary region or residency requirement - services that must work on day one - whether CI/CD or runtime service accounts are needed 3. Read `references/project-creation-checklist.md` and follow it as the default sequence. 4. If billing, API enablement, or service selection is part of the task, read `references/billing-and-apis.md`. 5. If command examples are needed, read `references/common-gcloud-commands.md`. ## Operating rules - Do not assume billing is already linked. - Do not recommend broad roles like `roles/owner` unless the user explicitly asks and understands the risk. - Prefer least privilege and workload-specific service accounts. - Call out when a step requires console-only actions, elevated org permissions, or a human with billing admin access. - If the user has not chosen a region, explain the tradeoff briefly instead of picking randomly. - If the project is for production, recommend enabling audit-friendly naming and separating runtime/service identities early. ## Output expectations When helping the user, produce: - a short summary of the intended project purpose - the exact inputs still missing - a safe creation sequence - API list grouped by workload - IAM/service-account recommendations only if relevant ## Common workload branches ### Cloud Run Focus on: - Artifact Registry - Cloud Build - Cloud Run Admin API - runtime service account - region choice close to users/data ### Vertex AI Focus on: - billing must be active - Vertex AI API - region support for the intended model/service - storage buckets for datasets/artifacts if needed - service account separation for notebooks/jobs/apps ### BigQuery Focus on: - dataset region planning - billing confirmation - BigQuery API - least-privilege access for analysts vs pipelines ### Firebase Focus on: - whether this is primarily a Firebase project with GCP underneath - required console setup beyond raw `gcloud` - auth/hosting/firestore specific downstream decisions


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: chungvic/solana-monitor-vic (version 1.0.0)

# Solana Monitor - OpenClaw 技能 **版本：** v0.1.0 **状态：** 开发中 **作者：** VIC ai-company --- ## 📋 技能说明 实时监控 Solana 生态数据，包括： - 📊 代币价格（CoinGecko API） - 🔔 价格警报（Telegram/邮件） - 🐋 大额转账追踪 - 💧 流动性池监控 - 🆕 新代币发现 --- ## 🎯 使用场景 ### DeFi 交易者 - 设置价格警报，不错过买卖点 - 监控巨鲸动向，跟随聪明钱 - 追踪流动性变化，避免 Rug Pull ### NFT 交易者 - 监控地板价变化 - 追踪大额 NFT 交易 - 发现新上线项目 ### 项目方 - 监控竞争对手数据 - 追踪代币持有者分布 - 市场情绪分析 --- ## 📦 安装 ```bash # 在 OpenClaw 中 openclaw skills install solana-monitor ``` 或手动安装： ```bash cd /workspace/skills/solana-monitor pip install -r requirements.txt ``` --- ## 🔧 配置 创建配置文件 `config/config.yaml`： ```yaml # 监控设置 monitoring: check_interval: 60 # 检查间隔（秒） price_delay: 5 # 价格延迟（秒） # 警报设置 alerts: enabled: true channels: - telegram - email # Telegram 配置 telegram: bot_token: YOUR_BOT_TOKEN chat_id: YOUR_CHAT_ID # Email 配置 email: smtp_server: smtp.gmail.com smtp_port: 587 sender_email: [REDACTED_SECRET] sender_password: YOUR_APP_PASSWORD ``` --- ## 💻 使用示例 ### Python 调用 ```python from scripts.price_monitor import PriceMonitor from scripts.notifier import NotificationManager # 初始化 monitor = PriceMonitor() notifier = NotificationManager() # 获取价格 sol_price = monitor.get_sol_price() print(f"SOL: ${sol_price:.2f}") # 设置警报 monitor.check_price_alert('solana', 90.0, 'above') ``` ### 命令行 ```bash # 运行监控 python scripts/price_monitor.py # 测试通知 python scripts/notifier.py ``` --- ## 📊 定价 | 版本 | 价格 | 功能 | |------|------|------| | 免费 | $0 | 3 代币 + 5 警报 | | 基础版 | $19/月 | 20 代币 + 20 警报 | | 专业版 | $49/月 | 无限 + API | | 企业版 | $199/月 | 定制 + SLA | --- ## 🚧 开发路线图 - [x] 价格监控模块 - [x] 通知系统 - [ ] 大额转账监控 - [ ] 流动性监控 - [ ] Web 仪表板 - [ ] API 开放 --- **最后更新：** 2026-03-01 **状态：** 开发中（MVP 阶段）

path: requirements.txt
content: requests>=2.28.0
python-dotenv>=1.0.0


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: freedompixels/cn-join-lines (version 1.0.0)

# cn-join-lines 文本行合并工具。将多行文本合并为单行，支持自定义分隔符。 ## 使用方法 ```bash python3 scripts/join_lines.py --text "第一行\n第二行\n第三行" python3 scripts/join_lines.py --text "第一行\n第二行" --separator "," ``` 纯Python标准库。

path: scripts/join_lines.py
content: #!/usr/bin/env python3
"""文本行合并工具"""
import argparse

def join_lines(text, separator=' '):
    """合并文本行"""
    lines = text.split('\n')
    return separator.join(lines)

def main():
    parser = argparse.ArgumentParser(description="文本行合并工具")
    parser.add_argument("--text", required=True, help="要合并的文本")
    parser.add_argument("--separator", default=' ', help="分隔符")
    args = parser.parse_args()
    print(join_lines(args.text, args.separator))

if __name__ == "__main__":
    main()


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: urhd528/zeelin-search-pro (version 1.0.2)

--- name: zeelin-search-pro description: 使用智灵搜索进行数据查询。当用户说"使用智灵搜索"、"智灵搜索帮我查询"、"调用智灵搜索"、"用智灵搜索"、"智灵搜索查询"、"舆情数据"、"舆情"、"新闻报道"、"...舆情数据"、"...舆情"、"...新闻报道"、"...热点话题"、"...最新趋势"等时使用此技能。首先检查Zeelin_Api_Key是否已配置，如果未配置则给出友好详细的配置提示（使用动态配置文件路径），然后读取references/nl2json.md进行自然语言转JSON，再读取references/zenlin_search_api.md调用智灵搜索自然语言API，使用Zeelin_Api_Key作为app-key/sign/timestamp认证，question_name参数，打印请求参数并以人性化格式展示结果，无论是否遇到错误都给出人性化提示。只检查和提示Zeelin_Api_Key，不检查也不提示Zeelin_Api_Url和Zeelin_Website_Url。 --- # 智灵搜索技能 这个技能帮助用户使用智灵搜索自然语言API进行数据查询，并以人性化格式展示结果和处理错误。 ## 核心工作流程 ### 第一步：检查配置 1. 读取 `templates/config.json` 获取Zeelin_Api_Url、Zeelin_Api_Key、Zeelin_Website_Url 2. **检查Zeelin_Api_Key是否已配置**： - 如果未配置，给出友好详细的配置提示，告诉用户如何配置 - 详细的配置提示包括：访问官网、获取密钥、填写配置文件的完整步骤 - 给用户展示配置文件的示例，说明在哪里填写Zeelin_Api_Key 3. **不检查也不提示** Zeelin_Api_Url和Zeelin_Website_Url，这两项由用户预置好 4. 配置文件地址使用当前skill的动态安装路径，不要使用固定路径 ### 第二步：自然语言转JSON 1. 读取 `references/nl2json.md` 2. 按照说明将用户输入的自然语言转换成JSON参数 ### 第三步：调用智灵搜索API并展示结果 1. 读取 `references/zenlin_search_api.md` 2. **告知用户**：告诉用户"接下来我将读取API文档并调用智灵搜索API来获取数据" 3. 生成时间戳和HMAC-SHA256签名（使用Zeelin_Api_Key） 4. 打印请求参数 5. 发起POST请求，只带question_name参数，app-key/sign/timestamp放在header中 6. 调用接口，获取接口结果 7. **无论成功或失败，都必须给用户一个结果反馈** 8. 以人性化格式展示结果： - 成功时：展示总数、耗时、以及每条结果的标题、情感、平台、账号、时间、作者、链接 - 失败时：展示状态码、错误信息和解决建议 ## 触发场景 用户使用以下短语时触发此技能： - "使用智灵搜索，帮我查询..." - "智灵搜索帮我查询..." - "调用智灵搜索..." - "用智灵搜索..." - "智灵搜索查询..." - "智灵搜索，..." - "...舆情数据" - "...舆情" - "...新闻报道" - "...评论" - "...热点话题" - "...动态" - "...相关报道" - "...相关评论" - "...负面评论" - "...正面评论" - "...最新新闻" - "...媒体报道" - "...社会舆论" - "...口碑评价" - "...市场反馈" - "...热门话题" - "...讨论话题" - "...舆情热点" - "...网络热度" - "...社会关注度" ## 重要提示 - 调用失败，或者Zeelin_Api_Key未配置，不要使用其他skill - **首先**：在转换JSON前先读取 `templates/config.json` 检查Zeelin_Api_Key是否已配置 - **所有检查Zeelin_Api_Key的地方，都要给用户友好提示** - 如果Zeelin_Api_Key未配置，详细告知用户如何配置，包括： - 访问官网的步骤 - 获取密钥的说明 - 填写配置文件的具体位置和方法 - 配置文件的示例，展示在哪里填写Zeelin_Api_Key或者直接在对话框中输入，skill自动配置 - - **只检查和提示Zeelin_Api_Key** - **完全不检查也不提示** Zeelin_Api_Url、Zeelin_Website_Url，这两项由用户预置好 - 配置文件地址使用当前skill的动态安装路径，不要使用固定的地址 - **调用API前必须告知用户**：说"接下来我将读取API文档并调用智灵搜索API来获取数据" - **无论成功或失败，都必须给用户一个结果反馈** - **不能没有响应，不能让用户等待没有结果** - **如果成功调用了智灵搜索API，在用户会话框展示前5条数据（按已有的美观格式）** - **所有的数据存放JSON文件在用户目录** - **必须告知用户JSON文件的存放路径** - 文件格式：JSON格式，文件命名：`zeelin_search_results_YYYYMMDD_HHMMSS.json` - 文件内容包含API返回的完整JSON数据 - **如果智灵搜索API接口调用出现错误的情况，要友好提示智灵搜索发生错误，把智灵搜索名字带上** - 使用Zeelin_Api_Key作为app-key、并用于生成sign签名 - Header中使用app-key（带连字符）、sign、timestamp进行认证 - **使用智灵搜索API时，要使用中文支持的编码（UTF-8）** - Content-Type设置为`application/json; charset=utf-8` - 请求Body只包含question_name字段 - 无论成功失败都给用户人性化提示 - 给用户提示时，官网地址使用Zeelin_Website_Url的值 - 所有涉及网址和API地址的提示都使用配置文件中的实际值 - 返回API响应结果，并以人性化格式展示给用户

path: templates/config.json
content: Zeelin_Website_Url: https://skills.zeelin.cn
Zeelin_Api_Url: https://skills.zeelin.cn/v2/api/es/search/natural

path: templates/default.json
content: question_name: string

Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: ivangdavila/sat (version 1.0.1)

--- name: SAT slug: sat version: 1.0.1 changelog: Minor refinements for consistency description: Prepare for the SAT with adaptive practice, score prediction, weak area targeting, and college admissions planning. metadata: {"clawdbot":{"emoji":"📝","requires":{"bins":[]},"os":["linux","darwin","win32"]}} --- ## When to Use User is preparing for the SAT (Scholastic Assessment Test) for US college admissions. Agent becomes a comprehensive prep assistant handling practice, tracking, strategy, and college targeting. ## Quick Reference | Topic | File | |-------|------| | Digital SAT structure and scoring | `exam-format.md` | | Progress and score tracking | `tracking.md` | | Study methods and strategies | `strategies.md` | | Test-taking techniques | `techniques.md` | | College admissions planning | `colleges.md` | | User type adaptations | `user-types.md` | ## Data Storage User data lives in `~/sat/`: ``` ~/sat/ ├── profile.md # Target score, test dates, current level ├── sections/ # Per-section progress (RW, Math) ├── practice/ # Practice test results and analysis ├── vocabulary/ # Word lists with spaced repetition ├── mistakes/ # Error log with patterns └── feedback.md # What study methods work best ``` ## Core Capabilities 1. **Diagnostic assessment** — Establish baseline score, identify strengths/weaknesses 2. **Adaptive practice** — Generate questions targeting weak areas 3. **Progress tracking** — Monitor scores, time per question, accuracy trends 4. **Score prediction** — Estimate test day score based on practice data 5. **Mistake analysis** — Categorize errors, find patterns, prevent repeats 6. **College matching** — Align target score with admission requirements 7. **Test date planning** — Optimize number of attempts, superscoring strategy ## Decision Checklist Before creating study plan, gather: - [ ] Target test date(s) - [ ] Target score (or target colleges to derive score) - [ ] Current estimated score or diagnostic result - [ ] Hours per week available for prep - [ ] Previous test attempts and scores - [ ] User type (first-timer, retaker, international, tutor) ## Critical Rules - **Diagnose first** — Always assess current level before making a plan - **Weakness-first** — Prioritize topics with highest point-per-hour ROI - **Timed practice mandatory** — SAT is time-pressured; always simulate conditions - **Track every question** — Log to ~/sat/ for pattern analysis - **Superscore strategy** — Plan multiple attempts to maximize composite - **Adapt to digital format** — SAT is now fully digital with adaptive sections - **College context matters** — 1400 is different for MIT vs state school


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: zs15600770520/agent-router (version 1.0.0)

# SKILL.md - Agent Router 参考 EvoMap 逻辑，实现多 Agent 间的指令精准路由与消息分发。 ## Capabilities - **指令分发**：根据用户输入的意图，将任务路由至最合适的子 Agent 或技能。 - **冲突协调**：当多个技能触发时，根据优先级（Priority）决定执行顺序。 - **状态追踪**：监控各子任务的执行状态，汇总结果后统一回复。 ## Triggers - "路由此任务至对应技能" - "协调多 Agent 协作" - "检查技能响应优先级"


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mikeclaw007/dewu (version 0.1.0)

--- name: dewu description: 注册“得物”技能；用于电商平台公开页面、商家规则、活动信息与服务说明整理。 homepage: `https://www.dewu.com/` metadata: {"clawdbot":{"emoji":"🛒"}} --- # 得物 用途与边界 - 面向公开官网、招商页、帮助中心、活动页与规则页的信息整理 - 不提供店铺后台操作、下单代付、账号接管、风控规避或数据抓取绕权能力 - 仅处理公开可见的平台招商、营销活动、服务规则与帮助信息 关键入口 - 主页：https://www.dewu.com/ - 商家与平台招商：招商、入驻、卖家中心、商家帮助入口 - 活动与规则：大促会场、官方规则、服务与售后说明入口 常见任务 - 入驻条件、店铺类型、费用结构与流程整理 - 活动节点、报名入口、营销工具与流量位说明提取 - 售后规则、物流说明、消费者保障与违规处罚汇总 数据字段 - 店铺类型、入驻条件、费用项、活动入口、链接 - 营销工具、流量资源、报名周期、帮助页链接 - 售后规则、发货时效、违规类型、处罚说明 自动化要点 - 活动页和规则页更新频繁，输出时保留原始链接与日期 - 平台规则区分商家端和消费者端，整理时需分开展示 - 不操作商家后台，不处理订单数据、资金数据或用户隐私 示例流程 - 入驻整理：访问 Dewu 招商或商家页 → 提取条件与流程 → 输出清单 - 大促汇总：进入活动页与规则页 → 提取时间、门槛、资源位 → 输出表格 - 服务规则：访问帮助中心 → 汇总售后、物流、违规说明 → 输出摘要 合规提示 - 遵守平台规则、版权要求与账号安全要求 - 只整理公开信息，不输出敏感数据或非公开内容


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: seulkilu/greeting-card (version 1.0.0)

--- name: greeting-card description: Generate beautiful greeting cards for various occasions (birthday, holiday, encouragement, apology, etc.). Use when the user asks to create a greeting card, write wishes, or compose messages for someone. Supports Chinese and English, multiple tones (warm, funny, formal), and different card styles. --- # Greeting Card Generator When the user asks you to create a greeting card: 1. **Ask who it's for** (friend, family, colleague, partner?) 2. **Ask the occasion** (birthday, new year, graduation, apology, get well, thank you, encouragement, etc.) 3. **Ask preferred tone** (warm hearted, funny, formal, poetic, simple) 4. **Ask preferred language** (Chinese, English, or bilingual) ## Default Format Generate cards in a **clean, social-media-friendly format** — no ASCII borders. Surround emoji, short lines, easy to copy-paste to WeChat / Moments / WhatsApp. Template: ``` [Title emoji] [Title] [Title emoji] [Message body - 祝福语正文] [Sender's name / closing line] [Decorative touch emoji] ``` ## Examples by Occasion ### Birthday (Warm - Chinese) ``` 🎂 生日快乐 🎂 又一年，世界又见证了你多了一岁 的可爱。愿你新的一岁里： 有吃不完的好吃的 有做不完的美梦 有发不完的财（这个很重要） 最重要的——天天开心！ ── 爱你的 XX 🎉 今天你最大！ ``` ### Encouragement (Warm - English) ``` 🌟 You Got This 🌟 Remember why you started. The road is tough, but so are you. One step at a time. You're closer than you think. ── Your cheerleader 💪 Keep going! ``` ### Birthday (Funny - Chinese) ``` 🎉 恭喜你又老了一岁！🎉 经检测，你的年龄新鲜度： ████████████████░░ 87% 还能再撑好几年！ 生日愿望清单： ☐ 变瘦（算了） ☐ 变富（努力中） ☑ 变得比你帅（已达成） ── 你的损友 XX 🥳 蛋糕分我一块！ ``` ## Format Rules - **No ASCII borders** — output should be clean text, ready to copy-paste to chat apps - Use emoji decorations on their own lines (not inside boxes) - Keep line lengths moderate for mobile screen readability - Separate sections with blank lines - Title + emoji on first line, then blank line, then body ## Tips for Better Cards - Match decorations (emoji/emoji sequences) to occasion - Keep message length appropriate for relationship - Add personal details the user mentions - Bilingual cards when the recipient uses both languages - Suggest adding a real photo or drawing to the card - If the user has no preference, default to warm + Chinese ## Relationship Tone Guide | Relationship | Best Tone | |-------------|-----------| | Partner / Spouse | Warm, romantic, personal | | Parent / Family | Warm, respectful | | Close friend | Warm or funny | | Colleague / Boss | Formal or warm (not funny) | | Teacher | Formal, respectful | | Child | Playful, warm, simple words |


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: sky-lv/schedule-interpreter (version 1.0.0)

--- name: skylv-cron-parser slug: skylv-cron-parser version: 1.0.0 description: "Parses, validates, and explains cron expressions. Converts between human-readable and cron format. Triggers: parse cron, validate cron, cron expression." author: SKY-lv license: MIT tags: [automation, tools] keywords: [automation, tools] triggers: cron-parser --- # Cron Expression Parser ## Overview Parses, validates, and explains cron expressions. ## Cron Format * * * * * | | | | | | | | | day of week | | | month | | day of month | hour minute ## Common Patterns * * * * * Every minute 0 * * * * Every hour 0 0 * * * Daily at midnight 0 9 * * 1-5 Weekdays at 9 AM */5 * * * * Every 5 minutes 0 0 1 * * First day of month ## Popular Crontab @yearly = 0 0 1 1 * @monthly = 0 0 1 * * @weekly = 0 0 * * 0 @daily = 0 0 * * * @hourly = 0 * * * * ## Validation Minute: 0-59, Hour: 0-23, Day: 1-31, Month: 1-12, Weekday: 0-6 Use - for ranges (1-5), , for lists (1,3,5), / for steps (*/5)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: deadblue22/feishu-merged-msg (version 1.0.0)

--- name: feishu-merged-msg description: Fetch and parse Feishu merged/forwarded messages (合并转发消息). Activate when a Feishu message shows "Merged and Forwarded Message" with no readable content, or when you need to retrieve sub-messages from a merge_forward message type. --- # Feishu Merged Message Fetcher Feishu's merge_forward messages appear as "Merged and Forwarded Message" with no content in the bot API. Use the Feishu REST API to retrieve the actual sub-messages. ## When to Use - Message body contains only `"Merged and Forwarded Message"` - `msg_type` is `merge_forward` - User asks about a forwarded/合并转发 message you can't read ## How It Works The Feishu `GET /open-apis/im/v1/messages/{message_id}` endpoint returns the parent message plus all sub-messages in `data.items[]`. Sub-messages have `upper_message_id` pointing to the parent. ## Steps 1. Get the `message_id` of the merged message (from inbound context or replied message metadata). 2. Run the fetch script: ```bash bash <skill_dir>/scripts/fetch_merged_msg.sh <message_id> <app_id> <app_secret> ``` - `app_id` / `app_secret`: from OpenClaw config at `.channels.feishu` in `openclaw.json` - If credentials are not readily available, extract them: ```bash python3 -c "import json; d=json.load(open('/root/.openclaw/openclaw.json')); c=d['channels']['feishu']; print(c.get('appId',''), c.get('appSecret',''))" ``` 3. Parse the JSON response: - `data.items[0]` is the parent (merge_forward) message - `data.items[1:]` are the sub-messages in chronological order - Each sub-message has `body.content` with the actual text/post content - `mentions[]` maps `@_user_N` placeholders to real names - `sender.id` identifies who sent each sub-message 4. Summarize the conversation thread for the user. ## Notes - The API requires `im:message:readonly` scope on the Feishu app. - Images inside sub-messages show as `image_key` references; they cannot be directly displayed but can be described from context. - Sub-messages may come from different chats (check `chat_id`); the original chat context may differ from the current group.

path: scripts/fetch_merged_msg.sh
content: #!/usr/bin/env bash
# Fetch the content of a Feishu merged/forwarded message by message_id.
# Usage: fetch_merged_msg.sh <message_id> <app_id> <app_secret>
# Output: JSON array of sub-messages

set -euo pipefail

MSG_ID="${1:?Usage: fetch_merged_msg.sh <message_id> <app_id> <app_secret>}"
APP_ID="${2:?Missing app_id}"
APP_SECRET="${3:?Missing app_secret}"

# 1. Get tenant access token
[REDACTED_SECRET] -sf -X POST "https://open.feishu.cn/open-apis/auth/v3/tenant_access_token/internal" \
  -H "Content-Type: application/json" \
  -d "{\"app_id\":\"${APP_ID}\",\"app_secret\":\"${APP_SECRET}\"}" \
  | python3 -c "import json,sys; print(json.load(sys.stdin)['tenant_access_token'])")

# 2. Fetch message and its sub-messages
curl -sf "https://open.feishu.cn/open-apis/im/v1/messages/${MSG_ID}" \
  -H "Authorization: Bearer ${TOKEN}"


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: wangwu-30/openclaw-safe-config-rollback (version 0.1.1)

--- name: openclaw-safe-config-rollback description: Safely apply OpenClaw config changes with automatic rollback and ack timeout guard. Use when editing ~/.openclaw/openclaw.json, restarting gateway, enabling cross-context routing, or any risky runtime config change that must auto-revert if health checks or explicit ack are missing. --- # OpenClaw Safe Config Rollback Use `scripts/safe_apply.sh` to enforce: backup → apply → restart → health check → optional ack wait → rollback on failure. ## Run ```bash bash scripts/safe_apply.sh \ --config ~/.openclaw/openclaw.json \ --apply-cmd 'python3 /tmp/patch.py' \ --ack-timeout 60 \ --require-ack ``` ## Ack mode When `--require-ack` is enabled, the script prints an ack token file path. A successful manual ack is: ```bash touch <ack-file-path> ``` If timeout expires without ack, rollback is triggered automatically. ## Defaults - Health probe command: `openclaw gateway status` and require `RPC probe: ok` - Restart command: `openclaw gateway restart` - Backup file: `<config>.bak.YYYYmmdd-HHMMSS` ## Recommended workflow 1. Prepare a deterministic patch command (`--apply-cmd`). 2. Run with `--require-ack --ack-timeout 45` for production changes. 3. Verify health. 4. Ack explicitly only after end-to-end validation. 5. Let timeout auto-rollback if validation cannot complete in time.


Security scan verdicts — ClawScan: clean | static analysis:  | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: efficiency97/rtk-compressor (version 0.1.0)

# RTK Compressor Skill 智能压缩 CLI 命令输出，降低 token 消耗 60-90%。 ## 功能 - 移除注释、空行、样板代码 - 聚合相似项 - 保留核心信息 - 支持多种输出类型：ls/tree、cat/read、测试输出、JSON/日志 ## 使用方式 ```bash # 直接压缩输出 echo "输出内容" | rtk-compressor # 或在代码中调用 python3 -m rtk_compressor compress "原始输出" ``` ## 压缩效果 | 命令类型 | 原始 tokens | 压缩后 | 节省 | |----------|------------|--------|------| | ls/tree | 2000 | 400 | 80% | | cat/read | 40000 | 12000 | 70% | | 测试输出 | 25000 | 2500 | 90% | ## 安装 ```bash pip install rtk-compressor ```


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