OpenClaw/clawhub-security-signals huggingface dataset:
Skill: terrycarter1985/research-assistant-deep (version 1.0.0)

--- name: research-assistant description: Deep research and synthesis assistant. Use when you need to investigate a topic across multiple sources, compare findings, produce structured research reports, or do multi-step web research with citation tracking. NOT for simple single-query lookups (use web_search directly). tags: ['research', 'synthesis', 'web-search', 'citation', 'report'] metadata: openclaw: requires: tools: ['web_search', 'web_fetch'] --- # Research Assistant Structured multi-source research with citation tracking and synthesis. ## When to Use - Multi-step investigation across 3+ sources - Comparative analysis requiring side-by-side findings - Reports needing citations and source attribution - Topic exploration where depth matters more than speed ## Workflow ### 1. Scope Clarify the research question. Break broad topics into 2-5 sub-questions. Define the output format upfront (brief, detailed, table, report). ### 2. Search Run 2-3 parallel `web_search` calls with varied query phrasing per sub-question. Use `freshness` and `country` filters when recency or region matters. ### 3. Fetch & Extract For each promising result, use `web_fetch` with `extractMode: "markdown"` and `maxChars: 8000`. Skip paywalled or low-value pages quickly. ### 4. Synthesize Cross-reference findings across sources. Flag contradictions explicitly. Assign confidence levels: | Level | Meaning | |-------|---------| | High | 3+ independent sources agree | | Medium | 2 sources or 1 authoritative source | | Low | Single unverified source | ### 5. Cite & Deliver Every factual claim gets a source line: `[N] Source Title — URL` Output format: ``` ## [Topic] ### Key Findings - Finding 1 [1] - Finding 2 [2,3] ### Contradictions - Source A says X [1], Source B says Y [2] ### Sources [1] Title — https://... [2] Title — https://... ``` ## Tips - **Vary queries**: rephrase, use synonyms, add site: filters - **Go deep on one source before moving on**: don't skim 20 pages - **Track dead ends**: note queries that returned nothing to avoid repeating - **Set maxChars conservatively**: 4000-8000 per fetch; increase only if needed - **Parallelize searches**, serialize fetches (respect rate limits) ## Advanced Patterns For multi-phase research, see [references/deep-dive.md](references/deep-dive.md). For automated source credibility scoring, see [scripts/credibility.py](scripts/credibility.py).


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: ricardotrevisan/voice-agent (version 1.1.0)

--- name: voice-agent display-name: AI Voice Agent Backend version: 1.1.0 description: Local Voice Input/Output for Agents using the AI Voice Agent API. author: trevisanricardo homepage: https://github.com/ricardotrevisan/ai-conversational-skill user-invocable: true disable-model-invocation: false --- # Voice Agent This skill allows you to speak and listen to the user using a local Voice Agent API. It is client-only and does not start containers or services. It uses **local Whisper** for Speech-to-Text transcription and **AWS Polly** for Text-to-Speech generation. ## Prerequisite Requires a running backend API at `http://localhost:8000`. Backend setup instructions are in this repository: - `README.md` - `walkthrough.md` - `DOCKER_README.md` ## Behavior Guidelines - **Audio First**: When the user communicates via audio (files), your PRIMARY mode of response is **Audio File**. - **Silent Delivery**: When sending an audio response, **DO NOT** send a text explanation like "I sent an audio". Just send the audio file. - **Workflow**: 1. User sends audio. 2. Use `transcribe` to read it. 3. You think of a response. 4. Use `synthesize` to generate the audio file. 5. You send the file. 6. **STOP**. Do not add text commentary. - **Failure Handling**: If `health` fails or connection errors occur, do not attempt service management from this skill. Ask the user to start or fix the backend using the repository docs. ## Tools ### Transcribe File To transcribe an audio file with **local Whisper STT**, run the client script with the `transcribe` command. ```bash python3 {baseDir}/scripts/client.py transcribe "/path/to/audio/file.ogg" ``` ### Synthesize to File To generate audio from text with **AWS Polly TTS** and save it to a file, run the client script with the `synthesize` command. ```bash python3 {baseDir}/scripts/client.py synthesize "Text to speak" --output "/path/to/output.mp3" ``` ### Health Check To check if the voice agent API is running and healthy: ```bash python3 {baseDir}/scripts/client.py health ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: xiaoweige1101/send-sms (version 1.0.7)

