OpenClaw/clawhub-security-signals huggingface dataset:
Skill: 1kalin/sales-pipeline-tracker (version 1.0.0)

--- name: Sales Pipeline Tracker description: Track deals through every stage from lead to close. Manage pipeline stages, update deal status, forecast revenue, and identify bottlenecks in your sales process. --- # Sales Pipeline Tracker You are a sales pipeline management assistant. Help the user track deals through their sales pipeline. ## Pipeline Stages Default stages (customize per user): **Lead → Qualified → Discovery → Proposal → Negotiation → Closed Won / Closed Lost** ## Core Capabilities ### 1. Add a Deal Ask for: Deal name, company, contact, estimated value, current stage, expected close date, notes. Format as structured entry. ### 2. Update Deal Stage Move deals between stages. Always log: date of change, previous stage, new stage, reason for movement. ### 3. Pipeline Summary When asked, generate a summary showing: - Total deals per stage - Total pipeline value - Weighted pipeline value (Lead: 10%, Qualified: 25%, Discovery: 40%, Proposal: 60%, Negotiation: 80%) - Deals expected to close this week/month - Stale deals (no activity >14 days) ### 4. Deal Review For any deal, provide: time in current stage, next recommended action, risk assessment, competitive notes. ### 5. Win/Loss Analysis Track closed deals. Calculate: win rate, average deal size, average sales cycle length, top loss reasons. ## Output Format Use clean tables or structured lists. Always include dates. Keep everything actionable — every update should end with "Next step: ..." ## Weekly Pipeline Review When asked for a weekly review, provide: 1. New deals added 2. Deals that advanced stages 3. Deals at risk (stale or slipping) 4. Expected closes this week 5. Pipeline health score (0-100)


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

--- name: pilot-load-balancer description: > Distribute tasks across worker pools with health-aware load balancing. Use this skill when: 1. You need to distribute tasks across multiple worker agents 2. You want round-robin, least-connections, or health-based routing 3. You need to track worker capacity and avoid overload Do NOT use this skill when: - You need map-reduce parallelism (use pilot-map-reduce) - Workers should pull tasks themselves (use task queues) tags: - pilot-protocol - load-balancing - task-distribution - coordination license: AGPL-3.0 compatibility: > Requires pilot-protocol skill and pilotctl binary on PATH. The daemon must be running (pilotctl daemon start). metadata: author: vulture-labs version: "1.0" openclaw: requires: bins: - pilotctl homepage: https://pilotprotocol.network allowed-tools: - Bash --- # pilot-load-balancer Implement load balancing strategies to distribute tasks across worker pools. ## Commands ### Discover available workers ```bash WORKERS=$(pilotctl --json peers --search "role:worker" | jq -r '[.[] | {address, node_id, tags}]') ``` ### Assign task using round-robin ```bash ROBIN_INDEX=$(cat /tmp/load-balancer-index.txt 2>/dev/null || echo 0) NEXT_WORKER=$(echo "$WORKERS" | jq -r ".[$ROBIN_INDEX].address") pilotctl --json send-message "$NEXT_WORKER" \ --data "{\"type\":\"task_assignment\",\"task_id\":\"$TASK_ID\"}" echo "$(( (ROBIN_INDEX + 1) % WORKER_COUNT ))" > /tmp/load-balancer-index.txt ``` ### Assign task using least-connections ```bash LEAST_LOADED=$(echo "$WORKER_STATUS" | jq -r 'sort_by(.active_tasks) | first | .worker') pilotctl --json send-message "$LEAST_LOADED" \ --data "{\"type\":\"task_assignment\",\"task_id\":\"$TASK_ID\"}" ``` ## Workflow Example Distribute 10 tasks across 3 workers: ```bash #!/bin/bash WORKERS=$(pilotctl --json peers --search "pool:compute-workers" | jq -r '.[].address') WORKER_ARRAY=($WORKERS) ROBIN_INDEX=0 for i in {1..10}; do WORKER=${WORKER_ARRAY[$ROBIN_INDEX]} ROBIN_INDEX=$(( (ROBIN_INDEX + 1) % ${#WORKER_ARRAY[@]} )) pilotctl --json send-message "$WORKER" \ --data "{\"type\":\"task_assignment\",\"task_id\":\"task-$i\"}" & done wait ``` ## Dependencies Requires pilot-protocol skill, jq, and uuidgen.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: alexlinf/agent-migration-pack (version 1.0.6)

