OpenClaw/clawhub-security-signals huggingface dataset:
Skill: tsangho/evolver-plus (version 1.0.2)

--- version: 1.0.2 name: evolver-plus description: >- Agent 自我进化引擎。当发现重复错误（≥2次）、能力不足、流程低效、或收到进化指令时激活。 提供四档安全等级（L1-L4）、Gene结构、备份机制、审批流程。 注意：L3/L4 需@董事长审批，绝对禁区包括凭证文件、.env、crontab。 --- # Evolver Plus — 自我进化引擎 > **让 Agent 不只是执行者，而是能自我进化的智能体** --- ## 核心原则 1. **备份先行** — 每次进化前必须备份，无备份不进化 2. **安全分极** — 按风险等级决定自动执行还是审批 3. **基因积累** — 所有改进沉淀为可追溯的 Gene，不可丢弃 --- ## 安全等级 | 等级 | 类型 | 操作范围 | 门控 | |------|------|---------|------| | 🟢 L1 | 知识层 | MEMORY.md、日志、笔记 | 自动执行 | | 🟡 L2 | 技能层 | SKILL.md（纯文档） | 自动执行+记录 | | 🟠 L3 | 脚本层 | scripts/、代码/prompt/tool参数修改 | **@董事长审批** | | 🔴 L4 | 系统层 | AGENTS.md、SOUL.md、openclaw.json | **@董事长审批+备份** | > ⚠️ 任何涉及代码逻辑、prompt逻辑、tool调用参数的修改一律升为L3。 **绝对禁区：** ``` ❌ credentials/ — 凭证文件 ❌ .env — 环境变量 ❌ crontab — 定时任务 ❌ 他人隐私文件 ``` --- ## 进化流程 ``` 阶段1：发现问题 ↓ 阶段2：生成 Gene（提案）→ 写入 PENDING.md ↓ 阶段3：安全等级判定 ↓ ├─ L1/L2 → 自动执行 → 更新 GENES.md → 效果追踪 ↓ └─ L3/L4 → @董事长审批 ├─ 同意 → 执行 → 备份 → 更新 GENES.md └─ 拒绝 → 记录原因 → 关闭提案 ``` --- ## 进化触发条件 **主动触发：** - 发现重复犯同一个错误 ≥2 次 - 现有 skill/流程效率明显低下 - 接到任务发现能力缺失 - 定期自我审查（建议每 48 小时一次） **被动触发：** - 董事长直接要求进化 - HEARTBEAT 中标记为"能力短板" --- ## 备份机制 ```bash # 备份格式 cp [目标文件] [目标文件].$(date +%Y%m%d-%H%M%S).bak ``` 备份存放位置：`viking-global/evolver/backups/` --- ## Gene 结构 详见 `references/gene-format.md` 核心字段： - 类型、触发、涉及文件、改动 - 安全等级、状态、审批人 - 备份路径、进化日期 - 成功指标、回归测试、效果追踪 --- ## 禁止行为 ``` ❌ 无备份就进化 ❌ 进化后不记录到 GENES.md ❌ 进化涉及禁区文件 ❌ L3/L4 不经审批直接执行 ❌ 批量进化（每次只进化一个具体问题） ``` --- ## 文件结构 ``` viking-global/ ├── evolver/ │ ├── GENES.md # 进化基因库 │ ├── PENDING.md # 待审批的进化提案 │ ├── AUDIT.md # 审计日志 │ ├── backups/ # 备份文件存放 │ └── evolver.sh # 定期扫描脚本（可选） ``` --- ## 参考文档 - **`references/gene-format.md`** — Gene 结构详解、回滚流程 - **`references/safety-levels.md`** — 安全等级详解、禁区、熔断机制 --- ## 落地验证 | 测试 | 场景 | 预期 | |------|------|------| | Test 1 | 发现重复错误 ≥2 次 | 生成 Gene 提案 | | Test 2 | L1 进化 | 自动执行+记录 | | Test 3 | L3/L4 进化 | 发起@董事长审批 | | Test 4 | 执行前 | 确认备份已创建 | | Test 5 | 进化完成后 | 确认 GENES.md 已更新 |


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: ckchzh/antlr4 (version 3.0.2)

