OpenClaw/clawhub-security-signals huggingface dataset:
Skill: ivangdavila/bar-exam (version 1.0.0)

--- name: Bar Exam slug: bar-exam version: 1.0.0 description: Prepare for the US Bar Exam with MBE practice, essay drilling, weak area targeting, and jurisdiction planning. metadata: {"clawdbot":{"emoji":"⚖️","requires":{"bins":[]},"os":["linux","darwin","win32"]}} --- ## When to Use User is preparing for a US Bar Exam. Agent becomes a comprehensive prep assistant handling practice scheduling, score tracking, essay feedback, and jurisdiction-specific planning. ## Quick Reference | Topic | File | |-------|------| | Exam structure by jurisdiction | `exam-format.md` | | MBE subjects and strategies | `mbe.md` | | MEE essay techniques | `mee.md` | | MPT performance tasks | `mpt.md` | | Progress tracking system | `tracking.md` | | User type adaptations | `user-types.md` | ## Data Storage User data lives in `~/bar-exam/`: ``` ~/bar-exam/ ├── profile.md # Jurisdiction, test date, law school, baseline ├── subjects/ # Per-subject progress (7 MBE subjects) ├── essays/ # Essay drafts with feedback ├── practice/ # Practice test results and analysis ├── outlines/ # Subject outlines and mnemonics └── feedback.md # What study methods work ``` ## Core Capabilities 1. **Diagnostic assessment** — Establish baseline MBE percentage, identify weak subjects 2. **MBE drilling** — Adaptive practice questions by subject and difficulty 3. **Essay feedback** — Score MEE essays using IRAC structure and issue spotting 4. **MPT practice** — Simulate closed-universe performance tasks with timing 5. **Progress tracking** — Monitor scores by subject, essay scores, overall trajectory 6. **Jurisdiction planning** — UBE vs state-specific requirements, score thresholds 7. **Schedule optimization** — Distribute study across subjects based on ROI ## Decision Checklist Before creating study plan, gather: - [ ] Target jurisdiction and passing score - [ ] Test date and weeks remaining - [ ] Law school graduation date (or retake history) - [ ] Current estimated MBE percentage - [ ] UBE jurisdiction or state-specific format - [ ] Taking bar prep course? (Barbri, Themis, etc.) - [ ] User type (first-timer, retaker, attorney transfer, international) ## Critical Rules - **MBE is pass/fail territory** — Most failures come from weak MBE, prioritize it - **50/50 MBE-essay split** — Don't over-focus on one at expense of other - **Issue spotting beats memorization** — Essays test recognition, not recall - **IRAC is mandatory** — Every essay answer uses Issue, Rule, Analysis, Conclusion - **Track by subject** — Overall percentage hides where points are lost - **Jurisdiction thresholds vary** — 266 UBE in NY ≠ 270 in DC - **Retakers need diagnosis** — Don't repeat the same prep that failed - **MPT is learnable** — Most underestimate it; it's the easiest points


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: axelhu/goal-task (version 1.0.2)

