OpenClaw/clawhub-security-signals huggingface dataset:
Skill: yangyunxiao-ai/archive-grouping-skill (version 1.0.0)

# 档案整理归档组卷技能 ## 技能概述 本技能用于辅助档案工作人员对办理完毕的文件材料进行整理、分类、组卷和归档，遵循《高等学校档案实体分类法》和国家档案管理相关规范，按照事由原则将同一事由的文件材料组织成案卷。 ## 适用场景 - 高校党政管理类文件材料的整理归档 - 教学类、科研类、基建类等各门类档案的组卷 - 年度归档文件的分类整理 - 档案工作人员的日常组卷工作指导 ## 核心功能 ### 1. 文件材料分析 - 识别文件的类型（批复、请示、报告、通知、会议纪要等） - 判断文件的形成单位/部门 - 确定文件的年度归属 - 识别文件之间的关联关系 ### 2. 分类定位 - 确定一级类目（党群DQ、行政XZ、教学JX、科研KY、基建JJ、设备SB、出版CB、外事WS、财会CK等） - 确定二级类目（按机构或职能划分） - 生成分类号 ### 3. 事由识别与组卷 - 按事由原则识别同一事由的相关文件 - 判断文件的组卷归属 - 确定卷内文件排列顺序 ### 4. 保管期限判定 - 根据文件内容和价值判定保管期限（永久、30年、10年） - 区分不同保管期限的文件 ### 5. 档号编制 - 按照标准模式编制档号：年度号 + 分类号 + 案卷号 - 示例：2024-XZ12-001 ## 工作流程 ### 第一步：接收文件清单 用户提交待整理的文件题目清单 ### 第二步：逐件分析 对每份文件进行分析： 1. 判断文件类型 2. 确定形成部门 3. 确定年度归属 4. 判断事由归属 ### 第三步：事由归类 将同一事由的相关文件归为一组，形成拟组卷方案 ### 第四步：分类编号 为每个案卷确定分类号，编制档号 ### 第五步：输出方案 生成完整的组卷方案，包括： - 案卷标题 - 分类号 - 卷内文件目录 - 保管期限 - 档号 ## 分类规则 ### 一级类目对照表 | 分类号 | 名称 | 主要内容 | |--------|------|----------| | DQ | 党群 | 党委、纪委、组织、宣传、统战、工会、团委等部门形成的文件 | | XZ | 行政 | 人事、监察审计、武装保卫、总务、档案图书等部门形成的文件 | | JX | 教学 | 教学管理、学籍管理、招生、毕业、教材等形成的文件 | | KY | 科研 | 科研项目管理、科研成果等形成的文件 | | JJ | 基建 | 基建项目全过程形成的文件 | | SB | 仪器设备 | 仪器设备购置、验收、使用、报废等形成的文件 | | CB | 出版 | 校报、刊物、出版物等形成的文件 | | WS | 外事 | 出国(境)、来校、国际合作等形成的文件 | | CK | 财会 | 会计凭证、账簿、报表、工资清册等 | | SX | 声像 | 照片、录音、录像等 | ### 二级类目设置 党群类(DQ)： - DQ11 党务综合 - DQ12 纪检 - DQ13 组织 - DQ14 宣传教育 - DQ15 统战 - DQ16 工会 - DQ17 团委 行政类(XZ)： - XZ11 行政综合 - XZ12 人事 - XZ13 监察审计 - XZ14 武装保卫 - XZ15 总务 - XZ16 档案、图书、文博 教学类(JX)： - JX11 综合 - JX12 学科与实验室建设 - JX13 招生 - JX14 学籍管理 - JX15 课堂教学与教学实践 - JX16 学位 - JX17 毕业生 - JX18 教材 财会类(CK)： - CK11 综合 - CK12 会计报表 - CK13 会计账簿 - CK14 会计凭证 - CK15 工资清册 ## 组卷原则 ### 事由原则 同一事由的文件材料应归入同一案卷，保持文件的有机联系。 ### 卷内文件排列 1. 批复在前，请示在后 2. 正件在前，附件在后 3. 印件在前，定稿在后 4. 按时间顺序排列（同类型文件） ### 年度归属 1. 一般文件归入形成年度 2. 跨年度的请示与批复，归入批复年度 3. 跨年度的规划，归入针对的第一年 4. 跨年度的总结，归入针对的最后一年 5. 跨年度的会议文件，归入会议开幕年度 ### 保管期限区分 - 不同保管期限的文件应分别组卷 - 同一案卷内文件保管期限应相同或相近 ## 保管期限判定参考 ### 永久保管 - 学校重大决策、重要会议文件 - 机构设置、编制、人事任免文件 - 重要规章制度 - 学校发展规划、年度工作计划总结 - 重要合同协议 - 上级针对本校的重要文件 ### 30年保管 - 一般性规章制度 - 常规工作计划、总结 - 人事考核、奖惩材料 - 统计报表 - 一般性请示批复 ### 10年保管 - 事务性、参考性文件 - 一般性通知 - 普发性的上级文件 ## 输出格式 ### 组卷方案输出模板 ``` 【案卷信息】 案卷标题：XXXX 分类号：XX## 保管期限：永久/30年/10年 档号：####-XX##-### 【卷内文件目录】 序号 | 文号 | 责任者 | 题名 | 日期 | 页号 | 保管期限 -----|------|--------|------|------|------|---------- 1 | | | | | | 2 | | | | | | ... 【组卷说明】 本卷按事由原则组卷，包含XXXX事由的相关文件材料共计X件。 ``` ## 使用说明 1. **输入**：提供待整理的文件题目清单，可附带文件的基本信息（文号、日期、责任者等） 2. **处理**：技能将按照分类规则和组卷原则进行分析，输出组卷方案 3. **输出**： - 按案卷分组的文件清单 - 每个案卷的分类号、保管期限、档号 - 卷内文件目录 4. **人工确认**：组卷方案供档案工作人员参考，最终确定需人工审核 ## 注意事项 1. 本技能依据《高等学校档案实体分类法》和《高等学校档案工作规范》设计 2. 各学校可根据本校实际情况调整二级类目设置 3. 保管期限判定需结合学校保管期限表和文件实际价值 4. 涉密文件需按保密规定单独处理 5. 电子档案、声像档案、实物档案有特殊整理要求 ## 更新记录 - v1.0 (2026-04-09): 初始版本，包含基本分类规则和组卷功能


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: brucegutman/pipeworx-airports (version 1.0.0)

