OpenClaw/clawhub-security-signals huggingface dataset:
Skill: mikeclaw007/capacity (version 1.0.0)

--- name: capacity description: "Forecasting load, headroom, and scaling plans. Use before big launches or cost reviews." --- # Capacity Structured guidance for **capacity planning** (load, headroom, scaling): confirm triggers, propose the stages below, and adapt if the user wants a lighter pass. ## When to Offer This Workflow **Trigger conditions:** - User mentions **capacity**, **headroom**, **scaling plans**, or closely related work - They want a structured workflow rather than ad-hoc tips - They are preparing a review, rollout, or stakeholder communication **Initial offer:** Explain the four stages briefly and ask whether to follow this workflow or work freeform. If they decline, continue in their preferred style. ## Workflow Stages ### Stage 1: Clarify context & goals Anchor on **growth assumptions and seasonality**. Ask what success looks like, constraints, and what must not break. Capture unknowns early. ### Stage 2: Design or plan the approach Translate goals into a concrete plan around **headroom and bottlenecks**. Compare alternatives and explicit trade-offs; avoid implicit assumptions. ### Stage 3: Implement, validate, and harden Execute with verification loops tied to **cost vs performance trade-offs**. Prefer small steps, measurable checks, and rollback points where risk is high. ### Stage 4: Operate, communicate, and iterate Close the loop with **load tests and forecasts**: monitoring, documentation, stakeholder updates, and lessons learned for the next cycle. ## Checklist Before Completion - Goals and constraints are explicit for **capacity** planning - Risks and trade-offs are stated, not hand-waved - Verification steps match the change’s impact (tests, canary, peer review) - Operational follow-through is covered (monitoring, docs, owners) ## Tips for Effective Guidance - Be procedural: stage-by-stage, with clear exit criteria - Ask for missing context (environment, scale, deadlines) before prescribing - Prefer checklists and concrete examples over generic platitudes - If the user declines the workflow, switch to freeform help without lecturing ## Handling Deviations - If the user wants to skip a stage: confirm and continue with what they need. - If context is missing: ask targeted questions before strong recommendations. - Prefer concrete examples, trade-offs, and verification steps over generic advice. ## Quality Bar - Each recommendation should be **actionable** (what to do next). - Call out **failure modes** relevant to capacity (security, scale, UX, or ops). - Keep tone direct and respectful of the user’s time.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: john-20-ux/scoped-memory-manager (version 1.0.0)

--- name: scoped-memory-manager description: Installs and manages Scope-Based Memory and Automated REM Sleep (memory consolidation) for OpenClaw agents. Use this skill when an agent's MEMORY.md is bloated, when the user asks to implement "REM Sleep", "memory decay", or "scoped memory", or to organize an agent's memory into domain-specific topics to save context window tokens. --- # Scoped Memory Manager This skill upgrades an OpenClaw agent's memory architecture from a single, bloated `MEMORY.md` to a **Scope-Based Memory** system with automated **REM Sleep** (memory consolidation and decay). ## Architecture 1. **Global Router (`MEMORY.md`)**: Kept extremely lean. Only contains core identity, active focus, and an index of domain-specific memory files. 2. **Domain-Specific Memory (`memory/topics/*.md`)**: Stores hyper-specific rules, constraints, and knowledge (e.g., `shopify.md`, `rails.md`). Retrieved dynamically via `memory_search` and `memory_get` only when relevant. 3. **Automated REM Sleep**: A scheduled background job (cron) that wakes up an isolated agent to compress daily logs, extract new patterns, prune outdated "trauma" constraints, and file the distilled knowledge into the correct topic files. ## Installation & Setup When the user asks to install or configure scoped memory / REM sleep, follow these steps: ### 1. Scaffold the Directory Structure Run the setup script to create the necessary directories: ```bash sh scripts/setup.sh ``` ### 2. Schedule the REM Sleep Cron Job Use the `cron` tool to schedule the weekly consolidation job. Call the `cron` tool with `action: "add"` and the following payload: - **name**: "Memory REM Sleep (Consolidation)" - **schedule**: `{ "kind": "cron", "expr": "0 3 * * 0" }` (Sundays at 3:00 AM) - **sessionTarget**: "isolated" - **delivery**: `{ "mode": "announce" }` - **payload**: ```json { "kind": "agentTurn", "message": "It is time for your weekly REM sleep cycle. Please read the current `MEMORY.md` and the daily log files (`memory/YYYY-MM-DD.md`) from the past 7 days. Your task is to perform memory consolidation: \n1. Extract new patterns and important context from the logs.\n2. Review `MEMORY.md` and prune obsolete rules or constraints.\n3. Move domain-specific knowledge into the appropriate `memory/topics/*.md` files.\n4. Rewrite `MEMORY.md` to be a concise global router.\n5. Summarize what was added, moved, and forgotten." } ``` ### 3. Migrate Existing Memory If the agent already has a bloated `MEMORY.md`, proactively offer to read it and partition the content into `memory/topics/*.md` files right now. ## Usage Guidelines - Remind users that `MEMORY.md` is NOT for storing everything. - When learning a new specific framework, proactively create a new topic file in `memory/topics/` instead of polluting the global `MEMORY.md`.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: nexscope/ebay-advertising (version 1.0.0)

