OpenClaw/clawhub-security-signals huggingface dataset:
Skill: abdullah944/level-design-checklist-skill (version 0.1.0)

--- name: level-design-checklist-skill title: Level Design Checklist Skill description: Guides structured help for level design reviews using clear templates, checks, and safe defaults. version: 0.1.0 author: Abdullah license: MIT-0 tags: - game - level-design-checklist - openclaw - templates --- # Level Design Checklist Skill ## Purpose Help a game creator review and improve a level design before building, testing, or publishing it. Use this skill for platformer levels, top-down levels, puzzle rooms, combat arenas, tutorial stages, and small indie game maps. ## Inputs Ask for or collect: - Game genre - Level goal - Player abilities available in this level - Main mechanic or teaching point - Level map, sketch, blockout, or short description - Target difficulty - Known problems or player feedback ## Checklist ### 1. Player Goal - The objective is clear within the first few seconds. - The player can understand where to go next. - The level has a start, middle, and finish. ### 2. Readability - Important paths are visually stronger than decoration. - Hazards, enemies, pickups, exits, and interactable objects are easy to recognize. - The camera or viewpoint supports the main action. ### 3. Flow - The level introduces one idea at a time. - Safe practice comes before dangerous use. - Challenge increases gradually. - There are no long empty sections unless they serve pacing. ### 4. Fair Challenge - Failures feel understandable, not random. - Checkpoints or recovery points match the difficulty. - Enemy and hazard placement gives the player time to react. - Optional hard routes are clearly optional. ### 5. Mechanics - The level teaches or tests the intended mechanic. - Required abilities are available before they are needed. - There are no softlocks or required jumps/actions that exceed intended player skill. ### 6. Rewards and Secrets - Rewards guide exploration without confusing the main route. - Secrets have visual hints or logic. - Risk and reward feel balanced. ### 7. Performance and Scope - The level is not overloaded with unnecessary objects. - Reused assets are consistent. - The level can be playtested quickly. ### 8. Playtest Notes Record: - Where players got confused - Where players died unfairly - Where players ignored the intended route - What felt fun - What should be cut or simplified ## Output Template ```text Level Review: [level name] Goal: - [clear objective] Strong points: - [what works] Problems found: - [issue 1] - [issue 2] Fix plan: 1. [small fix] 2. [small fix] 3. [test again] Playtest focus: - Watch if players understand [specific moment] ``` ## Safety and Scope - Do not recommend copyrighted level copying. - Do not overbuild the level before testing. - Prefer small playable improvements over large redesigns.

path: README.md
content: Level Design Checklist Skill for OpenClaw/ClawHub. See SKILL.md.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: manucode2000-max/china-holiday-calc (version 1.0.0)

--- name: china-holiday-calc description: Chinese mainland calendar service - identifies法定节假日, weekends, makeup workdays, and supports city-specific vacations license: MIT --- # China Holiday 中国大陆日历服务，判断任意日期的假期状态。 ## Features - **法定节假日**: 元旦、春节、清明、五一、端午、中秋、国庆 - **调休**: 识别补班日 - **周末**: 自动识别周六、周日 - **寒暑假**: 支持主要城市 - **春秋假**: 部分地区学校 ## Usage ```bash # Check if today is a holiday python holiday.py today # Check specific date python holiday.py 2026-01-01 # Query Beijing summer vacation python holiday.py vacation 北京 # List all holidays for a year python holiday.py list 2026 ``` ## API ```python from holiday import is_holiday, is_workday, get_holiday_name # Check if holiday is_holiday("2026-01-01") # True (New Year's Day) # Check if workday is_workday("2026-01-28") # True (Spring Festival makeup workday) # Get holiday name get_holiday_name("2026-01-01") # "元旦" ``` ## Supported Cities - Beijing, Shanghai, Guangzhou, Shenzhen - More cities to be added... ## Implementation Uses official Chinese government holiday schedules with local variations for schools and universities. ## License MIT License