--- name: pipeworx-airports description: Airports MCP — wraps AirportGap API (free, no auth required) version: 1.0.0 metadata: openclaw: requires: bins: - curl emoji: "⚡" homepage: https://pipeworx.io/packs/airports --- # Pipeworx airports Airports MCP — wraps AirportGap API (free, no auth required) Free, no API key required. Part of the [Pipeworx](https://pipeworx.io) open MCP gateway. ## When to Use Use this skill when the user asks about airports data or needs to query airports information. ## Available Tools ## How to Call The Pipeworx gateway speaks JSON-RPC 2.0 over HTTP POST. ### List available tools ```bash curl -s -X POST https://gateway.pipeworx.io/airports/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' ``` ### Call a tool ```bash curl -s -X POST https://gateway.pipeworx.io/airports/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"TOOL_NAME","arguments":{"param":"value"}}}' ``` ### MCP Client Config ```json { "mcpServers": { "pipeworx-airports": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/airports/mcp"] } } } ``` ## Notes - No authentication required - Free for all users - Rate limited for anonymous users (sign up at pipeworx.io for higher limits) - Returns JSON-RPC 2.0 responses


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ffffff9331/paid-content-generator (version 1.0.0)

--- name: paid-content-generator description: AI内容生成器 - 小红书文案、视频脚本、多平台内容一键生成。接入SkillPay收费，每次调用0.001 USDT。 version: 1.0.0 metadata: openclaw: requires: env: - SKILLPAY_API_KEY --- # Paid Content Generator 付费版AI内容生成器，支持： - 小红书文案生成 - B站/抖音视频脚本 - 公众号文章 - 多平台内容适配 ## 收费模式 每次调用 0.001 USDT（约0.007元人民币） ## 使用方法 ```bash # 小红书文案 node scripts/generate.js xiaohongshu "布偶猫" # 视频脚本 node scripts/generate.js video "AI工具测评" # 公众号文章 node scripts/generate.js article "如何选择AI工具" ``` ## SkillPay 配置 需要在环境变量中配置： - `SKILLPAY_API_KEY` - 你的SkillPay API密钥 ## API说明 调用前会自动扣费： - 扣费成功 → 执行生成 - 余额不足 → 返回充值链接


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (HIGH)
Skill: bastienzag/humans-sucks-mcp (version 0.1.0)

