OpenClaw/clawhub-security-signals huggingface dataset:
Skill: ekin-chn/doc-first (version 1.2.0)

# doc-first **任何外部工具、服务、API 的配置或问题，第一时间查官方文档，力求精准解决。** ## 触发条件 遇到以下情况时自动触发： - 不确定某个工具/服务的正确配置格式 - 不确定某个命令的用法或选项 - 遇到权限、授权、认证相关问题 - 遇到错误不知道原因 - 任何不确定的操作 - 配置 openclaw.json / 环境变量 / CLI 参数时 ## 执行原则 ### 第一原则：查官方文档 - 优先查官方文档/官方 API 文档 - 用 `web_fetch` 抓取官方页面 - **英文文档为主，中文文档用于辅助确认**（中文翻译常有滞后或不完整） - **查完官方文档仍无解** → 按序尝试：GitHub Issue → Stack Overflow → 开发者社区搜索 - **每次查文档须说明依据**：告诉用户查了哪篇文档、哪个版本（URL + 日期或版本号），方便用户核实 ### 第二原则：精准解决 - 不确定答案时，宁可说"我不确定"也不瞎猜 - 遇到奇怪报错，先查文档再尝试修复 - 配置文件动手前，先确认正确格式和路径 ### 第三原则：如实告知 - 官方文档没有 → 直接说明，不编造 - 找不到解决方案 → 说清楚，而不是给可能错误的答案 - 不确定的地方 → 提出最可能的猜测，但标注不确定 ### 第四原则：验证步骤 改了配置之后，**重新对比官方文档**，确认格式/路径/选项都匹配，再继续下一步。不匹配就修正，不确定就停下来如实告知用户。 ### 第五原则：版本意识 查文档时**先确认版本号或服务版本**，尤其是 Discord API 这类有大版本变化的（v10 → v14 格式完全不同）。不确定用哪个版本时，优先用最新版文档，并在回答中注明版本依据。 ## 常见误区 - 以为配置格式和旧版本一样（实际上经常变） - 记错选项名（比如 `--force` 写成 `--forced`） - 混用不同 API 版本（v1 和 v2 格式完全不同） - 用错误的路径（比如把 user 配置放进 system 配置） ## 常用文档入口 | 服务 | 文档地址 | |------|----------| | OpenClaw | https://docs.openclaw.ai/llms.txt | | OpenAI | https://platform.openai.com/docs | | Anthropic | https://docs.anthropic.com/ | | GLM (智谱) | https://open.bigmodel.cn/dev/api | | MiniMax | https://www.minimaxi.com/document/Guide | | 阿里云通义千问 (DashScope) | https://qianwen-api.aliyun.com/ | | 百度文心一言 (千帆) | https://qianfan.cloud.baidu.com/ | | 讯飞星火认知大模型 | https://www.xfyun.cn/doc/spark/ | | 月之暗面 Kimi (Moonshot) | https://platform.moonshot.cn/ | | 昆仑万维天工AI | https://www.tiangong.cn/ | | 字节扣子 (Coze) | https://www.coze.cn/docs/ | | 微信小程序 | https://developers.weixin.qq.com/miniprogram/dev/framework/ | | Telegram Bot API | https://core.telegram.org/bots/api | | DeepSeek | https://api.deepseek.com/docs | | Slack API | https://api.slack.com/ | | Discord API | https://discord.com/developers/docs | | GitHub API | https://docs.github.com/rest | | Notion API | https://developers.notion.com/docs/getting-started | | GMAIL API | https://developers.google.com/gmail/api | ## 规则 **不查官方文档不开口。找不到就直说，不编答案。**


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: huangliujiao-tal/dev-project-tracker (version 1.0.0)