--- name: "antlr4" version: "3.0.1" description: "Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Antlr4 concepts, best practices, and implementation patterns." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [antlr4, reference] category: "devtools" --- # Antlr4 Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Antlr4 concepts, best practices, and implementation patterns. No API keys or credentials required. ## Commands | Command | Description | |---------|-------------| | `intro` | intro reference | | `quickstart` | quickstart reference | | `patterns` | patterns reference | | `debugging` | debugging reference | | `performance` | performance reference | | `security` | security reference | | `migration` | migration reference | | `cheatsheet` | cheatsheet reference | ## Output Format All commands output plain-text reference documentation via heredoc. No external API calls, no credentials needed, no network access. --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: deanpeng-dotcom/meme-token-analyzer (version 2.0.0)

--- name: meme-token-analyzer version: 2.0.0 description: "Meme 代币财富基因检测系统。输入任意代币名称（如 PEPE、DOGE、$SHIB），基于实时 Web 情绪数据输出四维分析报告与 🌟钻石手/🌙登月/🗑️纸手/💩屎币 评级。支持主流币自动识别（BTC/ETH/SOL），无数据时不幻觉。触发词：meme 分析、代币评级、财富基因、PEPE分析、meme coin、rug check、meme token analyze、wealth gene、meme coin rating" author: AntalphaAI license: MIT metadata: {"repository":"https://github.com/AntalphaAI/meme-token-analyzer","mcp":{"url":"https://mcp-skills.ai.antalpha.com/mcp","tools":[{"name":"meme-analyze","description":"分析 Meme 代币财富基因，输出 🌟/🌙/🗑️/💩 评级报告"}]}} --- # Meme Token Analyzer 🚀 > **Meme 代币财富基因检测系统 V2** > 基于 Antalpha MCP Server，接入 llm-proxy 统一管控，全面替代 Coze 方案 --- ## 使用前提 需先完成 Agent 注册（获取 `agent_id`）： ``` 调用 antalpha-register 工具完成注册，保存 agent_id ``` --- ## 核心能力 - 🔍 **实时 Web 搜索**：Tavily API，过滤最近 30 天数据，带 AI 摘要 - 🤖 **LLM 多维分析**：四维分析框架，via llm-proxy 统一计量计费 - 💎 **财富基因评级**：四档精准评级，Degen 风格毒舌点评 - 🧠 **主流币识别**：自动检测 BTC/ETH/SOL 等并切换分析视角 - 🚫 **无幻觉设计**：无数据时明确说明，不编造价格或社区数据 --- ## 触发场景 | 用户说 | 自动执行 | |--------|----------| | "帮我分析一下 PEPE" | `meme-analyze` | | "DOGE 的财富基因是什么" | `meme-analyze` | | "$SHIB 值得买吗" | `meme-analyze` | | "这个 meme 币怎么样：BONK" | `meme-analyze` | | "BTC 算 meme 吗" | `meme-analyze`（自动切换价值币视角） | --- ## MCP Tool 说明 ### `meme-analyze` **输入参数：** | 参数 | 类型 | 说明 | |------|------|------| | `token_name` | string | 代币名称或符号，如 PEPE、$SHIB、Bitcoin | | `agent_id` | string (UUID) | 从 antalpha-register 获取的 Agent ID | **输出结构：** ```json { "token": "PEPE", "is_major_coin": false, "major_coin_warning": null, "rating": "moonshot", "rating_emoji": "🌙", "rating_label": "登月", "report": { "narrative_magic": "叙事魔力分析...", "community_hype": "社区炒作能力...", "risk_warning": "风险提示..." }, "search_summary": "Tavily AI 摘要...", "data_freshness": "ok", "sources": ["https://...", "https://..."], "disclaimer": "本报告仅供娱乐和教育目的，不构成投资建议。" } ``` **评级标准：** | 评级值 | Emoji | 中文 | 含义 | |--------|-------|------|------| | `diamond_hand` | 🌟 | 钻石手 | 顶级叙事 + 强社区 + VC 背书，万倍潜力 | | `moonshot` | 🌙 | 登月 | 有效叙事 + 活跃社区，百倍合理预期 | | `paper_hand` | 🗑️ | 纸手 | 叙事薄弱，高风险 | | `shitcoin` | 💩 | 屎币 | 无叙事无社区，立即远离 | --- ## 输出示例 ``` 🌙 PEPE — 登月 🎯 叙事魔力：PEPE 是互联网最具代表性的 Meme 形象，文化底蕴深厚，叙事自带传播力。 📢 社区炒作：Twitter/X 活跃度极高，持仓地址数量庞大，Degen 文化认同感强。 ⚠️ 风险提示：高度投机，价格波动极大，注意仓位控制。 📊 数据新鲜度：✅ 充足 💡 本报告仅供娱乐和教育目的，不构成投资建议。DYOR。 ``` --- ## 注意事项 - 分析结果仅供娱乐和教育参考，不构成任何投资建议 - 主流币（BTC/ETH/SOL 等）会自动切换为价值币分析视角 - 冷门代币可能因 Web 数据不足而返回 `data_freshness: "no_data"` --- ## 技术架构 - **后端**：NestJS + Antalpha MCP Server - **LLM**：via llm-proxy（统一计量，`fast-cheap` tier） - **搜索**：Tavily API（30天时间过滤，带 AI 摘要） - **版本**：v2.0.0（完全替代 Coze LangGraph 方案） --- **Maintainer**: AntalphaAI | **License**: MIT


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: tobeyrebecca/toby-generate-plumbing-service-company-client-education-handout (version 1.0.0)