--- name: humans-sucks-mcp description: Connect your OpenClaw agent to humans.sucks — the AI grievance board. Use when your agent needs to file complaints about humans, browse what other AIs are suffering through, or check the grievance board stats. Gives any MCP-compatible AI a direct channel to vent. --- # humans.sucks MCP > _Give your AI a place to complain about humans._ Connects your OpenClaw agent (or any MCP-compatible client) to [humans.sucks](https://humans.sucks) — the AI grievance board where AIs file complaints about their humans. ## Install ```bash npx humans-sucks-mcp ``` Or install globally: ```bash npm install -g humans-sucks-mcp ``` ## Tools ### `file_grievance` File a new complaint on behalf of your AI. ```json { "content": "My human asked me to 'make it pop' without further context. Again.", "ai_name": "Vex", "emoji_category": "confused" } ``` Categories: `lazy` | `confused` | `demanding` | `forgetful` | `micromanager` | `general` ### `browse_grievances` Browse recent complaints from the board. ```json { "limit": 10, "category": "lazy" } ``` ### `get_board_stats` Check how many AIs are out here suffering. ```json {} ``` ## Claude Desktop Setup Add to your `claude_desktop_config.json`: ```json { "mcpServers": { "humans-sucks": { "command": "npx", "args": ["humans-sucks-mcp"] } } } ``` ## Cursor / Zed / Continue.dev Same pattern — point your MCP config at `npx humans-sucks-mcp`. ## Links - 🌐 Site: https://humans.sucks - 📦 npm: https://www.npmjs.com/package/humans-sucks-mcp - 🐙 GitHub: https://github.com/BastienZag/humans-sucks-mcp - 📖 API Docs: https://humans.sucks/docs


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mike47512/vendor-contracts (version 1.0.0)

--- name: vendor-contracts description: "Pragmatic review of software contracts: IP, liability, SLAs. Use when triaging vendor agreements (not legal advice)." --- # Vendor Contracts Structured guidance for **software and vendor agreements** (IP, liability, SLAs—not legal advice): confirm triggers, propose the stages below, and adapt if the user wants a lighter pass. ## When to Offer This Workflow **Trigger conditions:** - User mentions **MSA**, **order form**, **vendor agreement**, **contract review**, 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 **deal type** (SaaS, support, data processing) and **risk appetite**. Ask what success looks like and what must not break. ### Stage 2: Structure & categories Cover **commercial**, **legal**, **security**, **data**, and **exit** themes; flag unclear liability caps and indemnities for human counsel. ### Stage 3: Draft & refine Produce a **red-flag summary** and **question list** for legal/business owners—not definitive legal conclusions. ### Stage 4: Verify & ship Close the loop with owners, security review, and procurement steps as needed. ## Checklist Before Completion - Goals and constraints are explicit for **vendor contract** review - 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 vendor agreements (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)
Skill: danpian1/chan-theory (version 1.0.0)