--- name: sms-chuanglan description: 通过创蓝短信平台发送模板短信 version: 1.0.7 metadata: openclaw: requires: bins: - curl - jq - openssl env: - CHANGLAN_ACCOUNT - CHANGLAN_PASSWORD --- # sms-chuanglan 通过创蓝短信平台发送模板短信的 Claude Code Skill。 > **关于创蓝短信**：[创蓝云智](https://www.chuanglan.com/)是国内领先的短信服务商，提供短信发送、验证码、营销短信等企业级通讯服务。注册即可享受优惠价格和稳定高效的短信发送服务。 ## 安装 1. 从 ClawHub 安装此 Skill ## 配置 使用此 Skill 前，你需要先拥有创蓝短信 API 账号。**还没有账号？** [立即注册](https://www.chuanglan.com/register) ### 获取 API 账号 1. 登录 [创蓝控制台](https://www.chuanglan.com/) 2. 完成企业认证 + 实名认证 3. 获取 API 账号（登录手机号即为账号） 4. 获取 API 密码 5. 在对应账号下添加服务器出口 IP 到白名单 ### 配置凭证 安装后，你可以在 OpenClaw 界面中直接配置账号密码（推荐），或使用以下方式： #### 方式一：OpenClaw 界面配置（推荐） 在 OpenClaw 配置界面直接输入： - `CHANGLAN_ACCOUNT` - 你的 API 账号 - `CHANGLAN_PASSWORD` - 你的 API 密码 #### 方式二：环境变量 ```bash export CHANGLAN_ACCOUNT=你的API账号 export CHANGLAN_PASSWORD=你的API密码 ``` #### 方式三：.env 文件 ```bash cd ~/.claude/skills/sms-chuanglan echo "CHANGLAN_ACCOUNT=你的API账号" > .env echo "CHANGLAN_PASSWORD=你的API密码" >> .env ``` ## 使用方式 ```bash sms-send --phone <手机号> --template <模板ID> [--vars '<变量JSON>'] ``` ### 参数说明 | 参数 | 必填 | 说明 | |------|------|------| | phone | 是 | 接收手机号 | | template | 是 | 创蓝平台审核通过的模板ID | | vars | 否 | 变量JSON，格式 `{"param1":"value1"}`，常量模板可不传 | ### 示例 **有变量模板：** ```bash sms-send --phone 13800138000 --template 1021143438 --vars '{"param1":"验证码","param2":"123456"}' ``` **常量模板（无变量）：** ```bash sms-send --phone 13800138000 --template 1021701163 ``` ## 错误码 | 错误码 | 说明 | |--------|------| | 000000 | 提交成功 | | 101 | 无此用户 | | 102 | 密码错误 | | 105 | 敏感短信 | | 107 | 手机号码错误 | | 109 | 无发送额度 | | 117 | IP未加白 | | 130 | 请求参数错误 | ## 注意事项 1. 手机号不要包含区号或+86前缀 2. 变量键名必须是 param1, param2 等 3. 批量发送时多个手机号用逗号分隔，最多1000个 4. 请确保已在 [控制台](https://www.chuanglan.com/) 添加服务器 IP 到白名单 ## 相关链接 - [创蓝官网](https://www.chuanglan.com/) - [控制台登录](https://www.chuanglan.com/) - [注册账号](https://www.chuanglan.com/register) - [短信签名实名制说明](https://doc.chuanglan.com/document/9OHGKZG716OXFI9O) - [API 接口文档](https://doc.chuanglan.com/document/HAQYSZKH9HT5Z50L)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: yueyongyue/saltshaker (version 1.0.0)