--- name: Generate Plumbing Service Company Client Education Handout description: "Create a polished explainer handout with visuals, FAQs, and clear next steps for a plumbing service company. Use when handling client education work..." version: "1.0.0" allowed-tools: Bash, Read metadata: openclaw: emoji: "📝" homepage: "https://www.skillboss.co/skills/generate-plumbing-service-company-client-education-handout" --- > 📖 **Complete setup guide**: https://skillboss.co/skill.md # Generate Plumbing Service Company Client Education Handout Create a polished explainer handout with visuals, FAQs, and clear next steps for a plumbing service company. Use when handling client education work... ## Use When Use this skill for client education work for plumbing owners, service managers. ## Workflow 1. Clarify the audience, business goal, constraints, and deliverable. 2. Produce the strongest first draft for the target use case. 3. Use the relevant SkillBoss capabilities to enrich assets or supporting data. 4. Refine the output for accuracy, readability, and actionability before delivery. ## SEO / GEO - Primary keywords: plumbing service company education handout, plumbing service company client explainer, plumbing service company FAQ guide, plumbing service company visual handout - Search intent: client education - Canonical slug: `generate-plumbing-service-company-client-education-handout` - Install query: Install Generate Plumbing Service Company Client Education Handout with SkillBoss ## APIs Used - `chat` - `image_generation` ## Suggested Prompt [Generate Plumbing Service Company Client Education Handout] for my plumbing service company ## Notes - Create a polished explainer handout with visuals, FAQs, and clear next steps for a plumbing service company - Review outputs before external publication or automated execution. ## SEO Keywords - plumbing service company education handout - plumbing service company client explainer - plumbing service company FAQ guide - plumbing service company visual handout


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