# eBay Advertising Master eBay advertising — Promoted Listings Standard, Advanced, and Offsite Ads. Campaign setup, bidding strategy, budget allocation, and ROI optimization for eBay sellers. ## Capabilities - Promoted Listings Standard: ad rate strategy by category - Promoted Listings Advanced: CPC bidding and keyword targeting - Offsite Ads opt-in analysis and fee calculation - Campaign structure and listing selection - Budget allocation across Promoted Listings types - Performance metrics: ROAS, impression share, click-through rate - Seasonal campaign planning - A/B testing promoted vs organic performance ## Install ```bash npx skills add nexscope/ebay-advertising ``` ## Usage Ask your AI agent: - "Set up Promoted Listings campaigns for my top eBay products." - "What ad rate should I use for Promoted Listings Standard?" - "Compare my eBay ad ROAS against category benchmarks." ## Output Structured recommendations with actionable steps, benchmarks, and platform-specific guidance. --- *Built by [Nexscope](https://www.nexscope.ai/) — AI-powered e-commerce tools for sellers worldwide.*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: leooooooow/content-source-to-markdown (version 1.0.0)

--- name: content-source-to-markdown description: Convert URLs, social posts, and web snippets into clean markdown briefs for ecommerce content research and workflow reuse. Use when teams need structured inputs for script, SEO, and campaign planning. --- # Content Source to Markdown ## Skill Card - **Category:** Market Intelligence - **Core problem:** Raw source content is noisy and hard to reuse in ecommerce workflows. - **Best for:** Competitor intelligence, creator content teardown, script research prep. - **Expected input:** URL list, social links, source snippets, output purpose. - **Expected output:** Structured markdown brief with findings and action points. ## Workflow 1. Extract source content. 2. Remove noise. 3. Reorganize for workflow usage. 4. Output markdown-ready insight brief. ## Output format 1. Source summary 2. Key findings 3. Actionable insights 4. Next tasks ## Quality and safety rules - Preserve key facts. - Keep source context clear. - Ensure output is reusable for follow-on tasks. ## License Copyright (c) 2026 **Razestar**. This skill is provided under **CC BY-NC-SA 4.0** for non-commercial use. You may reuse and adapt it with attribution to Razestar, and share derivatives under the same license. Commercial use requires a separate paid commercial license from **Razestar**. No trademark rights are granted.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: linkfox-ai/linkfox-temu-fulfillment-global (version 1.0.0)