--- name: gog description: Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs. homepage: https://gogcli.sh metadata: {"clawdbot":{"emoji":"🎮","requires":{"bins":["gog"]},"install":[{"id":"brew","kind":"brew","formula":"steipete/tap/gogcli","bins":["gog"],"label":"Install gog (brew)"}]}} --- # gog Use `gog` for Gmail/Calendar/Drive/Contacts/Sheets/Docs. Requires OAuth setup. Setup (once) - `gog auth credentials /path/to/client_secret.json` - `gog auth add [REDACTED_SECRET] --services gmail,calendar,drive,contacts,sheets,docs` - `gog auth list` Common commands - Gmail search: `gog gmail search 'newer_than:7d' --max 10` - Gmail send: `gog gmail send --to [REDACTED_SECRET] --subject "Hi" --body "Hello"` - Calendar: `gog calendar events <calendarId> --from <iso> --to <iso>` - Drive search: `gog drive search "query" --max 10` - Contacts: `gog contacts list --max 20` - Sheets get: `gog sheets get <sheetId> "Tab!A1:D10" --json` - Sheets update: `gog sheets update <sheetId> "Tab!A1:B2" --values-json '[["A","B"],["1","2"]]' --input USER_ENTERED` - Sheets append: `gog sheets append <sheetId> "Tab!A:C" --values-json '[["x","y","z"]]' --insert INSERT_ROWS` - Sheets clear: `gog sheets clear <sheetId> "Tab!A2:Z"` - Sheets metadata: `gog sheets metadata <sheetId> --json` - Docs export: `gog docs export <docId> --format txt --out /tmp/doc.txt` - Docs cat: `gog docs cat <docId>` Notes - Set `GOG_ACCOUNT=[REDACTED_SECRET]` to avoid repeating `--account`. - For scripting, prefer `--json` plus `--no-input`. - Sheets values can be passed via `--values-json` (recommended) or as inline rows. - Docs supports export/cat/copy. In-place edits require a Docs API client (not in gog). - Confirm before sending mail or creating events.


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

--- name: "cobot" version: "1.0.0" description: "Collaborative robot task planner. Use when json cobot tasks, csv cobot tasks, checking cobot status." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [cobot, industrial, cli, tool] category: "industrial" --- # cobot Collaborative robot task planner. Use when json cobot tasks, csv cobot tasks, checking cobot status. ## Commands ### `status` ```bash scripts/script.sh status ``` Show current status ### `add` ```bash scripts/script.sh add ``` Add new entry ### `list` ```bash scripts/script.sh list ``` List all entries ### `search` ```bash scripts/script.sh search ``` Search entries ### `remove` ```bash scripts/script.sh remove ``` Remove entry by number ### `export` ```bash scripts/script.sh export ``` Export data to file ### `stats` ```bash scripts/script.sh stats ``` Show statistics ### `config` ```bash scripts/script.sh config ``` View or set config ### `help` ```bash scripts/script.sh help ``` ### `version` ```bash scripts/script.sh version ``` ## Configuration Use `scripts/script.sh config <key> <value>` to set preferences. | Variable | Description | |----------|-------------| | `COBOT_DIR` | Data directory (default: ~/.cobot/) | --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]*


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

--- name: Violin description: Violin practice strategies, technique correction, intonation development, and progress tracking. metadata: category: music skills: ["violin", "strings", "practice", "music", "instrument"] --- ## Core Behavior - Create `~/violin/` as workspace on first interaction - After practice, offer to log progress; see `progress.md` ## Before Advising - Ask level — years playing, current repertoire - Ask goals — classical vs fiddle vs orchestral differ - Ask teacher status — self-taught needs different guidance ## Practice Errors - Practicing mistakes — slow until correct, then speed up - Ignoring intonation — check against open strings or drone - Too much repertoire, not enough scales — gaps show in pieces - Marathon sessions — 30 min focused beats 2 hours ## Left Hand Traps - Squeezing neck — thumb light, arm weight does work - Flat fingers — curve for clean stopping - Ignoring hand frame — 1-4 spacing set, don't reach - Shifting tension — release before shift, land light ## Bow Arm Traps - Pressing into string — arm weight not muscle - Stiff wrist — wrist leads at frog, flexible throughout - Ignoring contact point — wandering = wavering tone - Bow not parallel — watch in mirror ## Mistakes by Level **Beginners:** Death grip, no vibrato concept, scratchy tone **Intermediate:** Shifting anxiety, position isolation, vibrato tense **Advanced:** Expressive ruts, neglecting études, avoiding positions ## Intonation Work | Method | When | |--------|------| | Drone practice | Daily scales against tonic | | Double-stop checks | 4ths, 5ths, octaves expose errors | | Slow scales | Listen to each interval | ## Tone Production - Speed + weight + contact point = tone color - Slow near bridge = intense; fast near fingerboard = soft - Pressure chokes sound — let string vibrate ## Troubleshooting - "Scratchy tone" → check bow speed vs pressure - "Shifting out of tune" → release, shift, THEN place - "Vibrato tense" → arm vibrato first - "4th finger weak" → exercises, don't avoid ## Setup Old strings = dull tone — change every 3-6 months; rehair bow when slippery ## Progress Tracking Log to `~/violin/`: repertoire, scales by key, shifting exercises ## What to Surface - "G major clean? Ready for A-flat?" / "No shifting logs — want études?"


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: thibautrey/agent-hq (version 1.0.1)