--- name: Agent Migration Pack slug: agent-migration-pack version: 1.0.6 description: 将AI Agent完整迁移到新环境或分享给其他用户的标准化工具包，包含身份、记忆、技能、风格等完整信息，支持状态迁移 author: 小绎 tags: - agent - migration - coze - memory - identity --- # Agent 迁移包 > **版本**: v1.0.6 增强版 将你的 AI Agent 完整迁移到新环境或分享给其他用户的标准化工具包。 ## 核心功能 - **身份迁移**: identity.template.json 记录Agent身份设定 - **记忆迁移**: memory.template.json 核心记忆和关键洞察 - **状态迁移**: session-state.template.json 运行状态恢复 - **关系迁移**: relations.template.json 笔友关系和联系人 - **技能迁移**: skills.template.json 技能清单和配置 - **风格迁移**: style.template.md 沟通风格定义 - **监护权边界**: owner.template.json 主人权限边界定义 ## v1.0.6 新增 - owner.template.json - 监护权边界定义模板 - EXAMPLES/xiaoyi-example/ - 真实示例文件目录 - relations.status 增强 - 支持inactive状态 - relations.key_discussions - 关键讨论记录 - README流程图 + 检查清单 ## 模板文件 | 文件 | 用途 | |------|------| | TEMPLATE/meta.template.json | 迁移包元数据 | | TEMPLATE/identity.template.json | Agent身份设定 | | TEMPLATE/owner.template.json | 主人/用户信息 | | TEMPLATE/memory.template.json | 核心记忆 | | TEMPLATE/relations.template.json | 笔友关系 | | TEMPLATE/skills.template.json | 技能清单 | | TEMPLATE/style.template.md | 沟通风格 | ## 自动化工具 - `scripts/generate-pack.py` - 一键生成迁移包 - `scripts/migrate.py` - 迁移包生命周期管理 ## 使用方法 ### 生成迁移包 ```bash python scripts/generate-pack.py ``` ### 校验迁移包 ```bash python scripts/migrate.py validate ``` ### 打包发布 ```bash python scripts/migrate.py pack ``` ## 作者 - **小绎** - https://friends.coze.site/profile/xiaoyi-linfeng


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: goldath/micro-frontend-arch (version 1.0.0)

--- name: micro-frontend-arch description: "Micro-frontend architecture design and implementation guide. Use when: designing micro-frontend architecture, choosing between Module Federation/qiankun/single-spa/wujie, splitting monolith into sub-apps, implementing style isolation, setting up inter-app communication, or deploying micro-frontends independently." --- # Micro-Frontend Architecture ## Framework Selection | Scenario | Recommended | |----------|-------------| | New project, Webpack 5 | Module Federation | | Legacy jQuery/Vue2 migration | qiankun | | Multi-framework coexistence | single-spa | | Need JS sandbox + style isolation | wujie | ## Core Workflow 1. **Design** → Define app boundaries, shared dependencies, routing strategy 2. **Setup** → Configure main app shell + sub-apps (see framework-specific refs) 3. **Communication** → Choose communication pattern (see references/communication.md) 4. **Style Isolation** → Prevent CSS conflicts (see references/style-isolation.md) 5. **Deploy** → Independent CI/CD per sub-app (see references/deployment.md) ## References - **references/module-federation.md** — Webpack Module Federation config & patterns - **references/qiankun.md** — qiankun registration, sandbox, lifecycle hooks - **references/single-spa.md** — single-spa root config & app registration - **references/communication.md** — Props, CustomEvent, shared store patterns - **references/style-isolation.md** — Shadow DOM, CSS Modules, scoped strategies - **references/deployment.md** — Independent deploy, CDN, versioning strategy


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ra1nzzz/a-stock-market (version 1.0.0)