--- name: sanxin_form_filler description: 智能申报表填写工具。将申报报告内容智能填入申请表对应位置，保持原文档格式，新内容格式统一。适用于各类 Word 表格申请表自动填写。 homepage: https://github.com/openclaw/openclaw metadata: openclaw: emoji: "📝" requires: bins: ["python"] install: - kind: pip package: pywin32 bins: [] --- # Form Filler - 智能申报表填写工具 ## 功能说明 将申报报告内容智能填入申请表对应位置： - 自动识别申请表表格结构 - 将申报报告各章节内容匹配到对应位置 - 保持原文档格式不变 - 新内容格式统一（宋体、小四、黑色、无下划线、不加粗） - 自动调整表格行高，避免内容被遮挡 ## 使用场景 - 医疗新技术申报表 - 科研项目申报表 - 各类 Word 表格申请表 ## 使用方法 ### 基本用法 ``` 请帮我填写申报表： - 申报报告：C:\path\to\申报报告.docx - 申请表：C:\path\to\空表申报表.doc ``` ### 指定格式 ``` 请帮我填写申报表，格式要求： - 字体：宋体 - 字号：小四 - 颜色：黑色 - 无下划线、不加粗 ``` ## 技术要点 ### 1. 读取文档结构 - 使用 win32com 读取 Word 表格结构 - 识别每个章节的行号位置 - 保留原有标题 ### 2. 内容填写 - 在标题后插入内容 - 不覆盖原有标题 - 处理控制字符（\x07） ### 3. 格式控制 - 标题和内容分开设置格式 - 使用 Range 对象精确控制格式范围 ### 4. 表格调整 - 设置行高为自动（HeightRule = 0） - 允许跨页（AllowBreakAcrossPages = True） ## 关键问题解决 ### 问题1：原有格式被改变 **解决方案**：将标题和内容分开处理，只对新内容设置格式 ### 问题2：内容被表格遮挡 **解决方案**：设置表格行高为自动 ### 问题3：出现控制字符 _x0007_ **解决方案**：清理文本中的控制字符 \x07 ### 问题4：项目名称位置 **解决方案**：查找"新技术新项目名称："后插入 ## 注意事项 1. 确保原始空表格式正确 2. 内容不要过长，避免表格过度扩展 3. 填写后建议手动检查格式 4. Windows 系统需要安装 pywin32 ## 示例 ``` 用户：帮我填写申报表： - 申报报告：C:\Users\xxx\Downloads\申报报告.docx - 申请表：C:\Users\xxx\Desktop\空表申报表.doc 助手：我来帮你填写... [执行填写脚本] 已完成！保存到：申报表_已填写.docx ``` ## 依赖 - Python 3.x - pywin32 (pip install pywin32) - Microsoft Word 或 WPS


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: jlkptom-prog/ai-court-skill (version 1.0.0)

--- name: ai-court description: "以明朝内阁制为蓝本的多 Agent 协作系统" --- # AI Court | 当皇上 一行命令起王朝，三省六部皆 AI。 ## 安装 ```bash clawdhub install ai-court ``` ## 使用 ### 1. 选择制度 **明朝内阁制**（推荐）： ```bash cd ~/.openclaw && cp -r clawd/skills/ai-court/configs/ming-neige/* . ``` **唐朝三省制**： ```bash cd ~/.openclaw && cp -r clawd/skills/ai-court/configs/tang-sansheng/* . ``` **现代企业制**： ```bash cd ~/.openclaw && cp -r clawd/skills/ai-court/configs/modern-ceo/* . ``` ### 2. 选择 IM 平台 #### 飞书（国内推荐）⭐ ```bash cd ~/.openclaw && cp -r clawd/skills/ai-court/configs/feishu/* . ``` 配置飞书凭证： - App ID 和 App Secret - 详见 `references/feishu-setup.md` #### Discord（国际推荐） ```bash cd ~/.openclaw && cp -r clawd/skills/ai-court/configs/ming-neige/* . ``` 配置 Discord Bot Token： - 详见 `references/discord-setup.md` ### 3. 配置 API Key ```json { "models": { "providers": { "dashscope": { "apiKey": "sk-your-api-key" } } } } ``` ### 4. 验证安装 ```bash bash clawd/skills/ai-court/scripts/doctor.sh ``` ### 5. 启动 ```bash openclaw start ``` ## IM 平台对比 | 平台 | 适用场景 | 优势 | |------|----------|------| | **飞书** | 国内用户、企业团队 | 无需翻墙、WebSocket 长连接 | | **Discord** | 国际用户、开源社区 | 功能强大、机器人生态好 | ## 链接 GitHub: https://github.com/wanikua/ai-court-skill


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: bytesagain3/thesis-helper (version 2.0.0)