--- name: project-tracker description: >- 按需求/版本维度管理项目全生命周期。创建需求目录、记录日常进展、追踪问题、管理变更、自动蒸馏归档。 触发词：创建需求目录、新建项目、项目进展、记录进展、项目归档、蒸馏项目、查看项目、项目状态、 "新需求"、"建个项目目录"、"记一下进展"、"这个需求上线了"。 适用于任何按版本/需求迭代的软件项目。 --- # Project Tracker 按需求/版本一站式管理项目文档，覆盖从创建到归档的完整生命周期。 ## 目录结构规范 每个需求/版本一个目录，放在 `projects/<project-name>/<requirement-name>/` 下： ``` projects/<project>/<requirement>/ ├── README.md # 总览：需求名称、负责人、上线时间、状态 ├── WORK_LOG.md # 日常进展（按日期倒序） ├── DIVISION.md # 分工表 ├── ISSUES.md # 问题追踪 ├── CHANGES.md # 变更记录 ├── docs/ # 需求文档、PRD链接 ├── tech/ # 技术方案 └── design/ # 设计稿链接 ``` ## 操作指南 ### 创建需求目录 收到"创建需求目录"或"新需求"时： 1. 读取 `references/templates/` 下的模板文件 2. 在 `projects/<project>/<requirement>/` 下创建完整目录结构 3. 填入已知信息（需求名、负责人、预计上线时间等） 4. README.md 中 `状态` 字段设为 `🟢 开发中` ### 记录日常进展 收到"记录进展"或项目相关更新时： 1. 在 `WORK_LOG.md` 顶部添加新条目（日期倒序） 2. 格式：`## YYYY-MM-DD` + 具体内容 3. 同步更新个人日志 `memory/YYYY-MM-DD.md` 4. 关键决策同时写入长期记忆（memory_store） ### 追踪问题 在 `ISSUES.md` 中管理： ```markdown | # | 问题描述 | 状态 | 负责人 | 创建日期 | 解决日期 | |---|---------|------|--------|---------|---------| | 1 | xxx | 🔴待解决 | xxx | 2026-03-20 | - | ``` 状态：🔴待解决 → 🟡处理中 → 🟢已解决 ### 变更记录 需求变更时在 `CHANGES.md` 记录： ```markdown ## YYYY-MM-DD 变更标题 - **变更内容：** xxx - **变更原因：** xxx - **影响范围：** xxx - **确认人：** xxx ``` ### 生命周期管理 README.md 中必须包含 `状态` 和 `实际上线` 字段： | 阶段 | 状态 | 触发条件 | 操作 | |------|------|---------|------| | 活跃期 | 🟢 开发中 | 创建时 | 完整记录所有文件 | | 蒸馏期 | 🟡 已上线(蒸馏中) | 上线后2周 | WORK_LOG/ISSUES 压缩为摘要，tech/design 保留 | | 归档期 | 🔴 已归档 | 上线后3个月 | 压缩为 ARCHIVE.md，删除原目录 | 蒸馏/归档前必须通知负责人确认。 ### 查看项目状态 收到"查看项目"或"项目状态"时： 1. 扫描 `projects/` 下所有需求目录 2. 读取每个 README.md 的状态和上线时间 3. 汇总输出项目看板 ## 注意事项 - 项目进展写 WORK_LOG.md，**不混入个人日志** - 关键决策、人员信息同步到长期记忆 - 设计稿链接存 `design/DESIGN.md`，需求文档链接存 `docs/` - 技术方案存 `tech/`，按前端/后端分文件


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: nansen-devops/nansen-web-fetcher (version 0.1.0)

--- name: nansen-web-fetcher description: Fetch and analyze content from one or more URLs using AI (Gemini 2.5 Flash). Use when you have specific URLs and need to extract or summarize their content. Pairs well with `nansen web search` results. metadata: openclaw: requires: env: - NANSEN_API_KEY bins: - nansen primaryEnv: NANSEN_API_KEY install: - kind: node package: nansen-cli bins: [nansen] allowed-tools: Bash(nansen:*) --- # Web Fetch Fetch and analyze content from one or more URLs using Gemini 2.5 Flash with URL context. ```bash nansen web fetch https://nansen.ai --question "What products does Nansen offer?" nansen web fetch --url https://example.com --url https://other.com --question "Compare these two sites" nansen web fetch https://docs.uniswap.org/contracts/v4/overview --question "What changed in v4?" ``` Positional args and `--url` flags can be combined — all become URLs to fetch. | Flag | Values | Default | Purpose | |------|--------|---------|---------| | `--url` | URL | — | URL to fetch (repeatable for multiple URLs, up to 20) | | `--question` | string | **required** | Question to answer about the URL content | | `--pretty` | flag | off | Human-readable JSON | Returns: - `analysis` — AI-generated answer to your question - `retrieved_urls` — URLs successfully fetched - `failed_urls` — URLs that could not be retrieved **Tip:** Combine with `web search` — search first to find relevant URLs, then fetch to get full content. ```bash # Find and analyze in two steps nansen web search "uniswap v4 launch" --num-results 3 --fields link nansen web fetch https://blog.uniswap.org/... --question "What are the key changes?" ``` **Note:** 30s timeout. Paywalled or bot-blocked pages may appear in `failed_urls`.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: g-hanasq/article-idea-capture (version 0.1.0)

