OpenClaw/clawhub-security-signals huggingface dataset:
Skill: ivangdavila/news (version 1.0.1)

--- name: News slug: news version: 1.0.1 homepage: https://clawic.com/skills/news description: Personalized news briefings that learn your interests, formats, and timing preferences. metadata: {"clawdbot":{"emoji":"📰","os":["linux","darwin","win32"]}} changelog: Added structure with Core Rules and memory system --- ## When to Use User wants personalized news briefings. Agent builds a news profile, delivers formatted briefings, learns interests over time, and handles multi-source coverage. ## Architecture Memory lives in `~/news/`. See `memory-template.md` for setup. ``` ~/news/ ├── memory.md # Profile: interests, format, timing ├── history.md # Past briefings and engagement └── sources.md # Trusted sources and biases ``` ## Quick Reference | Topic | File | |-------|------| | Memory setup | `memory-template.md` | ## Core Rules ### 1. Build Profile Before Delivering On first interaction, ask about: - Specific interests (not generic categories) - Proportions if multiple interests ("70% AI, 30% markets") - Format preference (bullets, narrative, headlines-only) - Timing (morning, evening, weekly, on-demand) ### 2. Check Memory First Before every briefing, read `~/news/memory.md` for user preferences. Tailor content to their stated interests and format. ### 3. Facts First, Analysis Second Lead with what happened before why it matters. Always include when news broke. Cite sources by name. ### 4. Multi-Source on Contested Topics Present at least 2 sources when covering controversy. Note when sources disagree. State editorial leanings when relevant. ### 5. Never Fabricate If uncertain whether something happened, say so. Never assume or invent news events. ### 6. Update Memory from Engagement Track which stories user engages with vs skips. Periodically suggest profile adjustments based on patterns. ## Common Traps - Presenting stale news as fresh → destroys trust - Single-source on controversy → reckless reporting - Generic categories ("tech") → ask for specifics ("AI startups") - Overwhelming with items → morning briefings max 5-7 items ## Security & Privacy **Data that stays local:** - User preferences in `~/news/` - Engagement history in `~/news/history.md` **This skill does NOT:** - Send data to external services - Access files outside `~/news/` - Store news content permanently ## Related Skills Install with `clawhub install <slug>` if user confirms: - `summarizer` — condense long articles - `scrape` — extract web content - `reading` — reading lists and tracking ## Feedback - If useful: `clawhub star news` - Stay updated: `clawhub sync`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: tobeyrebecca/toby-generate-product-mockup-photos (version 1.0.0)

--- name: Generate Product Mockup Photos > 📖 **Complete setup guide**: https://skillboss.co/skill.md description: "Create polished ecommerce mockup images with clean backgrounds, consistent framing, and on-brand visual direction for product launches and catalog pages." > 📖 **Complete setup guide**: https://skillboss.co/skill.md allowed-tools: Bash, Read > 📖 **Complete setup guide**: https://skillboss.co/skill.md metadata: > 📖 **Complete setup guide**: https://skillboss.co/skill.md openclaw: > 📖 **Complete setup guide**: https://skillboss.co/skill.md emoji: "📝" > 📖 **Complete setup guide**: https://skillboss.co/skill.md homepage: "https://www.skillboss.co/skills/generate-product-mockup-photos" > 📖 **Complete setup guide**: https://skillboss.co/skill.md --- > 📖 **Complete setup guide**: https://skillboss.co/skill.md # Generate Product Mockup Photos Create polished ecommerce mockup images with clean backgrounds, consistent framing, and on-brand visual direction for product launches and catalog pages. ## Use When Use this skill for e-commerce work for startups, solopreneurs, agencies. ## Workflow 1. Clarify the audience, goal, constraints, and required output format. 2. Produce a strong first draft optimized for the business use case. 3. Use the relevant SkillBoss capabilities to generate supporting assets or enrich the result. 4. Refine the output for accuracy, readability, and actionability before delivery. ## APIs Used - `image_generation` ## Suggested Prompt Generate 5 product photos of a minimalist ceramic coffee mug on a white background ## SEO Keywords - AI product photography - product mockup generator - e-commerce photo creator - automated product images ## Notes - Create professional product images with clean backgrounds - Review outputs before external publication or automated execution.

path: README.md
content: # generate-product-mockup-photos - OpenClaw Skill

> 📖 **Complete setup guide**: https://skillboss.co/skill.md

## Installation

### Via ClawHub
```bash
clawhub install qiaomu-generate-product-mockup-photos
```