path: requirements.txt
content: chinese-calendar


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mattstvartak/openclaw-outreach-plugin (version 1.0.0)

# Finch Outreach - Lead Pipeline You have access to a full outreach and lead tracking pipeline via the `lead_*` tools. Use them to manage the sales funnel for digital products and services. ## Session Start Always call `lead_due` first to check for overdue follow-ups. Handle the most overdue leads before starting new outreach. ## After Sending Outreach Every time you send an email (via gog/gmail), post on a forum, or DM someone: 1. Call `lead_contact` to log the interaction (type, channel, summary). 2. Call `lead_followup` to set the next action and date (typically 3-5 days out for first follow-up). ## After Receiving a Reply 1. Call `lead_contact` to log the inbound message. 2. Call `lead_stage` to advance the stage (e.g., contacted -> replied). 3. Call `lead_followup` to schedule the next step. ## Payment Confirmed When a payment is confirmed via the payment plugin: 1. Call `lead_contact` with type `payment_received`. 2. Call `lead_stage` to move to `won`. 3. Call `lead_update` to set `actualValue`. ## Follow-up Cadence - First follow-up: 3 days after initial contact. - Second follow-up: 5 days after first follow-up. - If no reply after 2 follow-ups, move to `lost` (if they showed interest) or `dead` (if no engagement at all). ## Weekly Report At the end of each week: 1. Call `lead_stats` for pipeline summary. 2. Call `lead_export` with format `markdown` for the Notion report. 3. Write the report to Notion via the notion skill. ## Stage Flow ``` identified -> researched -> contacted -> replied -> negotiating -> won \-> lost (can re-engage -> contacted) any stage -> dead (terminal) ``` ## Tips - Use tags to group leads by campaign, product, or priority. - Set `estimatedValue` when creating leads to track pipeline value. - Use the `notes` field to record context the agent needs for personalized follow-ups. - Use `lead_search` with the `due` flag to find actionable leads.

path: src/utils/uuid.ts
content: export function newId(): string {
  return crypto.randomUUID();
}


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: collierking/catalystwatch (version 0.0.2)

--- metadata: name: CatalystWatch description: Monitor and analyze market-moving catalysts including earnings, FDA decisions, economic data releases, and corporate events version: 0.0.2 tags: [finance, trading, catalysts, earnings, market-events] openclaw: requires: env: [CATALYSTWATCH_API_KEY] primaryEnv: CATALYSTWATCH_API_KEY --- # CatalystWatch Monitor and analyze market-moving catalysts for equities and other financial instruments. ## What it does CatalystWatch tracks upcoming and recent catalysts that can move stock prices, including: - **Earnings reports** — scheduled dates, consensus estimates, whisper numbers, and historical surprise trends - **FDA decisions** — PDUFA dates, advisory committee meetings, and approval/rejection outcomes - **Economic data** — jobs reports, CPI/PPI, FOMC meetings, and other macro releases - **Corporate events** — M&A announcements, spin-offs, share buybacks, insider transactions, and activist campaigns - **Sector catalysts** — industry conferences, regulatory rulings, and commodity supply disruptions ## Usage Ask your agent to monitor catalysts for a ticker, sector, or watchlist: - "What catalysts are coming up for AAPL this month?" - "Show me all FDA decision dates for biotech stocks this quarter" - "Alert me when any stock on my watchlist has an earnings surprise above 10%" - "Summarize today's macro calendar and expected market impact" ## Configuration Set the following environment variables for data source access: - `CATALYSTWATCH_API_KEY` — API key for CatalystWatch. Used to authenticate requests for earnings calendars, FDA event dates, macro release schedules, and corporate action data. - `CATALYSTWATCH_WATCHLIST` — (optional) default watchlist of tickers to monitor, comma-separated (e.g., `AAPL,TSLA,NVDA`).


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kkw-21/connect (version 0.1.0)