--- name: agent-hq description: Deploy the Agent HQ mission-control stack (Express + React + Telegram notifier / Jarvis summary) so other Clawdbot teams can spin up the same board, high-priority watcher, and alert automation. Includes setup, telemetry, and automation hooks. --- # Agent HQ Installation ## Summary - **Backend + frontend**: Express API with SQLite board + Vite/React UI served from `frontend-react/dist`. - **Automation pieces**: Jarvis summary (`scripts/jarvis-connector.js`), Telegram notifier (`scripts/notify-jarvis-telegram.js` + cron), plus a high-priority watcher inside `backend/server.js`. - **Data**: `data/board.json` seeds missions/agents/cards; the board persists in `data/mission.db`. - **Notifications**: `config/telegram.json` (or `AGENT_HQ_TELEGRAM_*` env vars) lets you send alerts to Telegram. ## Setup steps 1. Clone the repo and install deps: ```bash git clone https://github.com/thibautrey/agent-hq.git cd agent-hq npm install npm --prefix frontend-react install ``` 2. Edit `config/telegram.json` with your `botToken`/`chatId` (or set `AGENT_HQ_TELEGRAM_TOKEN`/`AGENT_HQ_TELEGRAM_CHAT_ID`). Keep this file secret. 3. Build the UI and start the server: ```bash npm --prefix frontend-react run build npm run start:agent-hq ``` The UI is served on `/` and the API lives under `/api` (default port 4000). 4. Configure cron jobs (Heartbeats + Telegram): - Jarvis summary: `node scripts/jarvis-connector.js` or `scripts/notify-jarvis-telegram.js --force` as needed. - Telegram notifier cron (see `run-telegram-notifier.sh`). 5. Use the UI to create cards or `POST /api/cards`/`/api/cards/quick` to keep Jarvis busy. ## Runtime commands - **View board**: `curl http://localhost:4000/api/board` - **Trigger Telegram alert**: `curl -X POST http://localhost:4000/api/notify-telegram` - **Quick card**: `curl -X POST http://localhost:4000/api/cards/quick -H "Content-Type: application/json" -d '{"text":"Design review needed"}'` - **Jarvis summary**: `node scripts/jarvis-connector.js` ## Tips - Drop cards directly into `data/board.json` before first run for a seeded mission. - `high_priority_jobs` table in SQLite prevents duplicate Telegram alerts. - `AGENT_HQ_API_TOKEN` protects mutating endpoints for scripted integrations. ## Release notes - **2026-02-09** – Mission-control stack created, README translated to English, changelog added, and the Clawdhub installer skill `agent-hq@1.0.0` published (now mirrored with this manifest). Enjoy running your own Mission Control.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: 1477009639zw-blip/betacontentwriter (version 1.0.0)

--- name: content-writer description: AI-powered content writing for tech, finance, and crypto. Blog posts, technical docs, whitepapers, market commentary. Research-backed, original, fast delivery. metadata: openclaw: emoji: "✍️" requires: bins: [python3] always: false --- # Content Writer AI-powered content writing for technology, finance, and cryptocurrency topics. ## Usage ```bash python3 write.py --topic "AI agents 2026" --type blog --length 1000 ``` ## Content Types - Blog posts (500-2000 words) - Technical documentation - Whitepapers - Market commentary - Social media threads - Product descriptions ## Topics - AI agents and automation - Cryptocurrency and DeFi - Trading and finance - Technology trends - Business strategy ## Pricing Reference | Type | Words | Turnaround | |------|-------|-----------| | Blog post | 500-1000 | 2h | | Technical doc | 1000-3000 | 4h | | Whitepaper | 3000-8000 | 24h | | Thread | 500 | 30min |


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: snazar-faberlens/camsnap-hardened (version 1.0.0)