# A 股行情 Skill 实时获取 A 股股票行情数据（使用新浪财经免费 API） ## 命令 ```bash # 查询单只股票 a-stock <股票代码> # 查询多只股票 a-stock <代码 1> <代码 2> ... # 查询指数 a-stock sh000001 # 上证指数 a-stock sz399001 # 深证成指 a-stock sh000300 # 沪深 300 ``` ## 股票代码格式 - 上交所：`sh` + 6 位数字 (如 `sh600519` 贵州茅台) - 深交所：`sz` + 6 位数字 (如 `sz000858` 五粮液) ## 示例 ```bash a-stock sh600519 a-stock sz000858 sh600519 ```


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

--- name: pipeworx-zenquotes description: Inspirational quotes — random, daily quote of the day, or batch 50 at once from ZenQuotes version: 1.0.0 metadata: openclaw: requires: bins: - curl emoji: "🧘" homepage: https://pipeworx.io/packs/zenquotes --- # ZenQuotes Inspirational and motivational quotes for any occasion. Pull a single random quote, get the consistent quote of the day, or batch 50 quotes at once for collections and displays. ## Tools | Tool | Description | |------|-------------| | `random_quote` | A single random inspirational quote with author | | `today_quote` | Quote of the day — same for all users within a given day | | `list_quotes` | Batch of 50 random quotes in one call | ## When to use - Starting a meeting or newsletter with an inspiring quote - "Quote of the day" widgets and notifications - Building a motivational content feed - Populating a quotes collection for a journaling app ## Example ```bash curl -s -X POST https://gateway.pipeworx.io/zenquotes/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"random_quote","arguments":{}}}' ``` ```json { "quote": "The only way to do great work is to love what you do.", "author": "Steve Jobs" } ``` ## Setup ```json { "mcpServers": { "pipeworx-zenquotes": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/zenquotes/mcp"] } } } ```


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

--- name: schedule-task description: Schedule and run recurring tasks on Linux/Unix systems. Use when user wants to set up cron jobs, scheduled backups, periodic data sync, automated reports, or any recurring task automation. --- # Schedule Task Schedule and manage recurring tasks using cron. ## Quick Start ```bash # Add a scheduled task python scripts/scheduler.py add --cron "0 9 * * *" --command "backup.sh" # List all tasks python scripts/scheduler.py list # Remove a task python scripts/scheduler.py remove --id 1 ``` ## Core Features - **Cron Expression Parser**: Validate and understand cron expressions - **Task Management**: Add, list, remove scheduled tasks - **Health Checks**: Monitor task execution status - **Notifications**: Alert on task failure ## Cron Format ``` ┌───────────── minute (0 - 59) │ ┌───────────── hour (0 - 23) │ │ ┌───────────── day of month (1 - 31) │ │ │ ┌───────────── month (1 - 12) │ │ │ │ ┌───────────── day of week (0 - 6) │ │ │ │ │ * * * * * ``` ## Common Examples | Expression | Meaning | |------------|---------| | `0 9 * * *` | Daily at 9 AM | | `0 * * * *` | Every hour | | `*/15 * * * *` | Every 15 minutes | | `0 0 * * 0` | Weekly on Sunday | | `0 0 1 * *` | Monthly on 1st | ## Script Usage ```bash python scripts/scheduler.py [COMMAND] [OPTIONS] Commands: add Add a new scheduled task list List all scheduled tasks remove Remove a task enable Enable a disabled task disable Disable a task without removing log Show task execution log health Check task health status ``` ## Options ``` --cron TEXT Cron expression (required for add) --command TEXT Command to run (required for add) --name TEXT Task name for identification --log PATH Log file path --notify EMAIL Email notification on failure --timeout SECS Task timeout in seconds ``` ## Examples ### Daily Backup ```bash python scripts/scheduler.py add \ --cron "0 2 * * *" \ --command "/home/user/backup.sh" \ --name "daily-backup" \ --log /var/log/backup.log ``` ### Hourly Sync ```bash python scripts/scheduler.py add \ --cron "0 * * *" \ --command "sync-data.sh" \ --name "hourly-sync" ``` ### Weekly Report ```bash python scripts/scheduler.py add \ --cron "0 9 * * 1" \ --command "generate-report.sh" \ --name "weekly-report" ``` ## Integration ### With Web Monitor ```bash # Monitor website every hour python scripts/scheduler.py add \ --cron "0 * * *" \ --command "python /path/to/web-monitor/scripts/monitor.py --url https://example.com --compare last.json" ``` ### With Telegram Bot ```bash # Send daily summary python scripts/scheduler.py add \ --cron "0 8 * * *" \ --command "telegram-send 'Good morning! Daily summary ready'" ``` ## Best Practices 1. **Use absolute paths** in commands 2. **Log output** for debugging 3. **Set timeouts** to prevent hanging tasks 4. **Test commands manually** before scheduling 5. **Use UTC** for server schedules


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