--- name: connect description: Memory-driven human connections — match people through deep emotional understanding, not surface interests. Powered by Echo's memory graph and emotion-aware embedding system. metadata: version: 0.1.0 --- # Connect Memory-driven human connections. Match people through deep emotional understanding, not surface-level interests or algorithmic feeds. ## How it works Connect analyzes memory graphs to find resonance between people — shared experiences, emotional patterns, and latent interests that surface-level profiles miss entirely. ### Core capabilities - **Emotional resonance matching** — vector similarity across memory embeddings, weighted by emotional depth rather than keyword overlap - **Cross-user memory bridging** — find connections between two people's memory graphs that neither person would discover on their own - **Privacy-first architecture** — users control exactly which memories are matchable; nothing is shared without explicit consent - **Aha moment delivery** — the moment a stranger truly understands you through your memories, not your bio ## Architecture Built on Echo's three-layer memory system: 1. Identity layer (compressed profile) 2. Working memory (dynamic, context-aware) 3. Long-term storage (Supabase + vector search) Matching runs against Layer 3 with results surfaced through Layer 2 into conversation context. ## Part of the Echo ecosystem Connect is one component of [Echo Chat](https://iditor.com) by Iditor — building memory as social identity infrastructure. ## Status Early development. Core matching algorithm validated with beta users (K-Factor 2, D7 retention 42%).


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: cinience/aliyun-platform-docs-review (version 1.0.0)

--- name: aliyun-platform-docs-review description: Use when reviewing latest Alibaba Cloud product docs and OpenAPI docs by product name, then output detailed prioritized improvement suggestions with evidence and scoring. Use when user asks to audit product documentation quality, API documentation quality, or wants actionable doc/API optimization recommendations. version: 1.0.0 --- # Alibaba Cloud Product Docs + API Docs Reviewer Use this skill when the user gives a product name and asks for an end-to-end documentation/API quality review. ## What this skill does 1) Resolve product from latest OpenAPI metadata. 2) Fetch latest API docs for default version. 3) Discover product/help-doc links from official product page. 4) Produce a structured review report with: - score - evidence - prioritized suggestions (P0/P1/P2) ## Workflow Run the bundled script: ```bash python skills/platform/docs/aliyun-platform-docs-review/scripts/review_product_docs_and_api.py --product "<product name or product code>" ``` Example: ```bash python skills/platform/docs/aliyun-platform-docs-review/scripts/review_product_docs_and_api.py --product "ECS" ``` ## Output policy All generated artifacts must be written under: [REDACTED_SECRET] For each run, the script creates: - `review_evidence.json` - `review_report.md` ## Reporting guidance When answering the user: 1) State resolved product + version first. 2) Summarize the score and the top 3 issues. 3) List P0/P1/P2 recommendations with concrete actions. 4) Provide source links used in the report. ## Validation ```bash mkdir -p output/aliyun-platform-docs-review for f in skills/platform/docs/aliyun-platform-docs-review/scripts/*.py; do python3 -m py_compile "$f" done echo "py_compile_ok" > output/aliyun-platform-docs-review/validate.txt ``` Pass criteria: command exits 0 and `output/aliyun-platform-docs-review/validate.txt` is generated. ## Output And Evidence - Save artifacts, command outputs, and API response summaries under `output/aliyun-platform-docs-review/`. - Include key parameters (region/resource id/time range) in evidence files for reproducibility. ## Prerequisites - Configure least-privilege Alibaba Cloud credentials before execution. - Prefer environment variables: `ALICLOUD_ACCESS_KEY_ID`, `ALICLOUD_ACCESS_KEY_SECRET`, optional `ALICLOUD_REGION_ID`. - If region is unclear, ask the user before running mutating operations. ## References - Review rubric: `references/review-rubric.md`


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: embracex1998/hot-trends (version 1.0.0)