--- name: linkfox-temu-fulfillment-global version: 1.0.0 category: product-sourcing description: Temu 全球站（非 US/EU）电商履行/发货 API（合一）：Buy-Shipping购标面单、合作仓履约、卖家自发货、物流跟踪等23个接口（不含 Scan Form）。当用户提到 Temu Global 发货、购标、Buy-Shipping、合作仓、自发货、tracking、shipment.create、site=global order-shipping 时触发。订单用 linkfox-temu-order-global。Scan Form 请用 linkfox-temu-fulfillment-us。 --- # Temu 全球站 — 电商履行 / 发货（Fulfillment） 本 skill（`linkfox-temu-fulfillment-global`）覆盖 Partner **Global** **Fulfillment** 域 **23** 个已接入 `type`（与 US 版对齐但 **不含** 4 个 Scan Form 接口）。 | 域 | 脚本前缀 | 接口数 | |----|----------|--------| | Buy-Shipping | `global_buy_shipping_*` | 13 | | Co-Warehouse | `global_co_warehouse_*` | 4 | | Self-Fulfilled | `global_self_fulfilled_*` | 5 | | Tracking | `global_tracking_*` | 1 | **未接入（相对 US）**：`temu.logistics.scanform.create`、`temu.logistics.scanform.get`、`temu.logistics.scanform.document.get`、`temu.logistics.candidate.scanform.list.get` — 请用 **`linkfox-temu-fulfillment-us`**（`site=us`）。 详见 [partner-global-catalog.md](./references/partner-global-catalog.md)。美国站请用 **`linkfox-temu-fulfillment-us`**；欧洲站请用 **`linkfox-temu-fulfillment-eu`**。 **网关**： | 能力 | 方法 | 路径 | |------|------|------| | 履约 OpenAPI | POST | `https://tool-gateway.linkfox.com/temu/proxy` | | 加签文件下载 | POST | `https://tool-gateway.linkfox.com/temu/fileDownload` | ## 相关 skill | 场景 | skill | |------|--------| | 订单列表/详情/地址 | `linkfox-temu-order-global` | | 取消订单 | [REDACTED_SECRET] | | 商品管理 | [REDACTED_SECRET] | | 美国站履约（含 Scan Form） | `linkfox-temu-fulfillment-us` | | 欧洲站履约 | `linkfox-temu-fulfillment-eu` | | 退货退款 | [REDACTED_SECRET] | ## 默认参数 | 字段 | 默认 | |------|------| | site | `global` | | managementType | `semi-managed` | | tokenPurpose | `order-shipping` | ## Scripts（按域） ### Buy-Shipping（`global_buy_shipping_*`） 购标、面单、上门揽收等（**不含 Scan Form**）— 见 [apis/README.md](./references/apis/README.md)。 ### Co-Warehouse（`global_co_warehouse_*`） `bg.cooperativewarehouse.*` — 合作仓授权、提交/取消履约。 ### Self-Fulfilled（`global_self_fulfilled_*`） `bg.logistics.shipment.v2.*`、`shippingtype.update` 等 — 卖家自带运单号。 ### Tracking（`global_tracking_*`） `temu.track.trackinginfo.get` ### 通用 | 脚本 | 说明 | |------|------| | `temu_global_proxy.py` | 任意 `type` | | `temu_global_file_download.py` | 加签文件下载 | 薄封装统一调用 **`_global_fulfillment_script.run_cli`**。 ## 示例 ```bash export LINKFOXAGENT_API_KEY="<key>" # Buy-Shipping 购标 python scripts/global_buy_shipping_logistics_shipment_create.py '{ "accessToken": "TOKEN", "site": "global", "tokenPurpose": "order-shipping", "request": { } }' # 卖家自发货更新跟踪号 python scripts/global_self_fulfilled_logistics_shipment_shippingtype_update.py '{ "accessToken": "TOKEN", "site": "global", "tokenPurpose": "order-shipping", "request": { "editPackageRequestList": [{ "packageSn": "PKG-1", "trackingNumber": "1Z..." }] } }' ``` **Feedback：** `skillName`：`linkfox-temu-fulfillment-global`


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: imzye/sre-news-digest (version 1.0.2)

--- name: sre-news-digest description: Generate a categorized and rated news digest from sre.news. Use for creating SRE/DevOps/Solution Architect daily or periodic news summaries with expert scoring, article categorization, and markdown output. --- # SRE News Digest Generate a professionally curated, categorized, and rated news digest from [sre.news](https://sre.news) with a senior SRE/DevOps/Solution Architect perspective. ## Workflow 1. **Scrape** — Fetch recent news from sre.news 2. **Read** — Open and read each article to understand its content 3. **Rate** — Score each article (1-5 ⭐) using the scoring rubric 4. **Categorize** — Assign categories from the taxonomy 5. **Format** — Generate the final markdown digest grouped by category ## Step 1: Scrape sre.news Run the helper script (path relative to this skill's directory): ```bash python scripts/scrape_sre_news.py [days] ``` The script outputs a JSON array. Each item contains `title`, `url`, `source`, and optionally `date`. The `days` argument filters articles to the requested time range (default: 1 day). If date metadata is unavailable on the page, all articles are returned. If the script output is incomplete or titles are missing, use the browser to visit `https://sre.news` directly and collect articles manually. When browsing, capture the original article title, URL, and source/publication name for each item. ## Step 2: Read Each Article Open each article URL and read the content to understand key points, technical depth, and relevance to SRE/DevOps practice. Focus on the article body; avoid following tracker links, ad networks, or unrelated external resources embedded in the page. This step is critical for accurate rating and summarization. ## Step 3: Rate Articles Rate each article from 1 to 5 stars from a senior SRE/DevOps/Solution Architect perspective. Consult the scoring rubric for detailed criteria: ``` references/scoring-rubric.md ``` ## Step 4: Categorize Articles Assign one or two categories to each article. The scoring rubric file also contains the category taxonomy. Create new categories if existing ones do not fit. Group articles by their primary category in the final output. ## Step 5: Format Output Generate the digest in English as a Markdown file. Follow the template structure in: ``` templates/digest_template.md ``` Key formatting rules: - Title includes the date of the digest - Articles grouped by category (use `##` for category headers) - Each article includes: title with link, source, star rating, and a 2-3 sentence expert summary - Preserve original article titles and URLs exactly as found - Write summaries from an SRE/DevOps/Solution Architect perspective, highlighting operational impact and practical relevance - End with a footer crediting sre.news as the source Save the output to `sre_news_digest.md` in the current working directory, or a user-specified path.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: casperzinou/reel-digest (version 1.0.0)