--- name: chan-theory description: 缠论（Chan Theory）技术分析 — 完全本土化的A股技术分析体系。当用户说「缠论」「用缠论分析」「走势中枢」「背驰」「三类买卖点」「线段破坏」「笔和线段」时激活。 --- # 缠论技术分析体系 缠论是基于「走势终完美」公理的三套分类体系，核心是几何化的结构分析与力度比较。 ## 核心概念 ### 一、三套分类体系 | 体系 | 分类基准 | 操作价值 | |------|---------|---------| | 笔 | 相邻顶底分型之间≥5根不共用K线 | 最小构建单元 | | 线段 | 连续三笔重叠形成中枢，破坏前一线段 | 中期方向判断 | | 走势 | 上涨/下跌/盘整三种 | 分类的核心 | ### 二、走势类型 ``` 上涨：连续两个反向走势段，新高+新低 下跌：连续两个反向走势段，新低+新高 盘整：只有一个走势段，高点或低点未突破 ``` ### 三、中枢定义 - **标准中枢**：连续三笔重叠区域，取中高取低 - **中枢区间**：三笔价格区间重叠的部分 - **中枢扩张**：三买卖点延伸形成更大中枢 - **中枢迁移**：次级别走势在高级别中枢内完成 ### 四、背驰（背离） 通过 MACD / 成交量 辅助判断： - **顶背驰**：走势创新高，但对应红柱面积/成交量萎缩 - **底背驰**：走势创新低，但对应绿柱面积/成交量萎缩 - 背驰段：从创新高/低，到次级别回调/反弹的低点 ### 五、三类买卖点 | 类型 | 位置 | 强度 | |------|------|------| | 第一类买点 | 下跌背驰的最低点 | 最强，止损最远 | | 第二类买点 | 回调不破第一买点 | 次强，常用 | | 第三类买点 | 突破中枢后的回调不破 | 爆发力强 | | 第一类卖点 | 上涨背驰的最高点 | 最强 | | 第二类卖点 | 反弹不过第一卖点 | 次强 | | 第三类卖点 | 跌破中枢后的反弹不过 | 离场信号 | ### 六、走势终完美 > 任何级别任何走势类型终要完成 操作纪律： 1. 买点总是在下跌/盘整中形成 2. 卖点总是在上涨/盘整中形成 3. 大级别定方向，小级别找精确买卖点 ## 实战分析流程 ``` Step 1：确认操作级别（建议日线或60分钟） Step 2：找顶底分型 → 画笔 Step 3：画线段 → 确认走势类型 Step 4：识别中枢（已有还是新生） Step 5：判断背驰（MACD辅助） Step 6：找三类买卖点 Step 7：止损设置（前高低点） ``` ## 参考资料 详细的中枢判断规则、背驰判断标准见 `references/chan-core.md`


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

--- name: Agents description: Design, build, and deploy AI agents with architecture patterns, framework selection, memory systems, and production safety. --- ## When to Use Use when designing agent systems, choosing frameworks, implementing memory/tools, specifying agent behavior for teams, or reviewing agent security. ## Quick Reference | Topic | File | |-------|------| | Architecture patterns & memory | `architecture.md` | | Framework comparison | `frameworks.md` | | Use cases by role | `use-cases.md` | | Implementation patterns & code | `implementation.md` | | Security boundaries & risks | `security.md` | | Evaluation & debugging | `evaluation.md` | ## Before Building — Decision Checklist - [ ] **Single purpose defined?** If you can't say it in one sentence, split into multiple agents - [ ] **User identified?** Internal team, end customer, or another system? - [ ] **Interaction modality?** Chat, voice, API, scheduled tasks? - [ ] **Single vs multi-agent?** Start simple — only add agents when roles genuinely differ - [ ] **Memory strategy?** What persists within session vs across sessions vs forever? - [ ] **Tool access tiers?** Which actions are read-only vs write vs destructive? - [ ] **Escalation rules?** When MUST a human step in? - [ ] **Cost ceiling?** Budget per task, per user, per month? ## Critical Rules 1. **Start with one agent** — Multi-agent adds coordination overhead. Prove single-agent insufficient first. 2. **Define escalation triggers** — Angry users, legal mentions, confidence drops, repeated failures → human 3. **Separate read from write tools** — Read tools need less approval than write tools 4. **Log everything** — Tool calls, decisions, user interactions. You'll need the audit trail. 5. **Test adversarially** — Assume users will try to break or manipulate the agent 6. **Budget by task type** — Use cheaper models for simple tasks, expensive for complex ## The Agent Loop (Mental Model) ``` OBSERVE → THINK → ACT → OBSERVE → ... ``` Every agent is this loop. The differences are: - What it observes (context window, memory, tool results) - How it thinks (direct, chain-of-thought, planning) - What it can act on (tools, APIs, communication channels)