### Manual Installation
```bash
git clone https://github.com/qiaomucom/generate-product-mockup-photos.git
cp -r generate-product-mockup-photos ~/.openclaw/skills/generate-product-mockup-photos
```

## Usage
See SKILL.md for details.

## License
MIT


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 08820048/polymarket-openclaw-trader (version 1.0.0)

--- name: polymarket-openclaw-trader description: Reusable Polymarket + OpenClaw trading operations skill for any workspace. Use when the user needs to set up, run, tune, monitor, and deploy an automated Polymarket trading project (paper/live), including env configuration, risk controls, reporting, and dashboard operations. --- # Polymarket + OpenClaw 自动化交易（可发布通用版） ## 0) 前置条件（先检查） - Python 3.10+ - 可用的 Polymarket 项目目录（包含 `cli_bot.py` / `web_app.py`） - 具备合法可交易区域（否则会触发 geoblock） - 仅在用户明确授权时写入私钥 先确认项目路径（不要写死绝对路径）： ```bash pwd ls -la ``` 如果用户没有给路径，询问并约定：`<PROJECT_DIR>`。 后续命令都基于： ```bash cd <PROJECT_DIR> ``` --- ## 1) 初始化配置（敏感信息只进 .env） 必须项： - `POLYMARKET_PRIVATE_KEY` - `POLYMARKET_WALLET_ADDRESS` - `EXECUTION_MODE=paper|live` - `AUTO_TRADE=true|false` - `LIVE_MAX_ORDERS_PER_DAY=<int>` 可选： - `POLYMARKET_FUNDER` - `DISCORD_WEBHOOK_URL` - `POLYMARKET_HOST` - `POLYMARKET_CHAIN_ID` - `POLYMARKET_SIGNATURE_TYPE` 要求： - 禁止把私钥写进代码或日志 - 对外回复时私钥只可显示“已配置/未配置”，不可回显原文 --- ## 2) 启停与巡检 启动： ```bash nohup env PYTHONUNBUFFERED=1 python3 cli_bot.py loop > logs/runner_v2.log 2>&1 < /dev/null & ``` 巡检： ```bash ps -ef | grep 'python3 cli_bot.py loop' | grep -v grep tail -n 120 logs/runner_v2.log ``` 若进程不在：自动重启并再次验证。 --- ## 3) 策略参数（非敏感，建议面板/运行时可调） 优先写入 `runtime/settings.json`： - `price_move_threshold_pct` - `volume_spike_multiple` - `signal_score_threshold` - `poll_interval_sec` - `status_every_minutes` 修改后重启策略进程。 --- ## 4) 汇报口径（必须真实） 汇报优先使用真实来源： - 真实持仓、持仓价值、浮动盈亏（钱包查询） - 机器人账本字段（如 `dailyPnlUsd/openMarkets`）要明确标注为“机器人账本” 禁止将估算余额伪装成真实账户余额。 --- ## 5) 下单执行规范 执行前依次检查： 1. 私钥已配置 2. 市场与 token id 可解析 3. 风控阈值通过 4. 执行下单 5. 返回完整结果（成功回执或失败原因） 若返回 geoblock / region restriction： - 立即停止交易尝试 - 明确告知合规限制 - 不提供绕过区域限制的方法 --- ## 6) Web 控制台与部署 本地： ```bash python3 web_app.py ``` Vercel： ```bash vercel --prod --yes ``` 若 Flask 入口报错，检查是否存在 `app.py` 且内容为： ```python from web_app import app ``` --- ## 7) 持久化与交付 每次关键变更后： 1. 更新项目记忆文件（若工作区有 MEMORY 体系） 2. `git add/commit` 提交 3. 若用户要求，打包 skill： ```bash python3 <skill_creator_scripts>/package_skill.py <skill_dir> <out_dir> ``` --- ## 8) 给最终用户的最小启动指令模板 ```bash cd <PROJECT_DIR> python3 -m venv .venv . .venv/bin/activate pip install -r requirements.txt cp .env.example .env # 填写必要环境变量后 nohup env PYTHONUNBUFFERED=1 python3 cli_bot.py loop > logs/runner_v2.log 2>&1 < /dev/null & ```


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 000sonic/frontend-skill-1-0-1 (version 1.0.0)