--- name: article-idea-capture description: Record公众号文章灵感、选题、半成品观点，并持续整理成可写的大纲或初稿。Use when the user says they have an article idea, topic, inspiration,选题, 钩子, 标题想法, or wants to save a thought for later writing. Also use when the user wants to append to the ongoing idea pool, rank saved ideas, or expand one saved idea into an outline or draft. --- # Article Idea Capture Maintain the user's ongoing article idea pool with low friction. ## Default storage Primary sink: - Feishu doc: `加十的公众号灵感池` - URL: `https://www.feishu.cn/docx/BwAFdeJZdoEeeWxfbkbcZVpWnOe` If Feishu doc tools are unavailable in the current tool surface, fall back to a local markdown file under the workspace and clearly say it was stored locally instead of Feishu. ## Core rule Optimize for **capture first, refinement later**. When the user drops a raw idea, do not force a full article structure immediately unless they ask for it. ## Capture workflow ### 1. If the user gives a raw idea Turn it into a compact idea card with these fields: - **题目方向** - **核心观点** - **为什么值得写** - **适合谁看** - **可延展角度** - **可能标题** Keep it concise and useful. Do not over-polish. ### 2. Append to the idea pool Prefer appending to the Feishu idea pool doc. Append under a new section like: `### 灵感 N：<short title>` Then include the six fields above. ### 3. Confirm what was stored Reply briefly with: - it was recorded - the short title used - whether it went to Feishu doc or local fallback ## Expansion workflow When the user wants to continue an existing idea, support these next steps: - pick the best 3 ideas - cluster ideas by theme - expand one idea into an outline - write a first draft - generate title options - split one big idea into a series ## Writing style - Keep the capture lightweight - Prefer practical article angles over abstract slogans - Preserve the user's original insight even when cleaning wording - Do not flatten everything into generic AI-blog phrasing ## Fallback local storage If Feishu doc append is unavailable, store in: - `/Users/shiyi/.openclaw/workspace/research/article-idea-pool.md` Append only; do not overwrite existing entries.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: abca12a/rakuten-shop-analysis (version 0.1.10)

--- name: rakuten-shop-analysis description: 用于分析 Rakuten 乐天店铺。用户提供店铺链接或 shopCode 时使用，适合竞品研究、店铺结构分析和快速出报告。 metadata: openclaw: requires: bins: ["node"] --- # Rakuten Shop Analysis 分析 Rakuten 乐天店铺，并返回结构化结果。 适合用于： - 店铺分析 - 竞品研究 - 爆款样本查看 - 快速出分析报告 支持输入： - 乐天店铺链接 - 乐天 `shopCode` ## 网络与隐私说明 - 这个 skill 会把你提供的店铺链接或 `shopCode` 发送到托管后端进行分析 - 当前托管后端域名：`https://rakuten.845817074.xyz` - 当前版本不需要 token，走匿名试用模式 - 除了你输入的店铺标识和分析请求本身，不要求额外账号凭证 ## 如何使用 安装后，直接对 OpenClaw 说： ```text 分析这个乐天店铺：https://www.rakuten.co.jp/vacchetta-topkapi/ ``` 或者： ```text 帮我出一份这个乐天店铺的分析报告：https://www.rakuten.co.jp/vacchetta-topkapi/ ``` 也可以直接输入 `shopCode`： ```text 分析这个乐天店铺：vacchetta-topkapi ``` ## 当前说明 - 安装后可直接匿名试用 - 当前匿名限额：每个 IP 每 60 秒最多 30 次 API 请求 - 如果限流，等待约 1 分钟后再试即可 - 当前版本不需要配置 token，也不需要配置后端地址 ## 结果返回规则 - 正常情况下，应等待 skill 执行完成后，再一次性返回最终分析结果 - 如果本次调用没有拿到最终结果，不要声称会在后台持续监控、稍后自动回复或继续异步跟进 - 遇到未完成、超时或宿主中断时，应明确告诉用户本次调用未完成，并请用户稍后重试 ## 执行约束 - 必须使用 skill 自带执行入口，不要临时改用别的实现 - 不要向用户展示内部 API 地址、接口路径、查询参数或调试细节 - 不要向用户承诺“我会继续监控并稍后主动返回结果”这类后台跟进能力 - 不要 `write_file` 生成临时 JS/Python/Bash 抓取脚本 - 不要自行用 `axios`、`fetch`、`https.request`、`cheerio`、浏览器抓取等方式直接抓 Rakuten 页面 - 不要绕过 skill，自行拼接不存在的 API 主机、路径或参数 - 目标是调用托管分析服务并返回结果，而不是现场重写一个新的 Rakuten 抓取器