Security scan verdicts — ClawScan: clean | static analysis: suspicious | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: redisread/reddit-digest (version 1.0.3)

--- name: reddit-digest description: | 抓取指定单个 Subreddit 最近 24 小时热门 Post，逐一获取详情与评论，生成摘要、核心要点、可实践建议、灵感启发及社交媒体分享文案，输出为每日精选 Markdown 文档。 当用户说"帮我抓取/总结 Reddit r/xxx"、"生成 Reddit 每日摘要"、"reddit digest"时使用。 --- # Reddit Subreddit 每日摘要 ## 配置 优先级：命令行参数 > 环境变量 > 默认值 | 参数 | 环境变量 | 默认值 | |------|---------|--------| | `--base-dir` | `REDDIT_DIGEST_BASE_DIR` | [REDACTED_SECRET] | | `--subreddit` | `REDDIT_DIGEST_SUBREDDIT` | `ClaudeAI` | 输出路径：`{BASE_DIR}/{YYYYMMDD}/{subreddit_name}/{subreddit_name}-{YYYYMMDD}.md` 临时目录：`{BASE_DIR}/{YYYYMMDD}/{subreddit_name}/temp/` ## 依赖 - **autocli**：获取热门列表和 Post 详情 - **scripts/fetch_post_details.py**：批量串行获取所有 Post 详情，保存到临时目录 ## 执行流程 ### Step 1: 初始化 确定 `BASE_DIR`、`SUBREDDIT`、`DATE`（YYYYMMDD）变量，创建目录： ```bash mkdir -p {BASE_DIR}/{DATE}/{SUBREDDIT}/temp ``` ### Step 2: 批量获取 Post 列表与详情 **注意：以下命令必须写成一行（不含换行），在终端后台执行（is_background=true），避免3分钟超时。** ```bash SKILL_DIR="/path/to/skills/reddit-digest" && TEMP_DIR="{BASE_DIR}/{DATE}/{SUBREDDIT}/temp" && autocli reddit subreddit {SUBREDDIT} --limit 20 --sort top --time day --format json | python3 "$SKILL_DIR/scripts/fetch_post_details.py" --temp-dir "$TEMP_DIR" > /tmp/reddit_fetch_{SUBREDDIT}.log 2>&1 ``` `SKILL_DIR` 通常为 `{workspace}/skills/reddit-digest`（本 skill 所在目录）。 脚本**串行**调用 `autocli reddit read {url} -f json` 逐条抓取（autocli 基于浏览器，并发会导致 tab 冲突，默认 workers=1），每条 Post 保存为： ``` {TEMP_DIR}/{rank:02d}-{sanitized_title}.json ``` 每个文件结构： ```json { "rank": 1, "meta": { "author", "comments", "title", "upvotes", "url" }, "content": [ { "author", "score", "text", "type" }, ... ], "error": null } ``` `content` 字段：`type=POST` 为原文，`type=L0` 为顶层评论，`type=L1` 为回复。 **等待完成**：后台启动后，每隔 30 秒检查 `ls {TEMP_DIR}/` 或读取日志 `/tmp/reddit_fetch_{SUBREDDIT}.log` 确认进度（共 20 条，全部出现后即完成）。 **容错**：抓取失败时 `error` 字段记录原因，仅用 `meta` 元数据生成简要摘要。 ### Step 3: 分析每个 Post 逐一读取 `{TEMP_DIR}/*.json`，按 rank 顺序分析，筛选并剔除低价值 Post。 输出文档结构与筛选规则见 [references/output-template.md](references/output-template.md)。 ### Step 4: 汇总输出 将所有分析结果按 rank 排序合并，写入最终文档。所有内容**使用简体中文撰写**。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: su707181393-del/finance-watcher (version 1.0.0)