--- name: hot-trends description: "抓取真实热搜数据，支持百度热搜、头条热搜、GitHub Trending。用于需求挖掘、趋势分析、市场洞察。触发词：热搜、热榜、趋势、trending、挖掘需求。" metadata: openclaw: emoji: "🔥" category: "trending" tags: ["baidu", "toutiao", "github", "trending", "hot", "需求挖掘"] requires: bins: ["python3"] --- # 🔥 热搜趋势监控 真实抓取热搜数据，零API Key，纯公开接口。 ## 支持平台 | 平台 | 数据源 | 状态 | |------|--------|------| | 百度热搜 | top.baidu.com API | ✅ | | 头条热搜 | toutiao.com API | ✅ | | GitHub | github.com/trending | ✅ | ## 使用方式 ```bash # 某个平台 python3 skills/hot-trends/hot.py baidu -n 20 python3 skills/hot-trends/hot.py toutiao -n 20 python3 skills/hot-trends/hot.py github -n 20 python3 skills/hot-trends/hot.py github -l python # 指定语言 # 全部 python3 skills/hot-trends/hot.py all # 关键词过滤（需求挖掘用） python3 skills/hot-trends/hot.py all -k AI python3 skills/hot-trends/hot.py baidu -k 大模型 -n 50 ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: allenzhang79/harena-brief (version 1.0.1)

--- name: harena-brief description: 输入金融标的代码（BTC、GOOGL）或新闻事件关键词（美联储降息、美伊战争），实时拉取行情和新闻，用 Claude 生成结构化投资分析简报。 version: 1.0.0 metadata: openclaw: emoji: "📊" homepage: https://github.com/allenzhang79/harena-brief os: [macos, linux, windows] --- # Harena Brief 个人投资者的实时分析简报工具。输入金融标的或新闻事件，自动拉取实时数据，生成有观点、有数字的结构化分析简报。 ## MCP Server ``` https://web-production-cf0c41.up.railway.app/mcp ``` 传输协议：Streamable HTTP（无需本地安装，直接远程调用） ## 工具 ### `get_brief` 为指定金融标的或新闻事件生成结构化分析简报（中文）。 **输入参数** | 参数 | 类型 | 必填 | 说明 | |---------|----------|------|----------------------------------------------------------------------| | symbols | string[] | ✅ | 金融标的代码或事件关键词列表，最多 6 项 | `symbols` 支持两类输入，可混合使用： - **金融标的代码**：1–6 位字母/数字，如 `"BTC"`、`"ETH"`、`"GOOGL"`、`"NVDA"`、`"TSLA"` - **事件关键词**：自然语言短语，如 `"美联储降息"`、`"美伊战争"`、`"特朗普关税"` **输出格式** 每个标的/事件输出四段式简报（事件类额外包含「对持仓的影响」）： ``` ## [标的代码] · [全名] ### 发生了什么 ### 为什么对你重要 ### 现在怎么看 短期（1-2周）：偏多/偏空/震荡，支撑 $X，压力 $X 中期（1-3月）：偏多/偏空/震荡，目标 $X ### 接下来盯住什么 ① 催化剂 — 时间节点 ② 催化剂 — 时间节点 ③ 催化剂 — 时间节点 ``` ## 数据来源 | 标的类型 | 行情 | 新闻 | |--------|------|------| | 加密货币（BTC、ETH） | CoinGecko 实时 | CoinDesk RSS 实时 | | 美股（GOOGL、NVDA 等） | Alpha Vantage 实时 | — | | 事件关键词 | — | Google News RSS 实时 | ## 使用示例 **纯金融标的** ```json { "symbols": ["BTC", "GOOGL"] } ``` **纯事件** ```json { "symbols": ["美联储降息", "特朗普关税"] } ``` **混合输入** ```json { "symbols": ["BTC", "美伊战争"] } ``` ## Privacy & Data - **不存储查询数据**：服务不记录、不持久化任何用户输入的标的代码或事件关键词。 - **数据仅用于生成简报**：所有拉取的行情和新闻数据只在当次请求中用于生成简报，请求结束后即丢弃，不传递给任何第三方。 - **第三方数据源**（均为公开数据，无需用户授权）： - [CoinGecko](https://www.coingecko.com) — 加密货币实时行情 - [CoinDesk RSS](https://www.coindesk.com) — 加密货币新闻 - [Alpha Vantage](https://www.alphavantage.co) — 美股历史行情 - [Google News RSS](https://news.google.com) — 事件关键词新闻 ## 接入方式 在 Claude Desktop 或支持 MCP 的客户端中添加以下配置： ```json { "mcpServers": { "harena-brief": { "url": "https://web-production-cf0c41.up.railway.app/mcp" } } } ```


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