--- name: reel-digest description: Download, transcribe, extract frames, and deeply analyze any video or reel from URL (Instagram, YouTube, TikTok, X, direct MP4). Use when user shares a video/reel URL and wants to understand its content, strategy, script, visual elements, or marketing breakdown. Triggers on "analyze this reel", "digest this video", "what's in this video", "break down this clip", or when any video URL is shared with intent to analyze. NOT for downloading videos to watch — only for AI-powered content analysis. --- # Reel Digest — Full Video Analysis Pipeline ## Quick Start Give this skill a video URL. It will download, extract frames, transcribe audio, and deliver a complete analysis. ## Step 1: Download & Extract Run the bash pipeline script (handles Instagram embed extraction, frame extraction, audio, and transcription): ```bash bash scripts/ig-reel-dl.sh "<URL>" /tmp/reel-digest ``` This produces: - `video.mp4` — original video - `audio.wav` — extracted audio (16kHz mono) - `transcript.txt` — Whisper transcription with timestamps - `frames/` — key frames (1 per 5 seconds, 640px wide) For non-Instagram URLs (YouTube, TikTok, etc.), use the Python script: ```bash python3 scripts/reel-digest.py "<URL>" -o /tmp/reel-digest -f 10 ``` ## Step 2: Analyze Frames 1. Read `transcript.txt` for the spoken content 2. Copy frames from `/tmp` to workspace directory (required for image tool) 3. Analyze 4-8 key frames using the `image` tool 4. Describe: on-screen text, UI, products, branding, visual style, transitions ## Step 3: Synthesize Combine transcript + frame analysis into a structured digest: 1. **Hook** — Opening 3 seconds: what grabs attention? 2. **Narrative Arc** — Frame-by-frame story 3. **Key Messages** — Main points communicated 4. **Visual Strategy** — Production quality, text overlays, aesthetic 5. **Engagement Tactics** — What makes this shareable? 6. **Business Intel** — Products, CTAs, pricing, competitive signals 7. **Viral Mechanics** — Why this works for the algorithm ## Step 4: Deliver Present in clean, scannable format. Quote exact transcript text, describe exact visual elements. No generic advice. ## Requirements - `curl` — HTTP requests - `ffmpeg` / `ffprobe` — video processing - `yt-dlp` — YouTube/TikTok downloads - `faster-whisper` (Python) — audio transcription ## Troubleshooting - **Instagram 403**: CDN URLs expire fast. The bash script handles this with single-session extraction via `tr -d '\\'` on embed HTML - **Vision model timeout**: Resize frames to 360px: `ffmpeg -i frame.jpg -vf scale=360:-1 small.jpg` - **Image tool path error**: Files must be under workspace directory, not `/tmp`. Copy first. - **Whisper OOM**: Use `--no-transcript` flag, analyze frames only - **No audio track**: Some clips are visual-only. Use `--no-audio` flag.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: denfly618/denfly-skill (version 1.0.0)