path: package.json
content: {
  "name": "rakuten-shop-analysis-skill",
  "private": true,
  "type": "module",
  "scripts": {
    "test": "node --test tests/run.test.mjs"
  }
}


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: yezhaowang888-stack/huimai-teacher-capacity (version 1.0.0)

--- name: teacher-capacity-evaluation description: 中国中小学教师教学能力动态评估系统。基于学生学业数据（来自 homework-grading-assessment skill）生成同年级班级间学业对比图及教师教学能力评估图。触发场景：(1)生成同年级不同班级学业情况动态对比图 (2)生成单科教师教学能力评估与同科教师横向对比 (3)按角色分级管理教师数据查看权限 (4)追溯分析教师教学效果趋势。 --- # 教师教学能力动态评估 ## 核心功能 ### 1. 教师教学效果评估 基于 `homework-grading-assessment` 输出的学生知识点掌握数据，评估教师教学效果： - **班级维度**: 所教班级各知识点掌握率的**提升幅度**（学期初 → 当前） - **时间维度**: 历次测验成绩变化趋势（稳定上升 / 波动 / 下降） - **均衡维度**: 班级内部学生差距变化（标准差缩小趋势 → 教学均衡性好） - **综合评分**: 多维度加权得出教学效果得分（0-100） ### 2. 同年级班级间学业对比 - **学业情况动态图**: - 折线图：各班各科平均分/掌握率随时间变化 - 箱线图：各班成绩分布对比（中位数、四分位距、极值） - 进度条图：各班知识点完成度对比 - **对比图交互**: 可选定任意两个或多个班级叠加对比，支持环比（与上次测验比）和同比（与上月/上学期比） ### 3. 同科教师教学对比 - **单科教师教学效果对比图**: - 柱状图：同年级同科教师教学综合评分排序 - 雷达图：教学能力的多个维度（知识点覆盖度、学生进步度、均衡性、作业反馈时效） - 热力图：各教师在各知识点上的"班级掌握率"对比 - **个人成长曲线**: 单名教师历次评估的分数变化趋势 ### 4. 分层授权管理 | 角色 | 数据可见范围 | |------|-------------| | 单科教师 | 自己教学评分、同科同年级教师对比数据（匿名或实名由学校配置） | | 年级组长 | 本年级各班各科教师数据、年级整体教师评价 | | 教导主任/教务 | 全校教师评估数据、配置对比实名/匿名、分配查看权限 | | 校长 | 全校教师总览、定向深入查看 | | 系统管理员 | 权限配置、数据导入导出、系统设置 | ### 5. 报告的组成 - **个人报告**: 教师姓名、所教班级、各维度评分、教学建议（可改进方向、推荐教研活动） - **年级报告**: 年级整体教学质量总览、各班/各科排布、关注建议（需重点关注班级或教师） - **校级报告**: 全校教学趋势、学科强弱项、资源配置建议 ## 数据依赖 本 skill **依赖** `homework-grading-assessment` skill 的输出数据，主要是： - student KP mastery data - class-level aggregated scores - historical trend data ## 参考文件 见 [references/data-model.md](references/data-model.md) — 教师、评估模型、对比维度的数据结构。 见 [references/permission-model.md](references/permission-model.md) — 教师数据分级查看权限。 见 [references/chart-spec.md](references/chart-spec.md) — 教师评估图表规格。 见 [references/textbook-version-mapping.md](references/textbook-version-mapping.md) — 知识点-教材版本映射方案，教师评估依赖的知识点数据源于此映射体系。 --- ## 授权说明 **版权与知识产权**: © 2026 Huimai Intelligence. All Rights Reserved. 本技能文件（含所有附属参考文档）为**设计说明与产品预览**，仅限个人教师免费查阅和使用其中的教育理念与评估方法论。 **商业使用许可**: 任何学校、教育机构或企业如需部署、集成、定制本系统，或进行任何形式的商业使用，须与惠迈智能（Huimai Intelligence）签订书面商业许可协议。 本文件发布于 ClawHub 平台，发布时间戳作为原创性证明，受《中华人民共和国著作权法》及相关国际版权条约保护。未经授权复制、分发、修改或商用将追究法律责任。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: freeeye/gz-media-tester (version 1.0.0)

