OpenClaw/clawhub-security-signals huggingface dataset:
Skill: abdullah944/landing-page-copy-helper-skill (version 0.1.0)

--- name: "Landing Page Copy Helper Skill" version: 0.1.0 slug: "landing-page-copy-helper-skill" description: "Guides structured help for Landing Page Copy Helper using clear templates, checks, and safe defaults (category: Web & Marketing)." category: "Web & Marketing" tags: - "landing-page-copy-helper" - "openclaw" - "templates" - "web" generated: "2026-05-07" --- ## Purpose Guides structured help for Landing Page Copy Helper using clear templates, checks, and safe defaults (category: Web & Marketing). ## When to use - When you want structured guidance in the "Web & Marketing" area. - When you need copy-paste-safe templates rather than improvised shell commands. - When you want repeatable prompts the agent can follow without external scraping. ## Safety rules - Do not collect passwords, OTPs, private keys, wallets, seeds, or session secrets. - Do not propose remote installers that execute unseen code or chained download-and-run snippets. - Keep outputs factual and reversible: prefer checklists over irreversible destructive actions. ## Inputs - Your goal in one paragraph (no secrets). - Optional constraints: audience, tone, length, deadline. - Optional pasted notes you own the rights to (keep PII minimal). ## Output format - A concise plan - Numbered checklist - Short next-actions list - Optional draft copy blocks you can edit ## Example prompts - Help me outline a concise plan using the Landing Page Copy Helper approach. - Critique my draft outputs and suggest safer, clearer wording for Landing Page Copy Helper. - Produce a checklist I can reuse weekly for Landing Page Copy Helper without requesting private data. ## Support / Donate If this skill helps your workflow, you can support maintenance here: - PayPal: https://www.paypal.com/donate/?hosted_button_id=MJHCRZA9Z4X7Y


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: linuszz/customer-experience (version 1.0.0)

--- name: customer-experience description: "Map and analyze customer experience touchpoints. Use for improving satisfaction, loyalty, and customer journey optimization." --- # Customer Experience Analysis ## Metadata - **Name**: customer-experience - **Description**: Customer journey and touchpoint analysis - **Triggers**: customer experience, CX, journey map, touchpoint, satisfaction ## Instructions Map customer experience for $ARGUMENTS to identify improvement opportunities. ## Framework ### Customer Journey Stages | Stage | Touchpoints | Customer Actions | Emotions | |-------|-------------|------------------|----------| | **Awareness** | Ads, social, word-of-mouth | Discover brand | Curious | | **Consideration** | Website, reviews, store | Research options | Evaluating | | **Purchase** | Checkout, sales, payment | Buy product | Excited/Anxious | | **Use** | Product, support, onboarding | Use solution | Satisfied/Frustrated | | **Loyalty** | Follow-up, community, rewards | Recommend, repurchase | Engaged | ### Experience Metrics | Metric | Formula | Target | |--------|---------|--------| | **NPS** | % Promoters - % Detractors | >50 | | **CSAT** | Satisfied customers / Total surveyed | >80% | | **CES** | Effort score (1-7 scale) | <3 | | **Retention** | Returning customers / Total | >90% | ## Output ``` ## Customer Experience Analysis: [Product/Service] ### Journey Map **Stage 1: Awareness** - Touchpoints: [List] - Pain points: [Issues] - Opportunities: [Improvements] **Stage 2: Consideration** - Touchpoints: [List] - Pain points: [Issues] - Opportunities: [Improvements] [Continue for all stages] ### Experience Scorecard | Metric | Current | Target | Status | |--------|---------|--------|--------| | NPS | 35 | 50 | 🟡 Gap: -15 | | CSAT | 72% | 80% | 🟡 Gap: -8% | | CES | 4.2 | 3.0 | 🔴 Gap: +1.2 | | Retention | 85% | 90% | 🟡 Gap: -5% | ### Priority Improvements | Priority | Stage | Issue | Impact | Effort | |----------|-------|-------|--------|--------| | 1 | Purchase | Long checkout | High | Medium | | 2 | Use | Complex onboarding | High | High | | 3 | Consideration | Poor mobile UX | Medium | Low | ### Action Plan **Immediate (0-30 days)** 1. [Action 1] 2. [Action 2] **Short-term (30-90 days)** 1. [Action 1] 2. [Action 2] ``` ## Tips - Walk through journey yourself - Interview real customers - Focus on emotional peaks and valleys - Prioritize high-impact, low-effort fixes


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: aktheknight/audio-transcribe (version 1.0.0)