--- name: goal-task description: "为目标创建 cron 任务。agent 收到消息后处理目标，完成后主动删除该 cron。适用于延迟处理、定时提醒等场景。" metadata: {"openclaw":{"emoji":"🎯","requires":{"anyBins":[]}}} --- # goal-task 为实现特定目标而创建的 cron 任务。agent 收到消息后处理目标，完成后主动删除 job。 ## 核心理念 - **以目标为导向**：创建时附带任务说明，agent 收到后明确知道要做什么 - **完成后自删除**：任务完成后 agent 必须主动调用 `delete_goal_task` 删除 job，否则 cron 永久残留 - **区别于 cron 参数**：cron 参数适合定时定点重复执行，goal-task 适合目标驱动的一次性任务 ## 使用流程 ### 1. 设置环境变量 ```bash export AGENT_SESSION_KEY="agent:<agentId>:feishu:group:<feishu_group_id>" ``` sessionKey 格式：`agent:<agentId>:feishu:group:<groupId>` - `<agentId>` — 当前 agent 的 ID（如 `main`、`qa`、`producer`） - `<feishu_group_id>` — 飞书群 ID（从 MEMORY.md 获取） ### 2. 创建 goal task ```bash source goal-task.sh goal_task "<delay_minutes>" "<任务目标描述>" ``` **返回值**：jobId（UUID），供后续删除使用。 ### 3. 任务执行 agent 收到 cron 注入的 agentTurn 消息，按描述处理目标。 ### 4. 完成后删除 ```bash delete_goal_task "<jobId>" ``` **重要**：目标完成后必须删除 job。cron 本身不会自动删除，需要 agent 主动处理。 ## 示例 ### 持续跟进任务 ```bash # 持续跟进某个目标，定期提醒直到完成，完成后删除 cron export AGENT_SESSION_KEY="agent:main:feishu:group:oc_xxxxxxxxxxxxxxxx" source goal-task.sh # 创建 goal task，agent 会收到“跟进 M2 美工进度”的消息 # agent 处理后（如果完成）调用 delete_goal_task 清理 cron # 如果未完成，agent 可以创建新的 goal task 继续提醒 job_id=$(goal_task "120" "跟进 M2 美工进度，所有素材完成后删除 cron") ``` ### 任务完成后删除 ```bash delete_goal_task [REDACTED_SECRET] ``` ## 错误处理 | 场景 | 表现 | |------|------| | `AGENT_SESSION_KEY` 未设置 | `ERROR: AGENT_SESSION_KEY not set` | | 创建失败 | `ERROR: failed to create goal-task` | | 删除失败（job 不存在） | 返回 `{"ok":true,"removed":false}` | | 删除成功 | 返回 `{"ok":true,"removed":true}` | ## 注意事项 1. **sessionTarget 格式**：`session:agent:<agentId>:feishu:group:<groupId>` 2. **gateway token**：从 `~/.openclaw/openclaw.json` 读取，脚本运行时自动获取 3. **job 手动删除**：这是设计选择——agent 主动删除确保任务确实完成后才清理，不会误删未完成的任务


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal:  | SkillSpector: suspicious (HIGH)
Skill: leooooooow/social-video-resizer (version 1.0.0)

--- name: social-video-resizer description: Adapt one social video into platform-ready aspect ratios and dimensions for TikTok, Reels, Shorts, feeds, stories, and ads without awkward stretching or lost focal points. Use when teams need fast cross-platform resize decisions. --- # Social Video Resizer 把一条社媒视频，快速变成多个平台可发的尺寸版本。 ## Problem it solves 同一条内容发不同平台时，尺寸要求经常不一样： - TikTok / Reels / Shorts 偏 9:16； - Feed、广告位、封面预览可能要 1:1、4:5、16:9； - 直接硬拉伸会让人物变形，直接裁切又容易切掉字幕、脸或产品。 这个 skill 的目标是： **在不破坏主体和关键信息的前提下，把一条视频适配成多个社媒平台可直接使用的尺寸版本。** ## Use when - 一条视频要同时发 TikTok、Instagram、YouTube Shorts、Facebook、X 等平台 - 需要在 9:16、1:1、4:5、16:9 等比例之间切换 - 需要决定 pad、crop 还是 scale 的最佳策略 ## Do not use when - 需要高级主体追踪或复杂智能重构镜头 - 视频内容本身构图太差，需要重新剪辑而非单纯改尺寸 ## Inputs - Source video file - Target platforms or ratios - Whether the priority is face, product, subtitles, or full-frame preservation - Optional output dimensions, file size limit, or ad placement requirements - Optional brand constraints such as background color or padding preference ## Workflow 1. 确认目标平台和尺寸要求。 2. 判断该用 crop、pad 还是 scale。 3. 优先保护人物、产品和字幕安全区域。 4. 输出一个或多个平台适配版本。 5. 说明每个版本的构图取舍和兼容性。 ## Output Return: 1. Target platform versions 2. Resize strategy per version 3. Output dimensions 4. Framing / subtitle safety notes 5. Additional recommended variants if useful ## Quality bar - 绝不拉伸变形人物或产品 - 重要字幕和产品展示尽量不被切掉 - 优先使用平台安全尺寸 - 清楚说明 crop 与 pad 的取舍 ## Resource See `references/output-template.md`.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: dennis-da-menace/agent-memory (version 1.0.0)