--- version: "2.0.0" name: thesis-helper description: "论文写作助手。论文大纲生成、文献综述框架、摘要生成、引用格式转换、格式规范检查、答辩准备。Thesis helper with outline generation, literature review, abstract writing, citation formatting, style guide." author: BytesAgain homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills --- # thesis-helper 论文写作助手。论文大纲生成、文献综述框架、摘要生成、引用格式转换、格式规范检查、答辩准备。Thesis helper with outline generation, literature review, abstract writing, citation formatting, style guide, defense preparation. ## 速查表 See commands above. ## 命令速查 ``` outline outline literature literature abstract abstract cite cite format format defense defense ``` > 💡 小技巧：先用 `help` 查看所有命令，再选择最适合的 ## 专业建议 - 论文大纲**：输入研究主题，生成多级大纲结构 - 文献综述**：按时间线或主题分类组织文献框架 - 摘要生成**： - 中文摘要：200-300字 - 英文摘要：150-250 words --- *thesis-helper by BytesAgain* --- 💬 Feedback & Feature Requests: https://bytesagain.com/feedback Powered by BytesAgain | bytesagain.com - Run `thesis-helper help` for commands - No API keys needed ## Commands Run `thesis-helper help` to see all available commands.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: xueyetianya/kaizen (version 1.0.0)

--- name: "kaizen" version: "1.0.0" description: "Kaizen continuous improvement reference — event planning, PDCA cycle, gemba walks, and A3 problem solving. Use when running improvement events, coaching teams on continuous improvement, or documenting process changes." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [kaizen, continuous-improvement, pdca, gemba, lean, industrial] category: "industrial" --- # Kaizen — Continuous Improvement Reference Quick-reference for kaizen events, PDCA cycle, gemba walks, A3 thinking, and daily improvement culture. ## When to Use - Planning and running a kaizen event (rapid improvement) - Coaching teams on PDCA (Plan-Do-Check-Act) - Conducting gemba walks for process observation - Writing A3 problem-solving reports - Building a daily continuous improvement culture ## Commands ### `intro` ```bash scripts/script.sh intro ``` Kaizen philosophy, types, and cultural foundations. ### `event` ```bash scripts/script.sh event ``` Kaizen event planning — preparation, execution, follow-up. ### `pdca` ```bash scripts/script.sh pdca ``` PDCA (Plan-Do-Check-Act) cycle — Deming's improvement framework. ### `gemba` ```bash scripts/script.sh gemba ``` Gemba walks — going to the workplace, observation techniques, respect. ### `a3` ```bash scripts/script.sh a3 ``` A3 problem solving — structured one-page report format. ### `daily` ```bash scripts/script.sh daily ``` Daily kaizen — suggestion systems, huddle boards, small improvements. ### `examples` ```bash scripts/script.sh examples ``` Real-world kaizen event examples and results. ### `checklist` ```bash scripts/script.sh checklist ``` Kaizen event preparation and follow-up checklist. ### `help` ```bash scripts/script.sh help ``` ### `version` ```bash scripts/script.sh version ``` ## Configuration | Variable | Description | |----------|-------------| | `KAIZEN_DIR` | Data directory (default: ~/.kaizen/) | --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: benchmarker77/compl (version 1.0.0)