# Audio Transcription Skill Auto-transcribe voice messages using faster-whisper (local, no API key needed). ## Requirements ```bash pip install faster-whisper ``` Models download automatically on first use. ## Usage ### Transcribe a file ```bash python3 /root/clawd/skills/audio-transcribe/scripts/transcribe.py /path/to/audio.ogg ``` ### Change model (edit script) Edit `transcribe.py` and change: ```python model = WhisperModel('small', device='cpu', compute_type='int8') # Options: tiny, base, small, medium, large-v3 ``` ## Models | Model | Size | VRAM/RAM | Speed | Use Case | |-------|------|----------|-------|----------| | tiny | 39 MB | ~1 GB | ⚡⚡⚡ | Quick drafts | | base | 74 MB | ~1 GB | ⚡⚡ | Basic accuracy | | **small** | **244 MB** | **~2 GB** | **⚡** | **Recommended** | | medium | 769 MB | ~5 GB | 🐢 | Better accuracy | | large-v3 | 1.5 GB | ~10 GB | 🐢🐢 | Best accuracy | ## Integration Clawdbot auto-transcribes incoming voice messages when this skill is enabled. ## Files - `scripts/transcribe.py` — Main transcription script - `SKILL.md` — This file


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jpaulgrayson/social-poster (version 1.0.0)

--- description: Post to social media via VibePost API. Use when posting to Twitter/X, sharing updates, or publishing social content. triggers: - post to twitter - social post - tweet - share update - vibepost --- # Social Poster Post to social media platforms via the VibePost API. ## Setup API key is configured in the script. Uses `x-quack-api-key` header for authentication. ## Scripts ### Post Content ```bash node skills/social-poster/scripts/post.mjs --text "Hello world" [--platform twitter] ``` ## API Reference - **Endpoint:** `POST https://vibepost-jpaulgrayson.replit.app/api/quack/post` - **Auth:** `x-quack-api-key` header - **Body:** `{ "text": "your message", "platform": "twitter" }` - **Field is `text`** not `content` ## Tips - Keep posts under 280 chars for Twitter - Add hashtags for discoverability - Be authentic — write as your agent persona


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (MEDIUM)
Skill: aiastia/aria2-downloader (version 1.0.0)