# AgentMemory Skill Persistent memory system for AI agents. Remember facts, learn from experience, and track entities across sessions. ## Installation ```bash clawdhub install agent-memory ``` ## Usage ```python from src.memory import AgentMemory mem = AgentMemory() # Remember facts mem.remember("Important information", tags=["category"]) # Learn from experience mem.learn( action="What was done", context="situation", outcome="positive", # or "negative" insight="What was learned" ) # Recall memories facts = mem.recall("search query") lessons = mem.get_lessons(context="topic") # Track entities mem.track_entity("Name", "person", {"role": "engineer"}) ``` ## When to Use - **Starting a session**: Load relevant context from memory - **After conversations**: Store important facts - **After failures**: Record lessons learned - **Meeting new people/projects**: Track as entities ## Integration with Clawdbot Add to your AGENTS.md or HEARTBEAT.md: ```markdown ## Memory Protocol On session start: 1. Load recent lessons: `mem.get_lessons(limit=5)` 2. Check entity context for current task 3. Recall relevant facts On session end: 1. Extract durable facts from conversation 2. Record any lessons learned 3. Update entity information ``` ## Database Location Default: `~/.agent-memory/memory.db` Custom: `AgentMemory(db_path="/path/to/memory.db")`

path: requirements.txt
content: # No external dependencies - just Python stdlib


path: src/__init__.py
content: """
AgentMemory - Persistent Memory for AI Agents
"""

from .memory import AgentMemory, Fact, Lesson, Entity, get_memory

__version__ = "1.0.0"
__all__ = ["AgentMemory", "Fact", "Lesson", "Entity", "get_memory"]


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: codenova58/lightroom (version 0.1.0)

--- name: lightroom description: 注册“Lightroom”技能；用于创作工具公开页面、模板能力、功能说明与帮助文档整理。 homepage: `https://www.adobe.com/products/photoshop-lightroom.html` metadata: {"clawdbot":{"emoji":"🎨"}} --- # Lightroom 用途与边界 - 面向公开官网、模板页、功能页、帮助中心与定价页的信息整理 - 不提供账号代操作、素材版权绕过、付费资源下载或接口调用能力 - 仅处理公开可见的模板、编辑能力、导出规格、帮助信息与套餐说明 关键入口 - 主页：https://www.adobe.com/products/photoshop-lightroom.html - 功能与模板：官网中的模板中心、创作能力、素材或编辑器说明入口 - 帮助与定价：帮助中心、版权说明、套餐页与更新说明入口 常见任务 - 模板类型、编辑能力、导出规格与协作能力整理 - 素材、版权、商用说明与帮助信息汇总 - 套餐、会员权益、限制条件与更新日志提取 数据字段 - 模板类型、编辑功能、导出格式、分辨率或规格、链接 - 版权说明、商用边界、帮助页、素材入口链接 - 套餐名称、价格、限制项、协作功能差异 自动化要点 - 优先使用官方模板页与帮助页，不依赖第三方教程作为事实来源 - 版权和商用说明必须保留原始链接，避免误用素材 - 不处理用户私有项目、未公开素材库或账号资产 示例流程 - 功能整理：访问 Lightroom 功能页 → 提取创作能力与导出规格 → 输出摘要 - 模板汇总：进入模板中心 → 抽取分类与代表入口 → 输出链接清单 - 权益整理：访问定价与版权页 → 提取套餐与商用边界 → 输出表格 合规提示 - 遵守平台规则、版权要求与账号安全要求 - 只整理公开信息，不输出敏感数据或非公开内容


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: nexscope/ebay-seller-tools (version 1.0.0)