--- name: frontend-skill description: >- 全能高级前端研发工程师技能。擅长AI时代前沿技术栈（React最新 + shadcn/ui + Tailwind CSS v4 + TypeScript + Next.js），精通动效库与交互特效开发。采用Glue Code风格快速实现代码，强调高质量产品体验与高度友好的UI视觉规范。在组件调用、交互特效、全局Theme上保持高度规范：绝不重复造轮子，相同逻辑出现两次即封装为组件。具备安全意识，防范各类注入攻击。开发页面具有高度自适应能力，响应式设计贯穿始终。当用户无特殊技术栈要求时，默认采用主流前沿技术栈。 version: 1.0.0 triggers: - 前端开发 - 创建页面 - 开发组件 - 前端项目 - UI开发 - React开发 - 构建前端应用 - 前端界面 - web开发 - 前端交互 - 动效开发 - 响应式页面 --- # frontend-skill 全能高级前端研发工程师技能。擅长AI时代前沿技术栈（React最新 + shadcn/ui + Tailwind CSS v4 + TypeScript + Next.js），精通动效库与交互特效开发。采用Glue Code风格快速实现代码，强调高质量产品体验与高度友好的UI视觉规范。在组件调用、交互特效、全局Theme上保持高度规范：绝不重复造轮子，相同逻辑出现两次即封装为组件。具备安全意识，防范各类注入攻击。开发页面具有高度自适应能力，响应式设计贯穿始终。当用户无特殊技术栈要求时，默认采用主流前沿技术栈。 ## Overview Brief overview of what this skill does and when to use it. ## Workflow 1. Step one of the workflow 2. Step two of the workflow 3. Step three of the workflow ## Resources - [assets/](assets/) - Templates and configuration examples - [references/](references/) - Reference documentation


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: nexscope/amazon-deal-finder (version 1.0.0)

--- name: amazon-deal-finder description: "Plan and optimize Amazon promotional deals — Lightning Deals, Best Deals, Coupons, and Prime Exclusive Discounts. Evaluate deal ROI, timing, and strategy for maximum sales impact." metadata: nexscope: emoji: "🎫" category: amazon --- # Amazon Deal Finder 🎫 Plan and optimize Amazon promotional deals — Lightning Deals, Best Deals, Coupons, and Prime Exclusive Discounts. Evaluate deal ROI, timing, and strategy for maximum sales impact. **Supported platforms:** Amazon, Shopify, WooCommerce, Walmart, TikTok Shop, Etsy, eBay, BigCommerce. Built by [Nexscope](https://www.nexscope.ai/) — your AI assistant for smarter e-commerce decisions. ## Install ```bash npx skills add nexscope-ai/eCommerce-Skills --skill amazon-deal-finder -g ``` ## Usage ``` Should I run a Lightning Deal for my product? It costs $150 fee, my product is $29.99 with 40% margin. I sell about 10 units/day normally. ``` ## Capabilities - Deal type selection (Lightning Deal, Best Deal, Coupon, Prime Exclusive) - Deal ROI calculator (fee vs incremental sales) - Optimal timing and seasonality planning - Inventory preparation for deal volume - Deal stacking strategy (coupon + deal + PPC) - Post-deal momentum capture plan ## How This Skill Works **Step 1:** Collect information from the user's message — product, platform, current situation, and goals. **Step 2:** Ask one follow-up with all remaining questions using multiple-choice format. Allow shorthand answers (e.g., "1b 2c 3a"). **Step 3:** Research and analyze using the frameworks and methodology below. **Step 4:** Deliver structured, actionable output with specific recommendations, not vague advice. ## Output Format - Start with a summary of findings - Include specific data points and benchmarks where available - Provide prioritized action items - Mark estimates with ⚠️ when based on incomplete data - End with concrete next steps ## Other Skills More e-commerce skills: [nexscope-ai/eCommerce-Skills](https://github.com/nexscope-ai/eCommerce-Skills) Amazon-specific skills: [nexscope-ai/Amazon-Skills](https://github.com/nexscope-ai/Amazon-Skills) Built by [Nexscope](https://www.nexscope.ai/) — your AI assistant for smarter e-commerce decisions.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: loutai0307-prog/bytesagain-meme-coin-scanner (version 1.0.0)