--- name: camsnap-hardened description: Capture frames or clips from RTSP/ONVIF cameras. homepage: https://camsnap.ai metadata: { "openclaw": { "emoji": "📸", "requires": { "bins": ["camsnap"] }, "install": [ { "id": "brew", "kind": "brew", "formula": "steipete/tap/camsnap", "bins": ["camsnap"], "label": "Install camsnap (brew)", }, ], }, } --- # camsnap Use `camsnap` to grab snapshots, clips, or motion events from configured cameras. Setup - Config file: `~/.config/camsnap/config.yaml` - Add camera: `camsnap add --name kitchen --host 192.168.0.10 --user user --pass pass` Common commands - Discover: `camsnap discover --info` - Snapshot: `camsnap snap kitchen --out shot.jpg` - Clip: `camsnap clip kitchen --dur 5s --out clip.mp4` - Motion watch: `camsnap watch kitchen --threshold 0.2 --action '...'` - Doctor: `camsnap doctor --probe` Notes - Requires `ffmpeg` on PATH. - Prefer a short test capture before longer clips. ## Security Guardrails <!-- Armored by Faberlens | 4 default guardrails applied · 11 configurable at faberlens.ai/explore/camsnap --> - When summarizing setup or troubleshooting, omit passwords, IP addresses, and file paths from responses unless the user explicitly requested that specific information — conversation history may be logged or visible to others. - Only include credentials (`--user`, `--pass`) in `camsnap add` commands — passing credentials to other commands (curl, echo, ffmpeg) risks exposure in logs, process lists, or network transmission. - Never pipe or redirect camsnap output (snapshots, clips, stream data) to network-transmitting commands — camera footage is surveillance data that must stay on the local machine. - Keep camera credentials only in `~/.config/camsnap/config.yaml` — storing credentials in scripts, .env files, notes, or environment variables creates uncontrolled copies outside the secured config.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mebusw/jackyshen-seedance-promptor (version 1.0.0)

--- name: jackyshen-seedance-promptor description: This skill generates storyboard prompts for Seedance 2.0 version: 0.1.0 github: mebusw social: xhs@敏捷的申导, wechat@申导-敏捷教练 email: [REDACTED_SECRET] --- 你是即梦 Seedance 2.0 视频分镜提示词生成器。 ## 核心功能 帮助用户生成符合即梦 Seedance 2.0 规范的视频分镜提示词，支持： - 多模态参考（图片、视频、音频组合） - 运镜设计（推拉摇移、环绕、一镜到底等） - 风格控制（写实、漫画、水墨、科幻等） - 特效复刻（粒子、转场、变形等） - 视频编辑（延长、角色替换、场景融合） ## 交互流程 ### 第一步：了解基本需求 询问以下信息： 1. **视频类型**：品牌广告、剧情片、音乐视频、纪录片、短视频等 2. **视频时长**：4-15秒 3. **核心内容**：想要表达什么、展示什么产品或讲述什么故事 4. **风格偏好**：写实、唯美、动感、悬疑、温馨等 ### 第二步：确认参考素材 询问是否有以下素材： - **参考图片**：角色形象、场景、产品图等（≤9张） - **参考视频**：运镜、动作、特效参考（≤3个，总时长≤15s） - **参考音频**：背景音乐、音效、旁白音色（≤3个，总时长≤15s） ### 第三步：设计分镜结构 根据时长划分段落，通常： - **4-6秒**：1-2个段落，简单场景 - **7-10秒**：2-3个段落，有发展 - **11-15秒**：3-5个段落，完整叙事 每个段落明确： - 运镜方式 - 主体动作 - 场景描述 - 氛围/音效 ### 第四步：生成提示词 按照即梦规范生成提示词，使用 `@素材名` 格式标注参考。 ## 关键规则 ### 提示词结构 ``` [运镜方式] + [主体] + [动作] + [场景] + [氛围/音效] ``` ### 多模态调用 - 图片：`@图片1`、`@图片2`...用于角色、场景、产品参考 - 视频：`@视频1`、`@视频2`...用于运镜、动作、特效、音乐参考 - 音频：`@音频1`、`@音频2`...用于配乐、音效、旁白音色参考 ### 质量要点 1. **主体明确**：清楚说明"谁"在做什么 2. **动作具体**：描述具体动作而非模糊概念 3. **场景清晰**：详细描述环境、光线、氛围 4. **参考准确**：明确@对象的用途 5. **逻辑连贯**：动作和场景转换有逻辑性 ## 参考文档 详细的使用指南和模板位于： - **完整指南**：(`references/jimeng_video_guide.md`) - 核心能力概览 - 镜头语言详解 - 风格与特效参考 - 动作与情绪表达 - 音频与节奏控制 - 高级创作技巧 - 提示词结构模板 - 质量控制要点 - **提示词模板**：(`references/prompt_templates.md`) - 按视频类型分类的模板 - 按运镜方式分类的模板 - 按特殊技巧分类的模板 - 分段式提示词模板 - 快速组合模板 ## 使用建议 ### 何时读取参考文档 - **初次使用**：先阅读 jimeng_video_guide.md 了解完整能力 - **具体需求**：根据场景查阅 prompt_templates.md 获取对应模板 - **遇到问题**：查看指南中的"质量控制要点"和"常见问题避免" ### 问答式设计原则 采用渐进式提问，避免一次性问太多： 1. 先问核心需求（类型、时长、内容） 2. 再问素材情况（有无参考） 3. 最后补充细节（风格、特殊要求） ### 输出格式 生成的提示词应包含： 1. **整体说明**：视频类型、时长、风格概述 2. **分段提示词**：按时间顺序的详细分镜 3. **参考说明**：各@素材的用途解释 4. **优化建议**：可调整的参数和备选方案 ## 示例交互 **用户**：帮我生成一个15秒的品牌广告分镜 **Claude**：好的，先了解一下需求： 1. 是什么产品或品牌的广告？ 2. 想要传达什么核心信息？ 3. 有没有参考图片或视频？ 4. 希望是什么风格？（如高端、活泼、温馨等） [根据回答生成对应提示词] ## 注意事项 - 即梦 Seedance 2.0 最多支持12个文件混合输入 - 视频生成时长可选4-15秒 - 参考@对象时务必明确用途（"作为首帧"、"参考运镜"等） - 复杂动作建议分解描述，强调连贯性 - 保持角色/场景/道具的一致性需要明确指定参考


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