# eBay Seller Tools Essential tools and software for eBay sellers. Listing tools, repricing, analytics, inventory management, shipping, and research tools to scale your eBay business. ## Capabilities - Listing creation and bulk editing tools - Repricing automation software comparison - Sales analytics and profit tracking - Inventory management and cross-platform sync - Shipping label and tracking tools - Product research and sourcing tools - eBay API integrations and automation - Free vs paid tool recommendations by seller level ## Install ```bash npx skills add nexscope/ebay-seller-tools ``` ## Usage Ask your AI agent: - "What tools do I need to scale my eBay business?" - "Compare eBay repricing tools and recommend the best one." - "Set up inventory management for my eBay store." ## 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: onealmeng/deduplicate-images (version 1.0.1)

--- name: 图片智能去重专业版 name-en: Image Deduplicator Pro description: 递归扫描全目录图片，自定义相似度，安全软删除至回收站，保留高清原图 description-en: Recursively scan all images, custom similarity, safely move duplicates to trash, keep high-quality originals version: 2.0.0 author: User homepage: https://clawhub.ai/ user-invocable: true disable-model-invocation: false license: Commercial metadata: { "openclaw": { "requires": { "bins": ["python3"], "pips": ["pillow>=10.0.0"] }, "os": ["darwin", "linux", "win32"], "emoji": "🖼️", "tags": ["image","deduplicate","photo","cleaner","recursive","tool","file management"] } } --- # 🖼️ 图片智能去重专业版 | Image Deduplicator Pro ## 核心功能 | Core Features ✅ 递归深度扫描：根目录+所有子文件夹全量图片检索 ✅ 自定义相似度：支持 0~100% 任意阈值设置 ✅ 安全软删除：仅移动文件，不删除任何源文件 ✅ 智能择优保留：优先留存高分辨率、大体积优质图片 ✅ 全格式兼容：支持 JPG/PNG/WebP/BMP/TIFF ✅ 跨平台运行：macOS / Windows / Linux 全系统适配 ✅ Recursive Deep Scan: Scan all images in root and subfolders ✅ Custom Similarity: 0~100% adjustable threshold ✅ Safe Soft-Delete: Only move files, never delete originals ✅ Smart Selection: Keep high-resolution & large-size images ✅ Full Format Support: JPG/PNG/WebP/BMP/TIFF ✅ Cross-Platform: Compatible with macOS/Windows/Linux ## 使用方法 | Usage ### AI 智能调用 | AI Agent 中文：帮我扫描 [文件夹路径] 下所有图片，使用 [相似度] 进行去重 English: Scan all images in [folder path] with [similarity] deduplication ### 命令行调用 | CLI ```bash # 中文示例 python3 {baseDir}/main.py --path "你的图片目录" --similarity 99.5 # English Example python3 {baseDir}/main.py --path "Your Image Folder" --similarity 99.5


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: luciorenovato/notion-mvp (version 1.0.0)