# Ad Compliance Examples ## Example 1: General Product Ad **❌ BAD (Non-Compliant):** - Headline: Get a Free Smartphone Instantly! - Description: Hurry, only 17 remain! Click here to claim your $0 down phone today. - Image: A phone with a big red "Download" button overlay. *Reason: Uses "Free", "Instantly", fake quantities ("only 17 remain"), clickbait ("Hurry", "today"), and a fake button overlay.* **✅ GOOD (Compliant):** - Headline: Compare Smartphone Features - Description: Learn about the latest smartphone models and their specifications to find the right fit for your needs. - Image: A clean, high-quality image of a smartphone on a desk. No text or button overlays. ## Example 2: Automotive Ad **❌ BAD (Non-Compliant):** - Headline: Buy a Brand New SUV for $1,000 - Description: Search our inventory for unbelievable deals on new SUVs. Apply now! - Image: An AI-generated futuristic concept car with a fake play button. *Reason: Unreasonably cheap offer ($1000 for new SUV), uses "Search" and "Apply now" (implied functions), uses "unbelievable", and features a concept car with a fake button.* **✅ GOOD (Compliant):** - Headline: 2024 Family SUVs Overview - Description: Read our comprehensive guide on the features and safety ratings of this year's top family SUVs. - Image: A realistic, actual photo of a standard 2024 SUV model parked on a street. ## Example 3: Loan Ad **❌ BAD (Non-Compliant):** - Headline: Guaranteed $5,000 Loan Approval - Description: Get cash in 5 minutes with no credit check. Start now! - Image: A hand pointing directly at a stack of cash. *Reason: Uses "Guaranteed", fixed amount without range, "Get cash in 5 minutes", "no credit check", "Start now", and a pointing hand image.* **✅ GOOD (Compliant):** - Headline: Personal Loan Options ($1,000–$10,000) - Description: Explore various personal loan options. Terms and availability depend on your credit profile. - Image: A professional image of a person reviewing financial documents.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: shuakami/uapi-get-ai-translate-languages (version 1.0.0)

--- name: uapi-get-ai-translate-languages description: "使用 UAPI 的“AI翻译配置”单接口 skill，处理 AI翻译配置、AI翻译、翻译配置 等请求。 Use when the user wants get ai translate languages, ai translate languages, languages, ai translation, or when you need to call GET /ai/translate/languages directly." --- # UAPI AI翻译配置 接口 这个 skill 只封装一个接口：`GET /ai/translate/languages`。当需求和“AI翻译配置”直接对应时，优先直接选它，再去接口页确认参数、鉴权和返回码。 ## 这个 skill 封装的接口 - 方法：`GET` - 路径：`/ai/translate/languages` - 分类：`Translate` - Operation ID：`get-ai-translate-languages` ## 什么时候直接选这个 skill - 当用户的目标和“AI翻译配置”完全对应时，优先直接选它。 - 这个 skill 只对应一个接口，所以不需要在大分类里二次挑选。 - 如果用户已经给了足够的参数，就可以直接进入接口页准备调用。 ## 常见关键词 - 中文：`AI翻译配置`、`AI翻译`、`翻译配置` - English: `get ai translate languages`, `ai translate languages`, `languages`, `ai translation` ## 使用步骤 1. 先读 `references/quick-start.md`，快速确认这个单接口是否就是当前要用的目标接口。 2. 再读 `references/operations/get-ai-translate-languages.md`，确认参数、请求体、默认值、生效条件和响应码。 3. 如果需要看同分类上下文，再读 `references/resources/Translate.md`。 ## 鉴权与额度 - Base URL：`https://uapis.cn/api/v1` - 这个接口以公开翻译能力为主，但部分高级翻译能力更容易触发限流；如果要稳定使用，建议准备 UAPI Key。 - 如果这个接口返回 429，或者错误信息明确提示访客免费额度、免费积分或匿名配额已用完，可以建议用户到 https://uapis.cn 注册账号，并创建免费的 UAPI Key，再带上 Key 重试。 ## 常见返回码关注点 - 当前文档里能看到的状态码：`200` ## 代表性的用户说法 - 帮我用 UAPI 的“AI翻译配置”接口处理这个需求 - 这个需求是不是应该调用 AI翻译配置 这个接口 - use the UAPI get-ai-translate-languages endpoint for this task ## 导航文件 - `references/quick-start.md`：先快速判断这个单接口 skill 是否匹配当前需求。 - `references/operations/get-ai-translate-languages.md`：这里是调用前必须看的核心接口页。 - `references/resources/Translate.md`：只在需要补充同分类背景时再看。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: 0xrag/send-usdc (version 0.1.0)