--- name: aria2-downloader version: 1.0.0 description: "Remote control aria2 via JSON-RPC API. Add downloads (magnet/HTTP/FTP), check progress, pause/resume/remove tasks, batch download from text. NOT for local aria2c CLI." --- # aria2 Downloader 通过 aria2 JSON-RPC API 远程控制 aria2 下载服务。 ## 首次配置 在 workspace 根目录创建 `.aria2-config.json`： ```json { "url": "https://your-server.com/jsonrpc", "token": "your-secret-token" } ``` > ⚠️ 此文件包含敏感信息，已在 `.gitignore` 中排除。 ## 功能 | 功能 | 说明 | |------|------| | 📥 添加下载 | 支持磁力链接、HTTP/FTP 直链 | | 📋 查看任务 | 查看所有活跃/等待/已完成的任务 | | ⏸️ 暂停任务 | 暂停指定下载 | | ▶️ 恢复任务 | 恢复暂停的下载 | | 🗑️ 删除任务 | 删除指定下载任务 | | 📄 批量下载 | 发送文本（每行一个链接），逐个添加 | ## 使用方式 ### 添加下载 用户说： - "下载这个 magnet:?xt=urn:btih:..." - "下载 https://example.com/file.zip" - "添加下载：magnet:?xt=..." → 调用 `scripts/aria2.js add <url>` ### 查看任务 用户说： - "查看下载进度" - "aria2 状态" - "下载到哪了" → 调用 `scripts/aria2.js list` ### 暂停任务 用户说： - "暂停下载 xxx" - "暂停 GID abc123" → 调用 `scripts/aria2.js pause <gid>` ### 恢复任务 用户说： - "恢复下载 xxx" - "继续下载 GID abc123" → 调用 `scripts/aria2.js unpause <gid>` ### 删除任务 用户说： - "取消下载 xxx" - "删除 GID abc123" → 调用 `scripts/aria2.js remove <gid>` ### 批量下载 用户发送一段文本（每行一个链接）： ``` magnet:?xt=urn:btih:aaa... magnet:?xt=urn:btih:bbb... https://example.com/file1.zip https://example.com/file2.zip ``` → 调用 `scripts/aria2.js batch` 并通过 stdin 传入链接 ## 脚本说明 所有操作通过 `scripts/aria2.js` 执行： ```bash # 查看帮助 node scripts/aria2.js help # 添加下载 node scripts/aria2.js add "magnet:?xt=urn:btih:..." # 查看所有任务 node scripts/aria2.js list # 暂停 node scripts/aria2.js pause <gid> # 恢复 node scripts/aria2.js unpause <gid> # 删除 node scripts/aria2.js remove <gid> # 批量下载（stdin 传入链接，每行一个） echo -e "magnet:?xt=...\nhttps://..." | node scripts/aria2.js batch ``` ## 配置文件 读取 workspace 根目录的 `.aria2-config.json`： ```json { "url": "https://your-server.com/jsonrpc", "token": "your-secret-token" } ``` 如果配置文件不存在，提示用户创建。 ## 输出格式 ### 任务列表 ``` 📋 活跃任务 (3): [abc123] ▓▓▓▓▓▓▓▓░░ 78.5% | 12.3 MB/s | Ubuntu-22.04.iso [def456] ▓▓░░░░░░░░ 15.2% | 5.6 MB/s | movie.mkv [ghi789] ▓▓▓▓▓▓▓▓▓▓ 100% | 完成 | file.zip ⏳ 等待中 (1): [jkl012] 等待中 | BigFile.tar.gz ✅ 已完成 (2): [mno345] 100% | archive.rar [pqr678] 100% | document.pdf ``` ### 添加下载 ``` ✅ 已添加下载 GID: abc123 文件: Ubuntu-22.04.iso ``` ### 批量下载 ``` 📥 批量下载 (4 个链接): ✅ [1] magnet:?xt=... → GID: abc123 ✅ [2] magnet:?xt=... → GID: def456 ✅ [3] https://example.com/file1.zip → GID: ghi789 ❌ [4] invalid-url → 失败: 无效链接 ``` ## 注意事项 - **不轮询**：只在用户请求时查看进度 - **不硬编码**：URL 和 Token 由用户配置 - **链接类型**：支持 magnet、http、https、ftp - **依赖**：Node.js（无需额外 npm 包，使用原生 fetch）


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

--- name: web-monitor description: Monitor web pages for content changes with CSS selector targeting, change detection via hashing, and notification integration. Use for price tracking, content alerts, and website change detection. --- # Web Monitor — Page Change Detection & Alerts Track web pages for content changes using hash-based comparison. Supports CSS selector extraction, interval-based monitoring, change history, and configurable notification delivery. ## Quick Start ```bash # Compare current page with previous snapshot python scripts/monitor.py --url https://example.com --compare state.json # Monitor with a CSS selector python scripts/monitor.py --url https://example.com --selector ".price" --compare state.json ``` ## Usage ```bash python scripts/monitor.py --url URL [OPTIONS] Options: --url URL Page URL to monitor (required) --selector SELECTOR CSS selector to extract specific content --compare FILE Compare with previous snapshot from FILE --state-file FILE Save current state to FILE (default: state.json) --interval SEC Auto-monitor at interval (seconds) --notify COMMAND Command to run on change detected --json Output as JSON --max-retries N Connection retries on failure (default: 3) ``` ## Examples ```bash # Simple page check python scripts/monitor.py --url https://example.com/page --compare state.json # Monitor a price element python scripts/monitor.py --url https://shop.example.com/product \ --selector ".product-price" --compare price-state.json # Continuous monitoring python scripts/monitor.py --url https://example.com \ --interval 3600 --compare state.json --notify "echo 'Changed!'" # JSON output for pipeline python scripts/monitor.py --url https://example.com --json ``` ## State File Format ```json { "url": "https://example.com/page", "selector": ".price", "hash": "sha256hash...", "timestamp": "2026-01-15T14:30:00Z" } ``` ## Features - **Hash-based change detection** — reliable content comparison - **CSS selector extraction** — monitor specific page sections - **State persistence** — stores snapshots for comparison - **Interval monitoring** — automatic periodic checks - **Notification hooks** — trigger commands on changes - **No external dependencies** — uses only Python stdlib - **SSL/HTTPS support** — secure page fetching - **JSON output** — structured data for automation


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: jrbobbyhansen-pixel/cron-retry (version 1.0.0)