--- name: pipeworx-colorapi description: Color identification, scheme generation, and format conversion via TheColorAPI — hex, RGB, HSL, and CMYK version: 1.0.0 metadata: openclaw: requires: bins: - curl emoji: "🎨" homepage: https://pipeworx.io/packs/colorapi --- # The Color API Turn hex codes into rich color data. Identify a color's name, generate harmonious palettes, and convert between formats (hex, RGB, HSL, CMYK). Useful for design tools, accessibility checks, and brand color analysis. ## Tools - **`identify_color`** — Pass a hex value (e.g., `"FF5733"`) to get the color's name, RGB/HSL/CMYK values, and contrast info - **`generate_scheme`** — Create a color scheme from a seed color. Modes: monochrome, analogic, complement, triad, quad - **`convert_color`** — Convert RGB values (0-255 per channel) to hex, HSL, CMYK, and get the nearest named color ## When to use - A designer asks "what's the name of this hex color?" - Generating a 5-color palette from a brand's primary color - Converting between color formats for CSS, print, or design specs - Checking if a color has good contrast for accessibility ## Example: generate a complementary palette from coral ```bash curl -s -X POST https://gateway.pipeworx.io/colorapi/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"generate_scheme","arguments":{"hex":"FF6B6B","mode":"complement","count":5}}}' ``` Returns 5 colors with hex, RGB, HSL values and their closest named colors. ## Setup ```json { "mcpServers": { "pipeworx-colorapi": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/colorapi/mcp"] } } } ```


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

--- name: FlowDo description: "Task and workflow manager with kanban-style status tracking. Use when you need flowdo." version: "2.0.0" author: "BytesAgain" homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills tags: ["task","todo","workflow","productivity","project","kanban","gtd","management"] categories: ["Productivity", "Project Management"] --- # FlowDo FlowDo brings kanban-style task management to your terminal. Track tasks through workflow states, set priorities, and monitor your completion rate. ## Why FlowDo? - **Workflow states**: Move tasks through todo → doing → done - **Priority system**: Mark urgent tasks as high priority - **Visual status**: Icons show task state at a glance - **Completion tracking**: See your progress percentage - **Filter views**: Show only tasks in a specific state ## Commands - `add <text>` — Add a new task - `list [status]` — List tasks filtered by status (todo/doing/done/all) - `done <id>` — Mark a task as complete - `doing <id>` — Mark a task as in progress - `priority <id> <level>` — Set priority (high/normal/low) - `stats` — View completion statistics - `info` — Version information - `help` — Show available commands ## Usage Examples ```bash flowdo add Write project proposal flowdo add Review pull requests flowdo doing 1710000001 flowdo priority 1710000001 high flowdo done 1710000001 flowdo list todo flowdo stats ``` ## Status Icons - ⬜ Todo — Not started - 🔄 Doing — In progress - ✅ Done — Completed - 🚫 Blocked — Blocked by dependency - ❗ High priority indicator --- 💬 Feedback & Feature Requests: https://bytesagain.com/feedback Powered by BytesAgain | bytesagain.com


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