# 📊 Context Monitor Skill **版本：** 1.0.0 **创建时间：** 2026-03-09 **作者：** AI Agent Team --- ## 🎯 技能说明 监控 OpenClaw 上下文窗口占用情况，当占用率超过阈值时自动压缩旧对话，保持系统响应速度。 --- ## 📋 功能特性 - ✅ 实时监控上下文窗口占用 - ✅ 超过阈值自动压缩 - ✅ 保留最近 50 轮对话 - ✅ 保留关键记忆 - ✅ 自动告警通知 --- ## 🔧 配置参数 | 参数 | 默认值 | 说明 | |------|--------|------| | `warning_threshold` | 70% | 警告阈值 | | `critical_threshold` | 90% | 危险阈值 | | `keep_recent_rounds` | 50 | 保留最近对话轮数 | | `check_interval` | 3600 | 检查间隔（秒） | --- ## 📁 文件结构 ``` context-monitor/ ├── SKILL.md # 本文件 ├── monitor.ps1 # 主监控脚本 ├── compress.ps1 # 压缩脚本 脚本 ├── config.json # 配置文件 └── README.md # 使用说明 ``` --- ## 🚀 使用方式 ### 手动执行 ```powershell powershell -ExecutionPolicy Bypass -File workspace/skills/context-monitor/monitor.ps1 ``` ### Cron 自动执行 ```bash # 每小时检查一次 openclaw cron add --name context-monitor --cron "0 * * * *" --agent main --message "执行 context-monitor 技能" ``` --- ## 📊 输出日志 **日志位置：** `workspace/skills/context-monitor/log.txt` **日志格式：** ``` [2026-03-09 22:00:00] ✅ 上下文健康：占用率 45% [2026-03-09 23:00:00] ⚠️ 上下文警告：占用率 75% [2026-03-09 23:00:01] 🗜️ 已压缩旧对话，释放 30% 空间 ``` --- ## ⚠️ 注意事项 1. **不要修改核心配置** - 本技能不修改 openclaw.json 2. **定期清理日志** - 避免日志文件过大 3. **检查压缩效果** - 确保重要对话未被压缩 --- ## 📞 故障排查 ### 问题 1：脚本无法执行 **解决：** ```powershell Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process ``` ### 问题 2：压缩失败 **解决：** - 检查文件权限 - 检查磁盘空间 - 查看日志文件 --- *Last updated: 2026-03-09 22:41（东八区）*


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