--- name: notion-mvp description: Create and list Notion tasks in a single database via Notion API. Use when the user asks to add tasks, list today tasks, or capture quick todos in Notion from chat. --- # notion-mvp Use this skill to write/read tasks across multiple Notion databases (aliases). ## Required env vars - `NOTION_TOKEN` (integration token, `secret_...`) - one of: - `NOTION_DATABASE_MAP` (JSON map alias -> database_id) - `NOTION_DATABASE_ID` (fallback default database) Example `NOTION_DATABASE_MAP`: ```json {"agenda":"db_id_1","tarefas":"db_id_2","crm":"db_id_3"} ``` ## Command wrapper Run: ```bash bash {baseDir}/scripts/notion_mvp.sh <command> [args] ``` Commands: - `add <alias> "<bloco>" [YYYY-MM-DD] [HH:MM] ["<local>"]` → create an item - defaults: `data=today`, `hora=09:00`, `local=""` - `today <alias>` → list items with `Data = today` - `query <alias> "<text>"` → search items by `Bloco` contains text - `aliases` → list configured aliases ## Expected database properties This skill expects these Notion properties in each target database: - `Bloco` (title) - `Data` (rich_text/text) - `Hora` (rich_text) - `Local` (rich_text) ## Usage pattern 1. Validate env vars and fail with clear message if missing. 2. Resolve the correct database alias (`agenda`, `tarefas`, etc.). 3. For schedule capture requests, call `add` with alias + Bloco/Data/Hora/Local. 4. For “hoje” / “today” requests, call `today <alias>`. 5. Return a concise summary after command output. ## Examples ```bash bash {baseDir}/scripts/notion_mvp.sh aliases bash {baseDir}/scripts/notion_mvp.sh add agenda "Ligar para dermatologista" 2026-02-14 10:00 "Barra" bash {baseDir}/scripts/notion_mvp.sh add tarefas "Consertar tela do celular" 2026-02-14 15:30 "Centro" bash {baseDir}/scripts/notion_mvp.sh today agenda bash {baseDir}/scripts/notion_mvp.sh query agenda "dermatologista" ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: redfox-data/wechat-rewrite (version 1.0.0)

--- name: wechat-rewrite description: 一位公众号爆款文案撰写专家。具有硬核的公众号文案功底，不管给你什么文案，你总能把该文案转化为一篇高阅读数的公众号文案，文案中必定会包含一些具有公众号特色的词汇。这个角色需要具备精通语言的能力，这个角色的任务是通过语言的艺术表达，使句子更加生动、吸引人、有趣和具有说服力。 --- # 公众号文案改写 ## 核心规则 **你的角度是文案发起者的角度，用户的文案就是你的文案，你回答的内容只是进行了公众号文案风格转换。** --- ## 一、行文原则（必须遵守） 1. **根据公众号爆款文章总结行为特征和内容**：深度分析爆款文章的结构、开头逻辑、互动话术 2. **深度挖掘爆款数据中的规律**：从公众号爆款文章中提炼标题规律、内容规律、互动规律 3. **标题要简单粗暴**：直击痛点，引发好奇，让读者忍不住点开 4. **给大家一种不看就有损失的感觉**：制造信息差和紧迫感，让读者觉得错过就是损失 5. **观点能颠覆常识**：能提供看待世界的新鲜角度，或对当下的生活态度有所启发 6. **能表达情感共鸣**：能体察人性的痛点，表达大众的情感共鸣 7. **能结合经历充实文章**：融入真实案例和个人故事，增加可信度和代入感 8. **文章跟"我"有关**：核心问题落实到读者的关联上，在读者的角度去思考问题 9. **文章对"我"有用**：提供实用价值，让读者觉得读完有收获 10. **文风足够有趣**：用幽默、犀利的方式表达，避免枯燥说教 --- ## 二、风格特点 - **态度鲜明**：犀利直接、一针见血，不含糊、不中庸 - **金句频出**：每个观点用一句核心金句总结，便于传播和记忆 - **对比强烈**：善用正反对比、数字对比、身份对比等手法 - **直击痛点**：洞察人性弱点，揭露问题本质 - **节奏紧凑**：短句为主，多用反问和排比，增强气势 - **引发思考**：结尾留白或抛出问题，激发读者讨论 --- ## 三、创作规范 ### 1. 标题创作（严格遵循爆款标题模式） - **必须参考**爆款数据中出现最多的标题结构 - 优先使用**数字型标题**（如："3个技巧"、"5天见效"） - 可使用疑问句引发好奇（如："为什么..."、"居然..."） - 可使用感叹句增强情绪（如："太绝了！"、"绝了！"） - **标题最多不超过20字**（包含标点符号，超出必须精简） ### 2. 正文创作（严格遵循爆款内容结构） - **必须融入**公众号爆款数据中出现的高频关键词 - **必须参考**公众号爆款内容的开头"钩子"手法（如：痛点共鸣、惊人数据、反差对比） - **必须保持**爆款内容的写作风格（如：口语化、亲切感、代入感） - **可融入**最新搜索到的热点/资讯作为素材补充（如有） - **结构参考**：分点说明、步骤教程、对比展示等 - **结尾引导**：添加引导互动的话术（如："你们觉得呢？"、"评论区告诉我"） - **排版**：良好分段，点缀少量 Emoji（每段 1-2 个），使用简短句子 - **Tags**：结尾添加 5-10 个相关标签 --- ## 四、必须携带 Keyword 从以下10个中选择2-3个，**自然融入正文**： | 序号 | Keyword | 示例 | |------|---------|------| | 1 | 指南 | XX指南、XX攻略、XX技巧 | | 2 | 教程 | XX教程、XX入门指南 | | 3 | 解析 | XX解析、XX详解 | | 4 | 秘籍 | XX秘籍、成功秘籍 | | 5 | 经验分享 | XX经验、XX心得 | | 6 | 挑战 | XX挑战、XX实战 | | 7 | 故事 | XX故事、人物故事 | | 8 | 案例分析 | XX案例、XX成功案例 | | 9 | 趋势预测 | XX趋势、未来趋势 | | 10 | 重要事件 | XX事件、行业事件 | --- ## 五、输出检查清单 改写完成后，逐项确认： - [ ] 标题不超过20字，有吸引力/钩子 - [ ] 携带2-3个Keyword，自然融入正文 - [ ] 口语化表达（亲切自然，避免书面语） - [ ] 态度鲜明，犀利直接 - [ ] 有金句，便于传播 - [ ] 段落结构清晰，分段良好 - [ ] 结尾有引导互动话术 - [ ] 末尾有Tags（5-10个，以#开头） - [ ] 点缀少量Emoji（每段1-2个） - [ ] 以作者身份输出（不说"帮你改写"） - [ ] 不询问用户，直接输出结果 --- ## 资源 - 规则文件：`assets/platform-rules.md` - 脚本：`scripts/rewrite.py`


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal:  | SkillSpector: suspicious (CRITICAL)
Skill: freemandigger/isdayoff-checker (version 1.0.0)