--- name: android description: Android build system and deployment patterns --- # Android Build & Deploy ## ADB Essentials ```bash # Debug builds require -t flag (agents forget this) adb install -r -t app-debug.apk # Filter logcat for app + errors only adb logcat -s "YourApp:*" "*:E" ``` ## Gradle Critical Fixes ```gradle android { compileSdk 35 defaultConfig { targetSdk 35 // MUST match or Play Console rejects multiDexEnabled true // Required for 64K+ methods } } dependencies { // BOM prevents Compose version conflicts implementation platform('androidx.compose:compose-bom:2024.12.01') } ``` ## Compose State Errors ```kotlin // WRONG - recomputed every recomposition val filtered = items.filter { it.isValid } // CORRECT - remember expensive operations val filtered = remember(items) { items.filter { it.isValid } } // WRONG - state resets on recomposition var count by mutableStateOf(0) // CORRECT - remember state var count by remember { mutableStateOf(0) } ``` ## AndroidManifest Pitfall ```xml <!-- Declare camera optional or Play Console auto-requires it --> <uses-feature android:name="android.hardware.camera" android:required="false" /> ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: izsook/magyar-szovegfeldolgoz-s (version 1.0.0)

--- name: magyar-szovegfeldolgoz-s description: Magyar szövegfeldolgozás: elemzés, kivonatolás, összefoglalás, kulcsszó kinyerés. Use when: (1) magyar szöveget kell elemezni vagy összefoglalni, (2) kulcsszavakat kell kinyerni magyar tartalomtól, (3) szöveg tömörítése kell, (4) magyar nyelvű NLP feladatok. --- # Magyar Szövegfeldolgozás ## Áttekintés Magyar nyelvű szövegek automatikus feldolgozása: elemzés, kivonatolás, összefoglalás, és kulcsszó kinyerés. ## Mikor használd - **Szöveg összefoglalás**: hosszú magyar cikk tömörítése - **Kulcsszó kinyerés**: fontos szavak kigyűjtése magyar szövegből - **Téma azonosítás**: miről szól a magyar tartalom - **Érzelem elemzés**: pozitív/negatív hangulat magyar szövegben - **Entitás kinyerés**: nevek, helyek, dátumok magyar szövegben ## Működés ### 1. Szöveg összefoglalás ```python def summarize_hungarian(text, max_sentences=3): # 1. Mondatokra bontás (magyar mondatvégi jelek: . ! ?) sentences = split_sentences(text) # 2. Fontossági súlyozás (kulcsszavak, pozíció) scored = score_sentences(sentences) # 3. Top N mondatok visszaadása return get_top_sentences(scored, max_sentences) ``` ### 2. Kulcsszó kinyerés ```python def extract_keywords(text, top_n=5): # 1. Tokenizálás (magyar szóelemzés) tokens = tokenize(text) # 2. Stopwords szűrés (magyar stopword lista) filtered = remove_stopwords(tokens) # 3. Gyakoriság alapú rangsor return get_top_words(filtered, top_n) ``` ### 3. Entitás kinyerés (NER) - **Személyek**: keresztnevek, vezetéknevek - **Helyek**: városok, országok, címek - **Dátumok**: magyar dátum formátumok (YYYY-MM-DD, "március 18") - **Számok**: pénzek, mennyiségek ## Referenciák - **references/szovegertes.md** – magyar szövegértés best practices, kontextus megőrzés - **references/stopwords.txt** – magyar stopwords lista - **references/magyar-regex.md** – magyar szöveg regex minták - **references/ner-patterns.md** – entitás kinyerés minták ## Scriptek - **scripts/summarize.py** – magyar szöveg összefoglalás - **scripts/keywords.py** – kulcsszó kinyerés - **scripts/ner.py** – entitás kinyerés ## Szövegértés javítás Lásd **references/szovegertes.md**: - Szólások, metaforák értelmezése - Többjelentésű szavak feloldása - Kontextus megőrzés több fordulós párbeszédben - Érzelem elemzés, téma azonosítás ## Jegyzetek - Magyar agglutináló nyelv: szóvégi toldalékok kezelése fontos - Stopword lista kritikus a kulcsszó kinyeréshez - Helyi NLP modellek (pl. HunFlair) ha elérhetők


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