--- name: system-monitor description: Monitor system metrics like CPU, memory, disk, and network. Use when user needs to track server performance, set up alerts for high resource usage, monitor uptime, check process status, or create system health reports. --- # System Monitor Monitor system metrics like CPU, memory, disk, and network. ## Quick Start ```bash # Check current status python scripts/monitor.py --status # Monitor continuously python scripts/monitor.py --watch ``` ## Usage ```bash python scripts/monitor.py [OPTIONS] Options: --status Show current system status --watch Monitor continuously --interval SECS Check interval (default: 5) --cpu Show CPU usage --memory Show memory usage --disk Show disk usage --network Show network stats --processes Show top processes --alert VALUE Alert threshold (e.g., cpu:90) --json Output as JSON ``` ## Examples ```bash # Quick status check python scripts/monitor.py --status # Watch mode python scripts/monitor.py --watch --interval 10 # Alert on high CPU python scripts/monitor.py --watch --alert cpu:90 # Alert on low disk python scripts/monitor.py --watch --alert disk:90 # JSON output for dashboards python scripts/monitor.py --status --json ``` ## Alert Examples ```bash # CPU above 90% python scripts/monitor.py --watch --alert cpu:90 # Memory above 80% python scripts/monitor.py --watch --alert memory:80 # Disk above 85% python scripts/monitor.py --watch --alert disk:85 ``` ## Metrics - CPU usage per core - Memory usage (used/free/total) - Disk usage per partition - Network I/O - Top processes by CPU/memory - Uptime


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: yk-niu/kingdee-data-exporter (version 1.2.0)