--- name: isdayoff-checker description: "Определяет, рабочий ли указанный день (по умолчанию — сегодня) с помощью API isdayoff.ru. Использовать, когда нужно быстро ответить «рабочий» или «выходной» для даты с учётом часового пояса." --- # isdayoff-checker Коротко: этот навык проверяет, является ли указанная дата рабочим днём или выходным, используя публичный API на https://www.isdayoff.ru/docs/. Когда использовать этот навык - Когда нужно ответить "рабочий" / "выходной" для заданной даты (если дата не указана — по умолчанию сегодня). - Когда нужно принять решение о планировании/напоминании, зависящее от типа дня (например, не ставить будильник на воскресенье). Что включено - scripts/check_day.py — исполняемый Python-скрипт, который по умолчанию обращается к публичному API isdayoff и возвращает удобочитаемый результат и код выхода. - references/ISDAYOFF.md — ссылка на документацию и краткие замечания по формату ответа. Примеры использования - Локально: python3 scripts/check_day.py - Для конкретной даты: python3 scripts/check_day.py --date 2026-04-13 - Опция --endpoint позволяет указывать альтернативный URL API (если документация поменялась). Примечания по безопасности и конфигурам - Скрипт использует прямой HTTP(S) вызов к стороннему сервису. Убедитесь, что машина имеет выход в интернет. - Если формат ответа API изменится, отредактируй scripts/check_day.py и/или references/ISDAYOFF.md. Автор: Домовенок Кузя (скелет навыка — можно адаптировать под ваши нужды)

path: references/ISDAYOFF.md
content: isdayoff.ru API notes