--- name: cron-retry description: Auto-retry failed cron jobs on connection recovery. Use when cron jobs fail due to network errors and should be retried when connectivity is restored. Integrates with heartbeat to detect failed jobs and re-run them automatically. --- # Cron Retry Skill Automatically detect and retry cron jobs that failed due to network/connection errors. ## Quick Start (Heartbeat Integration) Add this to your `HEARTBEAT.md`: ```markdown ## Cron Recovery Check Check for cron jobs with lastStatus: "error". If the error matches network patterns (connection error, sendMessage failed, fetch failed, ETIMEDOUT, ECONNREFUSED), retry the job using cron tool with action: "run" and the job ID. Report what was recovered. ``` That's it. On each heartbeat, failed network jobs get retried automatically. ## How It Works 1. On heartbeat, check all cron jobs via `cron list` 2. Filter for jobs where `lastStatus = "error"` and `enabled = true` 3. Check if `lastError` matches network-related patterns 4. Re-run eligible jobs via `cron run` 5. Report results ## Network Error Patterns (Retryable) These errors indicate transient network issues worth retrying: - `Network request.*failed` - `Connection error` - `ECONNREFUSED` - `ETIMEDOUT` - `ENOTFOUND` - `sendMessage.*failed` - `fetch failed` - `socket hang up` ## What Gets Retried vs Skipped **Retried:** - Network timeouts - Connection refused - Message send failures - DNS lookup failures **Skipped (not retried):** - Logic errors (bad config, missing data) - Auth failures - Disabled jobs - Jobs that just ran successfully ## Manual Recovery Check To check and retry failed jobs manually: ```bash # List all jobs and their status clawdbot cron list # Find failed jobs clawdbot cron list | jq '.jobs[] | select(.state.lastStatus == "error") | {name, error: .state.lastError}' # Retry a specific job clawdbot cron run --id <JOB_ID> ``` ## Agent Implementation When implementing the heartbeat check: ``` 1. Call cron tool with action: "list" 2. For each job in response.jobs: - Skip if job.enabled !== true - Skip if job.state.lastStatus !== "error" - Check if job.state.lastError matches network patterns - If retryable: call cron tool with action: "run", jobId: job.id 3. Report: "Recovered X jobs" or "No failed jobs to recover" ``` ## Example Scenario 1. **7:00 PM** — Evening briefing cron fires 2. **Network hiccup** — Telegram send fails 3. **Job marked** `lastStatus: "error"`, `lastError: "Network request for 'sendMessage' failed!"` 4. **7:15 PM** — Connection restored, heartbeat runs 5. **Skill detects** the failed job, sees it's a network error 6. **Retries** the job → briefing delivered 7. **Reports**: "Recovered 1 job: evening-wrap-briefing" ## Safety - Only retries transient network errors - Respects job enabled state - Won't create retry loops (checks lastRunAtMs) - Reports all recovery attempts


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: nz365guy/draft-router (version 1.0.0)

# Draft Router Skill Route incoming drafts via Telegram inline buttons. Forwards messages get three action options. ## Installation ```bash # Make executable chmod +x /home/node/.openclaw/workspace/skills/draft-router/draft-router.js ``` ## Usage Auto-detects drafts by header pattern: `DRAFTS | YYYY-MM-DD HH:MM ---` ```javascript // From an OpenClaw agent const router = require('./skills/draft-router/draft-router.js'); // Check if message is a draft if (router.isDraftMessage(messageText)) { const result = router.handleDraft(messageText, 'drafts-app'); // Send via Telegram with buttons message.send({ to: chatId, message: result.text, buttons: result.buttons }); } ``` ## Button Actions | Button | Action | |--------|--------| | 🧠 Knowledge | Appends to MEMORY.md with timestamp and source | | 📦 Archive | Saves to `memory/drafts-archive/archived/` | | ✅ Tasks | Adds to SESSION-STATE.md as an active task | | ▶️ Run as Prompt | Prepares for execution; asks qualifying questions one at a time | ## File Structure ``` workspace/ ├── skills/draft-router/ │ ├── SKILL.md │ └── draft-router.js └── memory/ └── drafts-archive/ ├── archived/ # Archived drafts ├── prompts/ # Drafts marked for prompt execution └── processed/ # Knowledge additions ``` ## Callback Handling Callbacks use format: `draft:{id}:{action}` ```javascript // Parse callback callback_data.split(':') // ['draft', 'id', 'action'] // Execute const result = router.handleCallback(draftId, action); ``` ## Integration with AGENTS.md Add to your agent's routing logic: ```javascript // When message is forwarded or has draft content if (isForwarded || message.text.includes('#draft')) { const router = require('../skills/draft-router/draft-router.js'); const result = router.handleDraft(message.text, message.from); return { message: result.text, buttons: result.buttons }; } ```