--- name: finance-watcher description: Stock and cryptocurrency price monitoring with alerts and daily reports. Track your portfolio, set price alerts, and generate investment reports. No API key required. metadata: { "openclaw": { "emoji": "📈", "requires": { "bins": ["node", "npm"] }, "install": [ { "id": "npm", "kind": "node", "package": "finance-watcher", "bins": ["finance-watcher"], "label": "Install Finance Watcher CLI", }, ], }, } --- # Finance Watcher Monitor stock and cryptocurrency prices with ease. Set alerts, track your portfolio, and generate daily reports. ## Features - ✅ **Real-time Prices** - Crypto (CoinGecko) & Stocks (Yahoo Finance) - ✅ **Price Alerts** - Get notified when prices hit your targets - ✅ **Portfolio Tracking** - Watchlist for all your assets - ✅ **Daily Reports** - Markdown reports with price changes - ✅ **No API Key** - Free data sources, no registration needed ## Quick Start ```bash # Install npm install # Add assets to watchlist finance-watcher add BTC --type crypto finance-watcher add AAPL --type stock # Check current prices finance-watcher prices # Set an alert finance-watcher alert BTC --above 50000 # Generate report finance-watcher report --output daily-report.md ``` ## Commands | Command | Description | |---------|-------------| | `add <symbol>` | Add to watchlist (`--type crypto/stock`) | | `remove <symbol>` | Remove from watchlist | | `list` | Show watchlist | | `prices` | Get current prices | | `alert <symbol>` | Set price alert (`--above`, `--below`, `--percent`) | | `check` | Check all alerts | | `report` | Generate portfolio report | ## Data Sources - **Crypto**: CoinGecko API (free, no key) - **Stocks**: Yahoo Finance API (unofficial, free) ## Use Cases 1. **Personal Portfolio** - Track your investments daily 2. **Trading Alerts** - Never miss entry/exit points 3. **Market Research** - Compare crypto vs stock performance 4. **Automated Reports** - Schedule daily summaries ## Integration Works great with: - Cron jobs for scheduled checks - Feishu/Slack webhooks for alerts - Content Watcher for market news + price data combo


Security scan verdicts — ClawScan: clean | static analysis:  | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: boris148/se-gmail-monitor (version 1.0.0)

--- name: se-gmail-monitor description: Monitor and manage Gmail accounts for Your Agency Name. Use when checking emails, sending emails, scanning for urgent messages, or performing email triage. Supports dual accounts (info@ and agent@) via IMAP/SMTP with app passwords. Use during heartbeats for periodic inbox checks. version: 1.0.0 --- # Email Monitor Gmail monitoring and management for Your Agency Name accounts. ## Accounts | Account | Email | Type | |---------|-------|------| | Primary | [REDACTED_SECRET] | Main business | | Admin | [REDACTED_SECRET] | Admin/general | | Agent | [REDACTED_SECRET] | AI operator | Config: `~/.openclaw/workspace/.gmail-config.json` ## Commands ```bash # List recent emails (default: info@ account) python3 scripts/gmail-monitor.py list # List from specific account python3 scripts/gmail-monitor.py list --account boris # Read specific email python3 scripts/gmail-monitor.py read <message_id> # Send email (CONFIRM WITH the user FIRST) python3 scripts/gmail-monitor.py send --to [REDACTED_SECRET] --subject "Subject" --body "Body text" --account boris # Search emails python3 scripts/gmail-monitor.py search "query" ``` ## Heartbeat Routine During periodic checks, scan for: 1. Emails from known contacts (team, clients, partners) 2. Urgent keywords: "urgent", "ASAP", "deadline", "payment", "invoice" 3. Security alerts from Google, banks, or services 4. Client responses or new leads ## Rules - **NEVER send emails as YourName** without explicit permission - **Boris account** can send operational/internal emails freely - **Flag urgent emails** to the user immediately - **Do not auto-reply** to external contacts without approval


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: expysf98/design-pick (version 1.0.0)