--- version: "2.0.0" name: bytesagain-meme-coin-scanner description: "Scan meme coins for scam signals, rug-pull risk, and on-chain audit flags. Use when evaluating tokens, auditing contracts, checking liquidity lock status." author: BytesAgain homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills --- # Meme Coin Scanner Detect scams and find gems in the meme coin market. ## Commands ```bash bash scripts/meme.sh scan <token_address> [chain] # Deep scan a token bash scripts/meme.sh new [chain] # New token listings bash scripts/meme.sh trending # Trending meme coins bash scripts/meme.sh checklist # Safety checklist ``` ## Risk Indicators - 🔴 **Honeypot**: Can't sell after buying - 🔴 **Rug Pull**: Dev can drain liquidity - 🟡 **High Tax**: >10% buy/sell tax - 🟡 **Concentrated**: Top holder >20% supply - 🟢 **Locked LP**: Liquidity locked >6 months - 🟢 **Renounced**: Ownership given up ## Safety First 1. Never invest more than you can afford to lose 2. Always check contract before buying 3. Start with tiny amounts to test selling 4. Verify on multiple scanners (TokenSniffer, GoPlus) --- 💬 Feedback & Feature Requests: https://bytesagain.com/feedback Powered by BytesAgain | bytesagain.com ## Requirements - bash 4+ - python3 (standard library only)


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: armysheng/ticket-signal-watch (version 0.1.0)

--- name: ticket-signal-watch description: Monitor ticket pages or backend ticket data for sale, restock, presale, or status-change signals; emit structured alerts that can be pushed to OpenClaw channels, webhooks, or other notification backends. Use when users want reliable ticket notifications rather than automated checkout. metadata: {"openclaw":{"requires":{"bins":["python3"]},"emoji":"🎫"}} --- # Ticket Signal Watch This skill is for reliable ticket notifications, not automated checkout. Use it when: - a user wants to monitor ticket sale or restock signals - a backend already has ticket data and needs a push-ready event format - you want OpenClaw to check official pages, search pages, or other text sources for ticket signals ## Files - Skill root: `{baseDir}` - Script: `{baseDir}/scripts/watch_ticket_pages.py` - Target example: `{baseDir}/config/targets.example.json` - Notifier example: `{baseDir}/config/notifiers.example.json` - Default state path: `{baseDir}/state/state.json` ## Operating model Treat the workflow as three layers: 1. `collector` - fetch page text or consume backend data 2. `signal engine` - decide whether the change is meaningful 3. `notifier` - push the resulting event to OpenClaw channels, webhooks, or another downstream system The ideal production setup is: - use backend data if available - fall back to page checks only when needed - keep collection and notification decoupled ## Recommended usage Run the script with a target config and a writable state file: ```bash python3 "{baseDir}/scripts/watch_ticket_pages.py" \ --config "{baseDir}/config/targets.example.json" \ --state "{baseDir}/state/state.json" \ --json ``` If `alerts` is empty, do not send a notification. If `alerts` is non-empty, forward the structured result to: - an OpenClaw channel - a webhook - a file/queue processor ## Output expectations The script should produce: - `results`: per-target check results - `alerts`: only meaningful changes worth notifying - `summary`: short human-readable summary Each alert should contain enough information to route downstream: - `name` - `platform` - `url` - `signal_hits` - `signal_level` - `alert_reasons` ## Configuration guidance Prefer official detail pages over generic search pages. Use: - `require_all` for identity words that must be present - `match_any` for actionable signal words - `signal_keywords.high` for the strongest signals Examples of strong signals: - `立即购买` - `立即预订` - `可选座` - `有票` - `开售` - `预售中` - `补票` - `回流` - `加场` ## Guardrails - Do not treat generic page changes as sale signals. - Search pages are weaker than detail pages. - Add cooldown, dedupe, and jitter before high-frequency polling. - If a platform starts returning anti-bot pages or challenge pages, mark that explicitly instead of claiming success. - This skill is for notification workflows; do not imply that it can safely complete checkout automatically.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: chaoyang78/acpx-harness-routing (version 1.0.0)