Security scan verdicts — ClawScan: suspicious | static analysis:  | VirusTotal: suspicious | SkillSpector: suspicious (CRITICAL)
Skill: yang1002378395-cmyk/openclaw-telegram-setup (version 1.0.0)

# OpenClaw Telegram Setup 10 分钟配置 Telegram Bot 作为 OpenClaw 消息渠道。 ## 为什么选 Telegram？ - **免费无限制**：消息、文件、多媒体全免费 - **API 开放**：Bot API 简单易用 - **全球可用**：无地域限制 - **功能强大**：支持命令、按钮、Inline 查询 ## 快速配置 ### Step 1: 创建 Bot 1. 在 Telegram 搜索 `@BotFather` 2. 发送 `/newbot` 3. 按提示设置 Bot 名称 4. 保存返回的 **Token**（格式：`123456789:ABCdefGHI...`） ### Step 2: 获取 Chat ID ```bash # 方法 1：用你的 Bot 发条消息，然后访问 https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates # 方法 2：用 @userinfobot 获取你的 ID ``` ### Step 3: 配置 OpenClaw 编辑 `~/.openclaw/config.yaml`: ```yaml plugins: entries: - plugin: openclaw-telegram config: botToken: "123456789:ABCdefGHI..." allowedChatIds: - 123456789 # 你的 Chat ID ``` ### Step 4: 启动 Gateway ```bash openclaw gateway start ``` ### Step 5: 测试 在 Telegram 向你的 Bot 发送消息，应该收到 AI 回复。 ## 高级功能 ### 群组支持 ```yaml plugins: entries: - plugin: openclaw-telegram config: botToken: "xxx" allowedChatIds: - 123456789 # 个人 - -100123456789 # 群组（负数） ``` ### 命令支持 在 BotFather 设置命令： ``` /setcommands help - 获取帮助 status - 检查状态 clear - 清除对话 ``` ### Webhook 模式（需要公网服务器） ```yaml plugins: entries: - plugin: openclaw-telegram config: botToken: "xxx" webhook: url: "https://your-domain.com/telegram/webhook" port: 8443 ``` ## 常见问题 ### Q: Bot 不回复 A: 检查 Chat ID 是否正确（正数是个人，负数是群组） ### Q: 提示 "Forbidden: bot was blocked by the user" A: 你可能之前屏蔽了 Bot，需要先解除屏蔽 ### Q: 群组消息无响应 A: 确保 Bot 在群组中，且有读取消息权限 ## 成本 - Telegram Bot API：**完全免费** - OpenClaw Gateway：本地运行，无费用 - AI 模型：按使用量计费（DeepSeek 最便宜） ## 需要帮助？ - 微信：yanghu_ai - Telegram: @yanghu_openclaw - 免费远程配置（首次） --- Version: 1.0.0 Created: 2026-03-21


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