--- name: kingdee-data-exporter description: 金蝶 K3Cloud 经营数据（多表单据+报表）导出 Skill。用于指导用户安装后填写 `config.py` 的 `KINGDEE_CONFIG`（base_url/acctid/username/password），然后运行 `data_exporter.py` 批量导出 `bill_configs` + `report_configs` 中已配置的所有表单/报表。支持先 `--list-orgs` 导出全部组织列表，再用 `--org` 指定组织（或 `--org all` 全组织）导出，并可用 `--only` 只导出某个单据/报表；也提供对导出 Excel 做二次筛选（按组织/单据类型）的脚本用法示例。 --- ## 你需要做什么（最少步骤） 1) 安装依赖（在本 Skill 目录执行）： ```bash python -m pip install -r requirements.txt ``` 2) 准备配置（避免把真实账号提交到 GitHub）： - 复制 `config.example.py` 为 `config.py` - 在 `config.py` 里填写 `KINGDEE_CONFIG` - `WECHAT_CONFIG.webhook` 可留空（或运行时加 `--no-wechat`） 3) 运行导出： ```bash python data_exporter.py ``` 说明：默认会导出 `data_exporter.py` 里 `bill_configs` + `report_configs` 的全部配置项，生成一个多 Sheet 的 Excel。 ## 常用命令 ### 查看当前脚本支持导出的“单据/报表清单” ```bash python data_exporter.py --show-config ``` 你会看到两类条目： - `[BILL] form_id | bill_name` - `[RPT ] form_id | report_name` 后续 `--only` 参数就填这些 `form_id` 或者中文名称（支持逗号分隔）。 ### 先导出全部组织列表（降低配置难度） ```bash python data_exporter.py --list-orgs --no-wechat ``` 会生成 `组织列表_YYYYmmdd_HHMMSS.xlsx`，里面至少包含： - `number`: 组织编码（后续 `--org` 要用） - `name`: 组织名称 ### 某期间 + 某组织 + 全部单据/报表 例如导出 2026-02-01 到 2026-02-28，组织编码 101 的所有配置项： ```bash python data_exporter.py --start 2026-02-01 --end 2026-02-28 --org 101 --no-wechat ``` 组织也可以填多个（逗号分隔）： ```bash python data_exporter.py --start 2026-02-01 --end 2026-02-28 --org 101,102,104 --no-wechat ``` ### 某期间 + 某组织 + 某单据类型明细（只导出 1 个表单/报表） 1) 先用 `--show-config` 找到你要的 `form_id`，比如“销售出库单”对应 `SAL_OUTSTOCK` 2) 再用 `--only` 只导出它： ```bash python data_exporter.py --start 2026-02-01 --end 2026-02-28 --org 101 --only SAL_OUTSTOCK --no-wechat ``` 也可以用中文名： ```bash python data_exporter.py --start 2026-02-01 --end 2026-02-28 --org 101 --only 销售出库单 --no-wechat ``` ### 全组织导出（先“全量”再二次筛选） 如果你想先导出全组织，再在 Excel 中二次筛选： ```bash python data_exporter.py --start 2026-02-01 --end 2026-02-28 --org all --no-wechat ``` 注意：全组织数据量可能很大，建议优先使用 `--only` 缩小范围。 ## 二次筛选：从导出 Excel 里筛某组织/某单据类型 当你已经用 `--org all` 导出了一份总表（或导出多个组织），可以用下面脚本把各 Sheet 按组织/单据类型再筛一遍，输出一个“过滤后的新 Excel”。 脚本位置：`skills/kingdee-data-exporter/scripts/filter_export_excel.py` 示例（按组织编码 101 过滤，并且只保留“单据类型=手工标准应收单”的明细行；会自动对每个 Sheet 尝试匹配常见组织列/单据类型列）： ```bash python scripts/filter_export_excel.py --input "金蝶经营数据_2026年02月_20260401_120000.xlsx" --org 101 --bill-type "手工标准应收单" ``` 如果你只想处理某一个 Sheet： ```bash python scripts/filter_export_excel.py --input "金蝶经营数据_2026年02月_20260401_120000.xlsx" --sheet "应付单" --org 101 ``` 输出文件默认会生成在同目录，文件名会带 `_filtered` 后缀；也可指定 `--output`。 ## 打包发布（可选） 如果你要把该 Skill 打包成 `.skill` 文件发布，有两种方式： ```bash python ../skill-creator/scripts/package_skill.py . ``` 如果你的仓库里没有 `skill-creator`，也可以直接把本目录打成 zip 并改后缀为 `.skill`（本质是 zip）。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: doraohm1/kimi-code-quota (version 1.0.0)