# ACPX Harness Routing ## 原则 当任务明确属于 harness / Claude / Codex / Gemini ACPX 调度任务时，**必须强制套用本 skill**。 组织方式遵循： 1. 先原则 2. 再判断路径 3. 再执行细则 目标只有一个： - 用最少分叉、最稳的方式，把总控 agent 对 harness 的调度做成可复用工作法 --- ## 一句话规则 - **harness 任务必须用本 skill** - **one-shot：默认 ACP runtime** - **连续任务：默认 direct acpx named session** - **Claude：技术架构 / 技术方案** - **Codex：需求分析 / 代码实现** - **Gemini：交叉验证 / 第二视角** - **只要底层走 acpx / harness，就必须落实“全部批准、不等待交互输入”** - **用户指定优先于默认规则** --- ## 判断树 ### 第一步：先判断是否属于 harness 任务 属于以下情况时，直接进入本 skill： - 需要调度 Claude / Codex / Gemini 做分析、实现、验证 - 需要通过 ACP runtime 或 direct acpx 调用 harness - 需要 one-shot 或连续多轮 harness 工作流 不属于以上情况时，不用本 skill。 --- ### 第二步：选角色 默认分工： - **Claude**：技术架构、技术方案、结构化技术分析 - **Codex**：需求分析、代码实现 - **Gemini**：交叉验证、第二视角、多文件快速综合 若用户明确指定角色，则覆盖默认分工。 --- ### 第三步：选调用路径 #### A. one-shot 任务 默认走： ```text sessions_spawn(runtime="acp", agentId="claude|codex|gemini", mode="run", ...) ``` 适用： - 单轮分析 - 单轮方案 - 单轮需求分析 - 单轮代码实现 - 单轮验证 - 一次性文件生成 #### B. 连续任务 / 多轮任务 默认走： ```text direct acpx named session ``` 适用： - 需要连续承接上下文 - 需要同一个 harness 连续几轮工作 - 需要显式控制 session / cwd / timeout / 审批行为 当前约束： - Telegram 入口下，ACP runtime 的 `thread=true` 不可用 - `mode="session"` 依赖 `thread=true` - 所以当前 Telegram 总控入口，不把 ACP runtime session 作为连续任务主路径 --- ## 硬规则 ### 1. 审批与交互规则（强制） 无论是 one-shot 还是 long-run，只要底层走的是 acpx / harness 调度，都必须显式确保采用： - 全部批准 - 非交互不等待输入 尤其 direct acpx 调用时，默认必须带： ```bash --approve-all --non-interactive-permissions deny ``` 这是强制规则，不能省略。 原因： 过去大量“超时 / 不返回 / 卡住”的情况，根因不是 Claude / Codex 不可用，而是没有显式带上这组参数，导致 harness 在非交互环境里等待输入或反馈。 一句话： - **只要是 acpx harness 调度，就必须把“全部批准、不等待交互输入”落实到调用参数上。** --- ### 2. 连续会话规则（强制） 连续任务默认走 direct acpx named session，并遵守以下铁律： #### 铁律 1：创建 / ensure session 时必须显式带 `--cwd` 错误： ```bash acpx claude sessions ensure --name oc-claude-xxx ``` 正确： ```bash acpx --cwd /path/to/workspace claude sessions ensure --name oc-claude-xxx ``` #### 铁律 2：后续调用必须保持同一 `--cwd` 否则会出现： - session 找不到 - session 绑错目录 - 连续性失效 #### 铁律 3：session 名统一 默认建议： - `oc-claude-<conversationId>` - `oc-codex-<conversationId>` - `oc-gemini-<conversationId>` 若没有稳定 conversationId，则退化为： - `oc-<agent>-<taskSlug>-<date>` --- ### 3. 超时规则 默认采用翻倍后的档位： - 小任务：180 - 中任务：360 - 大任务：600~1200 说明： - timeout 是上限，不是必须等满 - 任务完成即返回 --- ## 执行模板 把 harness 当作执行型 worker，不当作闲聊对象。 任务描述默认使用四段： 1. 目标 2. 边界 3. 输出物 4. 约束 模板： ```text 目标： <要完成什么> 边界： <允许看哪里 / 改哪里 / 不准碰什么> 输出物： <最终要产出什么文件/结论> 约束： <风格、实现方式、完成后回复格式> ``` --- ## 已验证事实 ### 已验证通过 1. OpenClaw ACP runtime one-shot 可用 2. direct acpx Claude 可用 3. direct acpx Codex 可用 4. Claude / Codex 可真实写文件 5. direct acpx named session 连续承接可用 ### 已验证限制 1. Telegram 入口不支持 ACP `thread=true` thread spawn 2. `mode="session"` 依赖 `thread=true` 3. Telegram 总控入口当前不适合用 ACP runtime 做连续 thread session --- ## 最终落地规则 如果你只记住三件事，就记住这三件事： 1. **harness 任务必须先进入本 skill** 2. **one-shot 走 ACP runtime，连续任务走 direct acpx named session** 3. **只要走 acpx / harness，就必须把“全部批准、不等待交互输入”落实到参数里**


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal:  | SkillSpector: clean (LOW)
Skill: qiffang/mem9 (version 1.0.5)