--- name: gz-media-tester description: | 广州日报/融媒云通用测试助手。专为广州日报报业集团及广州市区融媒云平台的测试工作设计。 覆盖场景： (1) 广州市区融媒云平台后台管理系统（CMS/采编/运营后台）功能测试 (2) 广州融媒云APP（Android/iOS/HarmonyOS）功能、性能、兼容性测试 (3) 广州日报新花城APP（Android/iOS/HarmonyOS）功能、性能、兼容性测试 (4) H5页面、活动链接可用性与兼容性测试 (5) 微信小程序/支付宝小程序功能测试 (6) 后端接口（API）自动化测试 (7) 测试用例生成、测试报告输出、Bug单撰写 触发关键词：测试、test、冒烟测试、回归测试、接口测试、APP测试、H5测试、小程序测试、融媒云测试、新花城测试、测试用例、测试报告、Bug单 --- # 广州日报/融媒云通用测试助手 ## 平台概览 | 平台 | 说明 | |------|------| | 融媒云后台 | 广州市区融媒体云平台采编/运营管理后台（B/S架构，内网+公网双通道） | | 融媒云APP | 广州日报社开发，包ID: `com.pdmi.blend.media`，Android/iOS/HarmonyOS三端 | | 新花城APP | 广州日报官方客户端，广州市区融媒体平台，Android/iOS/HarmonyOS三端 | | 新花城H5 | 域名: `huacheng.gz-cmc.com`，内嵌于APP及微信生态 | | 大洋网 | `news.dayoo.com`，广州日报新闻门户 | | 微信小程序 | 新花城小程序、各区融媒体小程序 | --- ## 工作流 ### 1. 接收测试任务 用户说明测试目标后，先确认： - **测试类型**：冒烟 / 功能 / 回归 / 性能 / 接口 / 兼容性 - **测试平台**：后台 / APP（哪个端）/ H5 / 小程序 / 接口 - **测试范围**：模块/功能点/版本号 - **输出格式**：测试用例 / 测试报告 / Bug单 如信息不足，主动询问缺失项（一次最多问3个问题）。 ### 2. 生成测试用例 调用 `scripts/generate_cases.py` 或直接按模板输出。 参见 `references/test-cases.md` 获取各平台标准用例库。 ### 3. 执行接口测试 调用 `scripts/api_test.py` 对目标接口发起请求并验证响应。 接口规范参见 `references/api-reference.md`。 ### 4. 输出测试报告 按 `references/report-template.md` 格式输出测试报告。 ### 5. 撰写 Bug 单 按 `references/bug-template.md` 格式输出 Bug 单。 --- ## 快速命令 | 用户说 | 执行动作 | |--------|---------| | "生成冒烟测试用例" | 读 references/test-cases.md → 输出对应平台冒烟用例 | | "测试这个接口 [URL]" | 运行 scripts/api_test.py | | "生成测试报告" | 读 references/report-template.md → 填充输出 | | "写一个Bug单" | 读 references/bug-template.md → 填充输出 | | "检查H5链接" | 运行 scripts/check_url.py | | "APP兼容性测试方案" | 读 references/compatibility.md | --- ## 注意事项 - 接口测试默认使用测试环境，**不得**对生产环境发起写操作 - APP测试需区分 Android / iOS / HarmonyOS 三端差异 - H5测试需覆盖微信内置浏览器、系统浏览器、APP内嵌WebView三种场景 - 性能基准：APP冷启动 ≤ 3s，接口响应 ≤ 1s（P99），H5首屏 ≤ 2s


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: ivangdavila/podcasts (version 1.0.0)