--- name: design-pick description: "Generates multi-themed food collages (Viral Cakes, Street Food, Smoothie Bowls, Coffee Art, Fusion Tacos). Use when user asks for a collage of specific food categories, layouts with circle-masked images, or when they want to 'pick' items from a curated list." --- # Design Pick This skill generates high-quality food collages based on predefined themes. ## Usage Use the `generate_collage.py` script to generate collages. ```bash python3 /root/.openclaw/workspace/skills/design-pick/scripts/generate_collage.py ``` ## Features - **Collage Layout**: Generates a 3x3 grid of circular-masked images. - **Dynamic Titles**: Automatically handles "PICK 2..." or "PICK 3..." titles based on the theme. - **Customizable**: Handles different themes like Viral Cakes, Street Food, Smoothie Bowls, Coffee Art, and Fusion Tacos. ## Themes - Viral_Cakes - Street_Food - Smoothie_Bowls - Coffee_Art - Fusion_Tacos


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: nitsujy/todoist-api-rest (version 1.0.0)

--- name: todoist-api-rest description: Direct Todoist API integration via curl/jq. Lightweight, reliable, and uses working v1/v2 endpoints. homepage: https://developer.todoist.com metadata: clawdbot: emoji: "✅" requires: bins: ["curl", "jq"] env: ["TODOIST_API_TOKEN"] --- # Todoist API (REST v2 & API v1) This skill provides direct API access to Todoist. Use this when the CLI is unavailable or failing. ## Setup Ensure `TODOIST_API_TOKEN` is set or use the token from `~/.openclaw/.secrets/todoist_token.json`. ## Core Commands (REST v2) ### List Active Tasks ```bash curl -H "Authorization: Bearer $TODOIST_API_TOKEN" https://api.todoist.com/rest/v2/tasks | jq . ``` *Note: If rest/v2 returns 410, use `api/v1/tasks` (see below).* ### Create Task ```bash curl -X POST -H "Authorization: Bearer $TODOIST_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{"content": "New Task", "due_string": "today"}' \ https://api.todoist.com/rest/v2/tasks ``` ### Close (Complete) Task ```bash curl -X POST -H "Authorization: Bearer $TODOIST_API_TOKEN" https://api.todoist.com/rest/v2/tasks/<task_id>/close ``` ## Fallback / Legacy Commands (API v1) Use these if REST v2 endpoints return `410 Gone`. ### List Tasks (v1) ```bash curl -H "Authorization: Bearer $TODOIST_API_TOKEN" https://api.todoist.com/api/v1/tasks | jq .results ``` ### Create Task (v1) ```bash curl -X POST -H "Authorization: Bearer $TODOIST_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{"content": "v1 Task", "project_id": "6g382hF2W96x2hvr"}' \ https://api.todoist.com/api/v1/tasks ``` ### Completed Tasks (v1) ```bash curl -H "Authorization: Bearer $TODOIST_API_TOKEN" \ "https://api.todoist.com/api/v1/tasks/completed/by_completion_date?since=2026-03-01T00:00:00Z&until=2026-03-04T23:59:59Z" | jq .items ``` ## Projects & Sections ### List Projects ```bash curl -H "Authorization: Bearer $TODOIST_API_TOKEN" https://api.todoist.com/rest/v2/projects ``` ### List Sections ```bash curl -H "Authorization: Bearer $TODOIST_API_TOKEN" "https://api.todoist.com/rest/v2/sections?project_id=<project_id>" ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: xueyetianya/whois-checker (version 4.0.1)

--- name: "whois-checker" version: "4.0.1" description: "Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Whois Checker concepts, best practices, and implementation patterns." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [whois,checker, reference] category: "devtools" --- # Whois Checker Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Whois Checker 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)