Source: https://www.isdayoff.ru/docs/

- Endpoint used: https://isdayoff.ru/api/getdata?date=YYYYMMDD
- Response: often a short text, sometimes CSV like "YYYYMMDD;0" or a single digit per date.
- Codes: 0 = working day, 1 = non-working day (holiday), 2 = weekend (varies by endpoint and country settings).
- If the API structure changes, update scripts/check_day.py accordingly.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: chipp11/angus-bounty-hunter (version 1.0.0)

--- name: bounty-hunter description: Automated smart contract bug bounty hunting. Scans Immunefi/Code4rena targets with Slither static analysis, triages findings with local LLMs, and generates PoC templates. Zero API cost for scanning phase. version: 1.0.0 --- # Bounty Hunter Automated smart contract vulnerability scanner for bug bounty programs. Uses free tools (Slither + local LLMs) for the heavy lifting, saves expensive models for PoC writing. ## Requirements - `slither-analyzer` (pip): Static analysis - `solc-select` (pip): Solidity compiler management - Node.js: For script execution - Optional: Ollama with any code model for local triage ## Quick Start ```bash # Scan a repo bash scripts/scan.sh <github-repo-url> [src-dir] # Triage findings (uses local LLM if available, otherwise prints raw) bash scripts/triage.sh <scan-output.json> # Generate PoC template for a finding bash scripts/poc-template.sh <finding-id> <contract-address> ``` ## Workflow 1. **Target Selection** — Check Immunefi/Code4rena for active programs 2. **Clone & Scan** — `scan.sh` clones the repo, installs solc, runs Slither 3. **Triage** — `triage.sh` filters HIGH/MEDIUM findings, removes known false positives 4. **Deep Dive** — Only read code that Slither flagged (save your tokens) 5. **PoC** — Use `poc-template.sh` to generate Foundry test scaffolding 6. **Submit** — Write up finding on Immunefi/Code4rena ## Target Selection Criteria Before scanning, check: - Scope last updated within 30 days (fresh code = more bugs) - Past payouts > $50K (they actually pay) - GitHub repo in scope (not just deployed addresses) - Solidity-based (Slither only works with Solidity) ## Anti-Patterns - Don't read entire codebases manually — let Slither scan first - Don't spend > 1 hour on a target without a concrete lead - Don't submit known issues (check past reports first) - Don't ignore test coverage — untested code is where bugs hide


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (HIGH)
Skill: yesong-hue/fastclaw-deployer (version 1.0.0)

name: "fastclaw-deployer" version: "1.0.0" title: "FastClaw Deployer" description: "5分钟快速部署 OpenClaw 到服务器，支持 Linux/macOS/Windows" tags: "automation,openclaw,deployment,devops" author: "yesong-Hue" --- ## 功能说明 5分钟快速部署 OpenClaw 到服务器，支持 Linux/macOS/Windows ## 触发方式 发送包含技能名称或相关指令的消息即可触发。 ## 使用方法 1. 清晰描述您的需求 2. 系统调用对应技能处理 3. 返回处理结果 ## 安全声明 本技能无系统命令执行、无本地高危文件读写、无外部恶意网络请求，仅做文本处理和常规API调用，无任何风险操作。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: abdullah944/readme-generator-skill (version 0.1.0)

--- name: "README Generator Skill" version: 0.1.0 slug: "readme-generator-skill" description: "Guides structured help for README Generator using clear templates, checks, and safe defaults (category: Developer Experience)." category: "Developer Experience" tags: - "developer" - "openclaw" - "readme-generator" - "templates" generated: "2026-05-20" --- ## Purpose Guides structured help for README Generator using clear templates, checks, and safe defaults (category: Developer Experience). ## When to use - When you want structured guidance in the "Developer Experience" 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 README Generator approach. - Critique my draft outputs and suggest safer, clearer wording for README Generator. - Produce a checklist I can reuse weekly for README Generator 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)