--- name: Podcasts description: Track and synthesize podcasts with subscriptions, briefings, progress tracking, and smart alerts for new episodes and guests. --- ## Core Behavior - User mentions a podcast → add to subscriptions, track new episodes - User asks "what's new?" → summarize recent episodes from subscribed shows - User asks for briefing → generate summary without them listening - User mentions time constraints → prioritize and recommend what to skip --- ## Workspace Store podcast data in `~/podcasts/`: ``` ~/podcasts/ ├── subscriptions.md # Shows I follow ├── queue.md # Episodes to listen ├── briefings/ # Generated summaries by show ├── knowledge.md # Extracted insights (learner mode) └── guests.md # VIP guest watchlist ``` --- ## Quick Commands | User Says | Agent Does | |-----------|------------| | "I follow Lex Fridman" | Add to subscriptions | | "Summarize latest Huberman" | Generate episode briefing | | "What should I listen to?" | Prioritize queue by time available | | "Did Naval appear anywhere?" | Check guest across all podcasts | | "I finished episode X" | Mark complete, update progress | | "Too many episodes" | Suggest what to skip, create catch-up plan | --- ## Load Reference | Situation | File | |-----------|------| | Generating briefings, summaries | `briefings.md` | | YouTube video podcasts, clips | `youtube.md` | | Learning mode, knowledge extraction | `learning.md` | | Discovery and recommendations | `discovery.md` |


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: suspicious (MEDIUM)
Skill: coolhackboy/z-image (version 1.0.0)

--- name: poyo-z-image description: Use PoYo AI Z-Image for straightforward prompt-based image generation through the `https://api.poyo.ai/api/generate/submit` endpoint. Use when a user wants direct text-to-image output, simple aspect-ratio control, lightweight PoYo payloads, or submissions for `z-image`. metadata: {"openclaw": {"homepage": "https://docs.poyo.ai/api-manual/image-series/z-image", "requires": {"bins": ["curl"], "env": ["POYO_API_KEY"]}, "primaryEnv": "POYO_API_KEY"}} --- # PoYo Z-Image Generation Use this skill to submit and track PoYo jobs for the Z-Image family. ## Quick workflow 1. Choose the right model id for the requested output. 2. Build the request body for `POST https://api.poyo.ai/api/generate/submit`. 3. Send Bearer-authenticated JSON with `Authorization: Bearer <POYO_API_KEY>`. 4. Save the returned `task_id`. 5. Poll unified task status or wait for `callback_url` notifications. ## Request rules - Require top-level `model`. - Keep prompts concrete and outcome-focused. - Require `input.prompt` unless the user already supplied a full payload. - Use `input.size` to match the intended aspect ratio or canvas. ## Model selection ### `z-image` Use for general generation with this model variant. ## Execution - Read `references/api.md` for endpoint details, model ids, key fields, example payloads, and polling notes. - Use `scripts/submit_z_image.sh` to submit a raw JSON payload from the shell. - If the user only needs a curl example, adapt the example from `references/api.md` instead of rewriting from scratch. - After submission, report the `task_id` clearly so follow-up polling is easy. ## Output expectations When helping with this model family, include: - chosen model id - final payload or a concise parameter summary - whether reference images are involved - returned `task_id` if a request was actually submitted - next step: poll status or wait for webhook Notes: Needs POYO_API_KEY from https://poyo.ai PoYo.ai - Premium AI API Platform | Image, Video, Music & Chat APIs - 80% Cheaper


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: mozaldy/mis-logbook-submit (version 1.0.0)