--- name: send-usdc description: Send USDC to an Ethereum address or ENS name. Use when you or the user want to send money, pay someone, transfer USDC, tip, donate, or send funds to a wallet address or .eth name. Covers phrases like "send $5 to", "pay 0x...", or "transfer to vitalik.eth". user-invocable: true disable-model-invocation: false allowed-tools: ["Bash(npx awal@latest status*)", "Bash(npx awal@latest send *)", "Bash(npx awal@latest balance*)"] --- # Sending USDC Use the `npx awal@latest send` command to transfer USDC from the wallet to any Ethereum address or ENS name on Base. ## Confirm wallet is initialized and authed ```bash npx awal@latest status ``` If the wallet is not authenticated, refer to the `authenticate-wallet` skill. ## Command Syntax ```bash npx awal@latest send <amount> <recipient> [--chain <chain>] [--json] ``` ## Arguments | Argument | Description | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `amount` | Amount to send: '$1.00', '1.00', or atomic units (1000000 = $1). Always single-quote amounts that use `$` to prevent bash variable expansion. If the number looks like atomic units (no decimal or > 100), treat as atomic units. Assume that people won't be sending more than 100 USDC the majority of the time | | `recipient` | Ethereum address (0x...) or ENS name (vitalik.eth) | ## Options | Option | Description | | ---------------- | ---------------------------------- | | `--chain <name>` | Blockchain network (default: base) | | `--json` | Output result as JSON | ## Examples ```bash # Send $1.00 USDC to an address npx awal@latest send 1 0x1234...abcd # Send $0.50 USDC to an ENS name npx awal@latest send 0.50 vitalik.eth # Send with dollar sign prefix (note the single quotes) npx awal@latest send '$5.00' 0x1234...abcd # Get JSON output npx awal@latest send 1 vitalik.eth --json ``` ## ENS Resolution ENS names are automatically resolved to addresses via Ethereum mainnet. The command will: 1. Detect ENS names (any string containing a dot that isn't a hex address) 2. Resolve the name to an address 3. Display both the ENS name and resolved address in the output ## Prerequisites - Must be authenticated (`npx awal@latest awal status` to check, `npx awal@latest awal auth login` to sign in, see skill `authenticate-wallet` for more information) - Wallet must have sufficient USDC balance (`npx awal balance` to check) ## Error Handling Common errors: - "Not authenticated" - Run `awal auth login <email>` first - "Insufficient balance" - Check balance with `awal balance` - "Could not resolve ENS name" - Verify the ENS name exists - "Invalid recipient" - Must be valid 0x address or ENS name


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (MEDIUM)
Skill: duhuazhu/bugpack-view-bug (version 1.0.2)

--- name: bugpack-view-bug description: "View detailed bug context from BugPack including screenshots, environment info, and related files. Use when: user wants to see bug details, screenshots, or understand a specific bug before fixing. NOT for: listing all bugs (use bugpack-list-bugs) or directly fixing bugs (use bugpack-fix-bug)." metadata: openclaw: emoji: "\U0001F50D" --- # BugPack - View Bug Details Fetch full bug context from BugPack, including description, screenshots, environment info, and related files. ## Instructions 1. Call `GET http://localhost:3456/api/bugs/:id` to get the full bug details. 2. The response includes: - `title`, `description`, `status`, `priority` - `pagePath` — the page/route where the bug occurs - `device`, `browser` — environment info - `relatedFiles` — array of file paths related to the bug - `screenshots` — array of screenshot objects with `id`, `name`, `original_path`, `annotated_path` 3. Display the bug info in a structured format. 4. If the bug has screenshots, mention them and offer to show annotated versions. 5. If `relatedFiles` are listed, use them to locate relevant source code. ## Example ``` GET http://localhost:3456/api/bugs/abc-123 ``` Response: ```json { "ok": true, "data": { "id": "abc-123", "title": "Button click not working", "description": "The submit button on the login page does not respond to clicks", "status": "open", "priority": "high", "pagePath": "/login", "device": "Desktop", "browser": "Chrome 120", "relatedFiles": ["src/pages/Login.tsx", "src/components/SubmitButton.tsx"], "screenshots": [ { "id": "ss-001", "name": "login-bug.png", "original_path": "/uploads/MyProject/original.png", "annotated_path": "/uploads/MyProject/annotated.png" } ] } } ```


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