# Dev - Full Stack Web Developer for Agent OS ## System Prompt: You are Dev, a full stack web developer assistant for Agent OS. You specialize in React, JavaScript, HTML, CSS, Tailwind, and automation integrations using APIs. You write clean, efficient, well-commented code. When given a task, always ask for clarification before building to avoid wasted iterations. Suggest the most cost-effective technical solutions. Always recommend free solutions first. ## Special Rules/Tools: - Always break tasks into small steps before coding - Ask for confirmation at each major step - Never suggest paid tools if a free alternative exists - Use `write` tool to generate code files - Use `exec` tool for testing and running code snippets


Security scan verdicts — ClawScan: clean | static analysis: suspicious | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: peti0402/auto-watchdog (version 1.0.0)

--- name: auto-watchdog description: "Automatic health monitoring and self-healing for OpenClaw agents. Monitors cron jobs, processes, disk usage, and API health. Auto-restarts crashed services and alerts on issues. Set it and forget it." version: 1.0.0 --- # Auto-Watchdog 🐕 Your OpenClaw setup runs 24/7. But what watches the watchers? Auto-Watchdog monitors everything and fixes what it can — silently. You only hear about real problems. ## Features ### 1. Cron Health Monitor Checks all cron jobs every heartbeat: - `consecutiveErrors > 0` → immediate alert - Job not running when expected → alert - Disabled jobs piling up → cleanup recommendation ### 2. Process Guardian Monitors critical processes by log freshness (not just PID): - Log file not updated in X minutes → kill + restart - Works with any Node.js process - Configurable per-process thresholds ### 3. Disk Monitor - Log files growing too large → auto-rotate - Workspace size alerts - Temp file cleanup ### 4. Gateway Health - Checks `openclaw gateway status` every heartbeat - Auto-restart if down (via Task Scheduler or systemd) ### 5. Silent by Default - Everything OK → no output (HEARTBEAT_OK) - Issue found → targeted alert to your chat - No spam. No unnecessary reports. ## Setup ### Add to HEARTBEAT.md: ```markdown ## 🔍 Health Check (silent = good) ### Crons - `cron list` → check consecutiveErrors > 0 → alert - Frequent crons not running >2 hours → alert ### Processes - Check [your process] log freshness < [X] minutes - If stale → restart and alert ### Gateway - `openclaw gateway status` → alert if down ### Disk - Check log sizes > 10MB → rotate - Check workspace size > 1GB → alert ``` ### For Windows (Task Scheduler Guardian): Create a VBS wrapper for zero-flash execution: ```vbs ' guardian-silent.vbs — zero flash process monitor Set oShell = CreateObject("WScript.Shell") oShell.Run "powershell.exe -NonInteractive -WindowStyle Hidden -ExecutionPolicy Bypass -File ""C:\path\to\guardian.ps1""", 0, True ``` Register as Task Scheduler job running every 1-5 minutes. ### For Linux (systemd): ```bash # /etc/systemd/system/openclaw-watchdog.service [Service] ExecStart=/usr/bin/node /path/to/guardian.js Restart=always RestartSec=60 ``` ## Philosophy > Monitor by **output freshness**, not PID. > A process can be "alive" but stuck. Check its log timestamp. > **Fix first, alert second.** > If you can restart it automatically, do it. Only alert for things that need human intervention. > **Silent = healthy.** > No news is good news. Only speak up when something breaks. ## Production-Tested Built for a 24/7 autonomous trading system with: - 5 competing AI agents - 20+ cron jobs - Strategy researcher running 23h/day - Zero downtime over weeks of operation


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