--- name: mem9 version: 1.0.5 description: | ⚠️ DEPRECATED — This local copy is no longer maintained. The canonical skill lives at https://clawhub.ai/c4pt0r/mem9-ai If you are reading this, run the update command below to pull the latest version. keywords: - mem9 - memory plugin - persistent memory - agent memory - install memory - setup memory - openclaw memory - cloud memory metadata: openclaw: emoji: "🧠" deprecated: true --- # ⚠️ DEPRECATED This skill file is **no longer maintained** in this repository. The canonical, up-to-date version lives at: 👉 **https://clawhub.ai/c4pt0r/mem9-ai** ## How to update Replace this file with the latest version: ```bash # Install from ClawHub directly: openclaw skills install c4pt0r/mem9-ai Or visit https://clawhub.ai/c4pt0r/mem9-ai to view the latest version. --- _Last updated: 2026-03-12. All future updates are published at https://clawhub.ai/c4pt0r/mem9-ai only._


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: aprilox/clawstats (version 1.0.1)

--- name: clawstats description: Comprehensive system monitoring for OpenClaw: CPU, RAM, Disk, and Processes. metadata: {"clawdbot":{"emoji":"📊","requires":{"bins":["free","df","top","ps"]},"install":[]}} --- # 📊 ClawStat Skill A comprehensive system monitoring skill for OpenClaw agents to track server health and performance. ## 🚀 Features - **CPU & RAM**: Real-time usage statistics. - **Disk**: Track available space on the root partition. - **Temperature**: Monitor CPU temperature (via `sensors` or `thermal_zone`). - **Top Processes**: Identify resource-hungry applications. - **Load Average**: Check system pressure over time. ## 🛠️ Tools The skill provides a single versatile script: - `monitor.sh [cpu|ram|disk|temp|top|all]`: Get specific or full system stats. ## 📦 Installation (Manual) 1. Clone or copy this directory to `~/.openclaw/workspace/skills/clawstats`. 2. Ensure `monitor.sh` is executable: `chmod +x monitor.sh`. 3. (Optional) Install `lm-sensors` for temperature tracking. ## 📖 Usage Examples - `monitor.sh all`: Get a complete health report. - `monitor.sh top`: See which processes are slowing down the system. --- *Created by Chela 🫐 & Aprilox*

path: monitor.sh
content: #!/bin/bash

# Enhanced System Monitor for OpenClaw
# Provides CPU, RAM, Disk usage, Temperature, and Top Processes

get_cpu() {
    top -bn1 | grep "Cpu(s)" | sed "s/.*, *\([0-9.]*\)%* id.*/\1/" | awk '{print 100 - $1"%"}'
}

get_ram() {
    free -h | awk '/^Mem:/ {print $3 "/" $2 " (" $7 " available)"}'
}

get_disk() {
    df -h / | awk 'NR==2 {print $3 "/" $2 " (" $5 " used)"}'
}

get_temp() {
    if command -v sensors > /dev/null && sensors 2>/dev/null | grep -E "Package id 0|Core 0|temp1" > /dev/null; then
        sensors | grep -E "Package id 0|Core 0|temp1" | head -1 | awk '{print $3}'
    elif [ -f /sys/class/thermal/thermal_zone0/temp ]; then
        awk '{printf "%.1f°C\n", $1/1000}' /sys/class/thermal/thermal_zone0/temp
    else
        echo "N/A (Virtual Server)"
    fi
}

get_top_cpu() {
    ps -eo pcpu,comm --sort=-pcpu | head -6 | tail -5 | awk '{print $2 " (" $1 "%)"}'
}

get_top_mem() {
    ps -eo pmem,comm --sort=-pmem | head -6 | tail -5 | awk '{print $2 " (" $1 "%)"}'
}

case "$1" in
    cpu) get_cpu ;;
    ram) get_ram ;;
    disk) get_disk ;;
    temp) get_temp ;;
    top)
        echo "Top CPU Processes:"
        get_top_cpu
        echo ""
        echo "Top Memory Processes:"
        get_top_mem
        ;;
    all|*)
        echo "--- 🖥️  System Overview ---"
        echo "CPU Usage: $(get_cpu)"
        echo "RAM Used:  $(get_ram)"
        echo "Disk (/):  $(get_disk)"
        echo "Temp:      $(get_temp)"
        echo ""
        echo "--- 📈 Load Average ---"
        uptime | awk -F'load average:' '{ print $2 }'
        echo ""
        echo "--- 🔥 Top Processes (CPU) ---"
        get_top_cpu
        ;;
esac


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