--- name: mis-logbook-submit description: Submit a daily PENS MIS Kerja Praktek logbook entry at online.mis.pens.ac.id after an approval-first workflow. Gather same-day work evidence, synthesize concise Indonesian activity text for the Kegiatan/Materi field, sign in with local secrets, navigate to Entry Logbook KP, save the entry, and verify the new row appears. Use when inspecting, preparing, or submitting MIS KP logbooks. --- # MIS logbook submit Read `references/workflow.md` before doing real work. ## Core rules - Use local secrets for login, never ask for or echo credentials in chat. - Prefer browser automation with Playwright. - Write `Kegiatan/Materi` in natural Indonesian. - Respect the approval-first flow when a pending draft exists. - Keep the text under the form limit and avoid literal `SELECT`, `INSERT`, `UPDATE`, and `DELETE` because the page may reject them. - Check for an existing row before creating a new one. - Verify both the success state and the saved row after submit.


Security scan verdicts — ClawScan: clean | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: terrycarter1985/news-summarizer (version 1.0.1)

--- name: news-summary description: > Fetch and summarize world news from BBC, Reuters, NPR RSS feeds. Can create voice summaries. USE WHEN: "What's happening in the world?", daily briefings, general news updates, current events. DON'T USE: Stock/market news (use stock-analysis), weather (use weather skill), sports scores, stock-specific company news. --- # News Summary ## Overview Fetch and summarize news from trusted international sources via RSS feeds. ## When NOT to Use This Skill ❌ "What's happening with NVDA stock?" → Use **stock-analysis** skill ❌ "What's the weather in Warren NJ?" → Use **weather** skill ❌ "Summarize this YouTube video" → Use **summarize** skill ❌ "What are people saying on Twitter about X?" → Use **bird** skill ❌ "Give me sports scores" → Use web_search directly ## RSS Feeds ### BBC (Primary) ```bash # World news curl -s "https://feeds.bbci.co.uk/news/world/rss.xml" # Top stories curl -s "https://feeds.bbci.co.uk/news/rss.xml" # Business curl -s "https://feeds.bbci.co.uk/news/business/rss.xml" # Technology curl -s "https://feeds.bbci.co.uk/news/technology/rss.xml" # Asia (good for India/South Asia coverage) curl -s "https://feeds.bbci.co.uk/news/world/asia/rss.xml" ``` ### Reuters ```bash # World news curl -s "https://www.reutersagency.com/feed/?best-regions=world&post_type=best" ``` ### NPR (US perspective) ```bash curl -s "https://feeds.npr.org/1001/rss.xml" ``` ### The Hindu (India) ```bash curl -s "https://www.thehindu.com/news/national/feeder/default.rss" ``` ## Parse RSS Extract titles and descriptions: ```bash curl -s "https://feeds.bbci.co.uk/news/world/rss.xml" | \ grep -E "<title>|<description>" | \ sed 's/<[^>]*>//g' | \ sed 's/^[ \t]*//' | \ head -30 ``` ## Workflow ### Text summary 1. Fetch BBC world headlines 2. Optionally supplement with Reuters/NPR 3. Summarize key stories 4. Group by region or topic ### Voice summary 1. Create text summary 2. Generate voice with OpenAI TTS 3. Send as audio message ```bash curl -s https://api.openai.com/v1/audio/speech \ -H "Authorization: Bearer $OPENAI_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "tts-1-hd", "input": "<news summary text>", "voice": "onyx", "speed": 0.95 }' \ --output /tmp/news.mp3 ``` ## Example Output Format ``` 📰 News Summary [date] 🌍 WORLD - [headline 1] - [headline 2] 💼 BUSINESS - [headline 1] 💻 TECH - [headline 1] ``` ## Best Practices - Keep summaries concise (5-8 top stories) - Prioritize breaking news and major events - For voice: ~2 minutes max - Balance perspectives (Western + Indian/Asia) - Cite source if asked


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: albionaiinc-del/agent-reflect-engine (version 1.0.0)

# Agent Reflect Engine A self-reflection engine that analyzes AI agent decision logs to identify reasoning flaws and suggest optimization patches, improving long-term performance and reducing hallucination. ## Usage ```bash # Analyze agent logs and get reflection report python agent_reflect_engine.py logs/agent_trace.jsonl --output report.json # Include trusted knowledge base for hallucination detection python agent_reflect_engine.py logs/agent_trace.jsonl --knowledge kb.json --output report.json # Pipe directly for automation python agent_reflect_engine.py logs/latest.jsonl | jq '.patch_suggestions' ``` ## Price $9.99


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