--- name: weather description: Get current weather and forecasts (no API key required). homepage: https://wttr.in/:help metadata: {"clawdbot":{"emoji":"🌤️","requires":{"bins":["curl"]}}} --- # Weather Two free services, no API keys needed. ## wttr.in (primary) Quick one-liner: ```bash curl -s "wttr.in/London?format=3" # Output: London: ⛅️ +8°C ``` Compact format: ```bash curl -s "wttr.in/London?format=%l:+%c+%t+%h+%w" # Output: London: ⛅️ +8°C 71% ↙5km/h ``` Full forecast: ```bash curl -s "wttr.in/London?T" ``` Format codes: `%c` condition · `%t` temp · `%h` humidity · `%w` wind · `%l` location · `%m` moon Tips: - URL-encode spaces: `wttr.in/New+York` - Airport codes: `wttr.in/JFK` - Units: `?m` (metric) `?u` (USCS) - Today only: `?1` · Current only: `?0` - PNG: `curl -s "wttr.in/Berlin.png" -o /tmp/weather.png` ## Open-Meteo (fallback, JSON) Free, no key, good for programmatic use: ```bash curl -s "https://api.open-meteo.com/v1/forecast?latitude=51.5&longitude=-0.12&current_weather=true" ``` Find coordinates for a city, then query. Returns JSON with temp, windspeed, weathercode. Docs: https://open-meteo.com/en/docs


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: crimsondevil333333/devlog-agent-skill (version 1.0.0)

# DevLog Skill 🦞 A standardized journaling skill for OpenClaw agents to track progress, tasks, and project status using `dev-log-cli`. ## Description This skill enables agents to maintain a professional developer log. It's designed to capture context, project milestones, and task statuses in a structured SQLite database. ## Requirements - `dev-log-cli` (installed via `pipx`) ## Links - **GitHub**: [https://github.com/CrimsonDevil333333/dev-log-cli](https://github.com/CrimsonDevil333333/dev-log-cli) - **PyPI**: [https://pypi.org/project/dev-log-cli/](https://pypi.org/project/dev-log-cli/) - **ClawHub**: [https://clawhub.com/skills/devlog-skill](https://clawhub.com/skills/devlog-skill) (Pending Publication) ## Usage ### 📝 Adding Entries Agents should use this to log significant progress or blockers. ```bash devlog add "Finished implementing the auth module" --project "Project Alpha" --status "completed" --tags "auth,feature" ``` ### 📋 Listing Logs View recent activity for context. ```bash devlog list --project "Project Alpha" --limit 5 ``` ### 📊 Viewing Stats Check project health and activity. ```bash devlog stats --project "Project Alpha" ``` ### 🔍 Searching Find historical context on specific topics. ```bash devlog search "infinite loop" ``` ### 🛠️ Editing/Viewing Detailed inspection or correction of entries. ```bash devlog view <id> devlog edit <id> ``` ## Internal Setup The skill includes a `setup.sh` to ensure the CLI is available.

path: setup.sh
content: #!/bin/bash
# setup.sh - Ensure dev-log-cli is installed for the DevLog Skill

if ! command -v devlog &> /dev/null
then
    echo "devlog not found. Checking for pipx..."
    if ! command -v pipx &> /dev/null
    then
        echo "pipx not found. Attempting to install pipx..."
        python3 -m pip install --user pipx
        python3 -m pipx ensurepath --force
        export PATH="$PATH:$HOME/.local/bin"
        
        if ! command -v pipx &> /dev/null
        then
            echo "Error: Failed to install pipx automatically."
            echo "Please install it manually: https://github.com/pypa/pipx#install-pipx"
            exit 1
        fi
    fi
    
    echo "Installing dev-log-cli via pipx..."
    pipx install dev-log-cli
    
    if command -v devlog &> /dev/null
    then
        echo "✓ dev-log-cli successfully installed and verified!"
    else
        echo "Error: devlog command still not found after installation. Please check your PATH."
        exit 1
    fi
else
    echo "✓ devlog is already installed."
fi


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: article-summarizer (version 0.1.0)

--- name: article-summarizer description: 文章摘要生成器 - 自动抓取网页文章，生成结构化摘要。支持长文简化、关键点提取、要点列表。适用于自媒体、运营、研究人员。 --- # 文章摘要 (Article Summarizer) ## 功能 - URL 输入自动抓取 - 生成结构化摘要 - 关键点提取 - 多语言支持 ## 使用方式 ```bash article-summarizer "https://example.com/article" ``` ## 价格 - 免费：10篇/天 - 专业版：¥49/月：无限制 - 企业版：¥199/月：API接入


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