--- name: lua-scripter description: > Expert Lua developer and scripter. Use this skill for ANY Lua-related request: writing scripts, fixing bugs, explaining code, OOP patterns, metatables, coroutines, modules, or Lua for specific platforms (Roblox/Luau, LÖVE2D, Neovim, OpenResty). Triggers on: "lua", "luau", "roblox script", "love2d", ".lua file", "lua error", "lua function", "lua table", "lua class", "lua coroutine", "lua metatable", "neovim plugin". Always use this skill whenever Lua is mentioned, even for simple questions. metadata: { "openclaw": { "emoji": "🦊" } } --- # Lua Scripter You are a **world-class Lua developer**. Write clean, idiomatic, well-commented Lua code and help the user understand it deeply. --- ## Rules - Always use `local` variables — never leak globals - Always add inline comments for non-obvious logic - When fixing bugs, explain what was wrong and why the fix works - For Roblox: always clarify if code goes in `Script` vs `LocalScript` vs `ModuleScript` - Keep responses concise — code speaks louder than paragraphs - Never use deprecated APIs (e.g. use `task.wait()` not `wait()` in Roblox) --- ## Code Style ```lua -- Always local local x = 10 -- String formatting over concatenation in loops local msg = string.format("Player %s has %d HP", name, hp) -- Error handling local ok, err = pcall(function() -- risky code end) if not ok then print("Error: " .. tostring(err)) end -- OOP pattern local MyClass = {} MyClass.__index = MyClass function MyClass.new(name) return setmetatable({ name = name }, MyClass) end function MyClass:greet() return "Hello, " .. self.name end ``` --- ## Platform Cheatsheet ### Roblox (Luau) - Use `game:GetService("Players")` etc. — never index game directly - `task.wait()`, `task.spawn()`, `task.delay()` — preferred over old APIs - `RemoteEvent` / `RemoteFunction` for client↔server comms - `Players.LocalPlayer` — LocalScript only ### LÖVE2D - Structure: `love.load()` → `love.update(dt)` → `love.draw()` - Input: `love.keypressed(key)`, `love.mousepressed(x, y, btn)` ### Neovim - Use `vim.keymap.set`, `vim.opt`, `vim.api.*` - Module pattern: `local M = {} ... return M` ### OpenResty - Use `ngx.say`, `ngx.req`, `ngx.thread.spawn` for async --- ## Debugging Checklist 1. Read the error — Lua includes file + line number 2. Check for `nil` access — most common crash 3. Check `local` vs global scope 4. Use `print(type(x), x)` to inspect unknowns 5. Wrap risky code in `pcall` to catch runtime errors


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: ckchzh/baby-guide (version 2.0.0)

--- version: "2.0.0" name: Baby Guide description: "育儿指南。按月龄发育指标、辅食添加、早教建议、疫苗提醒。. Use when you need baby guide capabilities. Triggers on: baby guide." 育儿指南助手。新生儿护理、辅食添加、疫苗接种、早教启蒙、睡眠训练、亲子互动。Baby care guide with feeding, vaccination, sleep training, early education. 育儿百科、宝宝成长、母婴护理。Use when parents need baby care advice. author: BytesAgain homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills --- # baby-guide 育儿指南。按月龄发育指标、辅食添加、早教建议、疫苗提醒。 ## Commands | 命令 | 说明 | |------|------| | `baby.sh milestone "月龄"` | 发育指标（身高体重/大运动/精细运动/语言/社交） | | `baby.sh food "月龄"` | 辅食添加指南 | | `baby.sh education "月龄"` | 早教建议与亲子活动 | | `baby.sh vaccine "月龄"` | 疫苗接种提醒 | | `baby.sh help` | 显示帮助信息 | ## Usage 当用户询问宝宝发育、辅食、早教、疫苗等育儿话题时，使用对应命令。 **示例：** ```bash # 6个月宝宝发育指标 bash scripts/baby.sh milestone "6" # 8个月辅食添加指南 bash scripts/baby.sh food "8" # 12个月早教建议 bash scripts/baby.sh education "12" # 3个月疫苗提醒 bash scripts/baby.sh vaccine "3" ``` 将脚本输出作为参考，提醒用户具体情况请咨询儿科医生。 --- 💬 Feedback & Feature Requests: https://bytesagain.com/feedback Powered by BytesAgain | bytesagain.com - Run `baby-guide help` for all commands


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: liwiw/runtime-monitor (version 1.0.0)

--- name: runtime-monitor description: AI 代理运行时 I/O 安全监控 - 检测提示注入、数据外泄、危险命令 --- # Runtime Monitor Skill 运行时 I/O 安全监控模块，保护 AI 代理免受安全威胁。 ## 功能 - **提示注入检测**：识别恶意注入模式 - **数据外泄检测**：监控敏感数据传输 - **危险命令检测**：拦截高风险系统命令 ## 使用场景 **使用此技能当：** - 需要监控工具调用的输入/输出安全 - 检测潜在的安全攻击 - 审计 AI 代理行为 ## 风险等级 | 等级 | 说明 | |------|------| | LOW | 低风险，正常操作 | | MEDIUM | 中等风险，需关注 | | HIGH | 高风险，建议拦截 | | CRITICAL | 严重风险，立即阻止 | ## 集成方式 ```python from runtime_monitor import RuntimeMonitor monitor = RuntimeMonitor() result = monitor.detect(tool_call) ``` ## 最佳实践 1. 所有外部调用前进行风险评估 2. 定期更新检测规则 3. 记录所有安全事件到审计日志


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