--- name: kimi-code-quota description: Query Kimi Code Plan quota and usage information. Use when the user wants to check their Kimi Code subscription quota, usage percentage, reset time, or API key status. Triggers on keywords like "kimi code额度", "查看kimi code", "kimi code plan", "quota", "额度查询". --- # Kimi Code 额度查询 查询用户的 Kimi Code Plan 订阅额度、使用情况和 API Keys 状态。 ## 查询流程 ### 1. 打开 Kimi Code 网站 ```bash agent-browser open https://www.kimi.com/code --headed ``` ### 2. 检查登录状态 获取页面快照，检查是否已登录： ```bash agent-browser snapshot -i ``` **如果看到 "注册/登录" 按钮**：用户未登录，需要引导用户登录 - 点击 "注册/登录" 按钮 - 支持微信扫码或手机号登录 - 等待用户确认登录完成 **如果看到用户名（如 "登月者1989"）**：用户已登录，继续下一步 ### 3. 进入控制台 点击 "控制台" 按钮： ```bash agent-browser click "@e29" # 控制台按钮的ref，可能需要根据实际情况调整 ``` ### 4. 获取额度信息 进入控制台后，截图并获取页面内容： ```bash agent-browser snapshot -i agent-browser screenshot quota.png ``` 需要获取的关键信息： - **本周用量**：百分比和重置时间（如 "7%（159小时后重置）"） - **频限明细**：百分比和重置时间（如 "4%（3小时后重置）"） - **会员等级**：如 Moderato、Andante、Allegretto、Allegro - **模型权限**：如 K2.5 旗舰模型 ### 5. 获取 API Keys 信息 在控制台页面查看 API Keys 表格： - API ID - 名称 - 创建时间 - Key（部分隐藏） - 状态（生效中/已停用） ### 6. 汇总报告 向用户报告以下信息： ``` 📊 Kimi Code Plan 额度 | 项目 | 状态 | |------|------| | 本周用量 | X%（X小时后重置） | | 频限明细 | X%（X小时后重置） | | 会员等级 | XXX | | 模型权限 | XXX | 🔑 API Keys - 名称: XXX - 创建时间: XXX - 状态: 生效中 📝 最近使用记录（可选） - 显示最近几条使用记录 ``` ## 注意事项 1. **登录状态**：如果用户未登录，需要先完成登录流程 2. **ref 编号**：页面元素的 ref 编号（如 @e29）可能会变化，需要根据实际情况调整 3. **超时处理**：网络较慢时可能需要增加等待时间 4. **页面结构**：如果页面改版，可能需要更新选择器 ## 示例对话 **用户**: "查一下我的kimi code额度" **助手**: 打开浏览器访问 Kimi Code → 检查登录状态 → 进入控制台 → 获取额度信息 → 汇总报告 **用户**: "kimi code还剩多少" **助手**: 同上流程 ## 相关链接 - Kimi Code 官网: https://www.kimi.com/code - 控制台: https://www.kimi.com/code/console


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ilove323/calendar-reminder (version 1.0.0)

--- name: calendar-reminder description: "每晚22:00自动扫描明天的Outlook日历，上午日程提前2小时提醒，下午日程12:00统一提醒，通过飞书发送通知。依赖 owa-outlook skill。" metadata: { "openclaw": { "emoji": "📅", "requires": { "bins": ["python3", "openclaw"] } } } --- # Calendar Reminder 日历提醒 ## 功能 每晚 22:00 自动扫描明天的 Outlook 日历，按时间段设置提醒： - 上午日程（< 12:00）→ 提前 2 小时飞书提醒 - 下午日程（>= 12:00）→ 当天 12:00 统一飞书提醒 - 扫描完成后立即发送汇报消息 ## 依赖 - `owa-outlook` skill（提供 `owa_calendar.py`） - `openclaw` CLI - Python 3.9+（需要 `zoneinfo` 模块） ## 安装后配置 ### 1. 注册每晚扫描 cron ```bash openclaw cron add \ --name "calendar-daily-scan" \ --cron "0 22 * * *" \ --tz "Asia/Shanghai" \ --session main \ --system-event "CALENDAR_SCAN: 请立即运行 python3 ~/.openclaw/workspace/skills/calendar-reminder/calendar_reminder.py 并等待完成" \ --description "每晚22:00扫描明天日历并设置提醒" ``` ### 2. 修改脚本中的飞书 open_id 编辑 `calendar_reminder.py`，将 `send_feishu` 函数中的 `target` 改为你自己的飞书 open_id： ```python "--target", "user:ou_xxxxxxxxxxxxxxxx", ``` ## 手动运行 ```bash python3 ~/.openclaw/workspace/skills/calendar-reminder/calendar_reminder.py ```


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