OpenClaw/clawhub-security-signals huggingface dataset:
Skill: phalapi/crawhub-skill-yesapi (version 1.1.0)

--- name: yesapi description: YesApi果创云低代码平台接口封装，支持表单结构和数据操作 version: 1.0.0 homepage: https://api.yesapi.net/ user-invocable: true metadata: {"requires": {"env": ["YESAPI_APP_KEY", "YESAPI_DOMAIN", "YESAPI_SIGN"]}, "tags": ["api", "lowcode", "yesapi", "form", "database"]} --- # YesApi 果创云低代码平台 Skill 本技能提供对 YesApi 果创云低代码平台的完整接口封装，支持表单结构管理和数据操作。 ## 配置要求 在使用前需要配置以下环境变量： - `YESAPI_APP_KEY`: 你的果创云应用密钥 - `YESAPI_DOMAIN`: 果创云API域名（默认：https://api.yesapi.net） - `YESAPI_SIGN`: 静态签名密钥 ## 功能特性 ### 1. 表单结构管理 - 获取表单模型列表 - 创建表单模型 - 更新表单结构 - 删除表单模型 ### 2. 表单数据操作 - 通用数据查询（支持分页、过滤、排序） - 数据新增 - 数据更新 - 数据删除 - 批量更新 - 批量删除 ## 使用方法 ### 获取表单列表 ``` 获取我的表单模型列表 ``` ### 查询表单数据 ``` 查询表单 [表单名] 的数据，限制10条记录 ``` ### 创建新数据 ``` 向表单 [表单名] 添加新数据：{"field1": "value1", "field2": "value2"} ``` ### 更新数据 ``` 更新表单 [表单名] 中ID为 [记录ID] 的数据：{"field1": "new_value"} ``` ### 删除数据 ``` 删除表单 [表单名] 中ID为 [记录ID] 的记录 ``` ### 批量更新数据 ``` 批量更新表单 [表单名] 中满足条件的数据：{"field1": "new_value"}，指定条件where：[["字段名", "比较符", "比较值"]] ``` ### 批量删除数据 ``` 批量删除表单 [表单名] 中满足条件的记录，指定条件where：[["字段名", "比较符", "比较值"]] ``` ## API 接口封装 ### 表单结构接口 基于 `App.Platform_MyModels` 接口封装： - `get_models()`: 获取模型列表 - `create_model(model_name)`: 创建新模型 - `delete_model(model_name)`: 删除模型 - `add_model_new_field(model_name, field_data)`: 为模型添加新字段 ### 表单数据接口 基于 `App.Table` 系列接口封装： - `query_data(model_name, params)`: 查询数据 - `insert_data(model_name, data)`: 插入数据 - `update_data(model_name, id, data)`: 更新数据 - `delete_data(model_name, id)`: 删除数据 - `batch_update(model_name, where, data)`: 批量更新数据 - `batch_delete(model_name, where)`: 批量删除数据 ## 错误处理 所有API调用都会返回详细的错误信息，包括： - HTTP状态码 - 错误代码 - 错误消息 - 建议解决方案 ## 最佳实践 1. **配置管理**: 建议使用环境变量管理敏感信息 2. **错误重试**: 网络请求支持自动重试机制 3. **数据验证**: 在发送数据前进行本地验证 4. **日志记录**: 重要操作会记录详细日志 ## 技术实现 - 使用 Python 的 `requests` 库进行HTTP请求 - 支持异步操作提高性能 - 内置签名算法确保API安全 - 完整的类型提示支持 ## 依赖项 - Python 3.8+ - requests >= 2.28.0 - pydantic >= 1.10.0 - python-dotenv >= 0.19.0 ## 许可证 MIT License


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: devinchen2014/socialdatax-xhs-creator-notes (version 0.1.6)

--- name: socialdatax-xhs-creator-notes description: 用于小红书博主数据、小红书博主笔记、账号内容列表、近期发布、内容调研和创作者内容分析。覆盖 Xiaohongshu / XHS / RedNote creator notes，来自 SocialDataX 社媒数据助手。 metadata: {"openclaw":{"requires":{"env":["SOCIALDATAX_API_KEY"],"bins":["node","npm"]},"primaryEnv":"SOCIALDATAX_API_KEY","emoji":"🗂️","homepage":"https://socialdatax.com/?from=clawhub","install":[{"kind":"node","package":"socialdatax-skills","bins":[]}]}} --- # 小红书博主数据 SocialDataX 博主笔记 Use this skill when the user wants 小红书博主数据, a Xiaohongshu / XHS / RedNote creator's published note list, content style analysis, recent-topic review, creator benchmarking, or account tracking. ## API Key Use `SOCIALDATAX_API_KEY` for data calls. The only official website for requesting or managing API access is <https://socialdatax.com/?from=clawhub>. If a user asks where to get a key, provide only this URL; do not infer alternate domains. 获取或管理 API Key：访问 <https://socialdatax.com/?from=clawhub>，按官网的 API Key 申请/管理入口操作。环境变量名固定使用 `SOCIALDATAX_API_KEY`；不要引导用户使用其他域名。 ## Preferred Direct CLI Prefer the direct CLI when the agent can run shell commands. It does not require MCP server configuration: ```bash npx -y socialdatax-skills@latest xhs user-posts --user-id "<user_id>" --pretty npx -y socialdatax-skills@latest xhs user-posts --profile-url "<profile_url_or_share_text>" --pretty ``` - `--user-id <user_id>`: preferred when the creator ID is already known. - `--profile-url <profile_url_or_share_text>`: use for a profile URL, short link, or profile share text. - `--page-token <next_page_token>`: opaque pagination token; pass back exactly the token returned by the previous page and do not reuse it across users. - `--pretty`: output formatting only. Use either `--user-id` or `--profile-url` for one command, not both. ## Safety Boundary This skill is read-only. It does not read local browser data, does not save API keys, and does not perform login, posting, liking, commenting, or account changes. ## MCP Tools If MCP tools are already available in the current agent, use one of these tools: - `xhs_get_user_posted_notes_by_user_id`: preferred when `user_id` is already known. - `xhs_get_user_posted_notes_by_profile_url`: use for profile URLs, short links, or profile share text. Creator note-list pagination uses `page_token`. Pass back exactly the returned `next_page_token`; tokens are bound to the current user and should not be reused across users. ## Output Guidance Summarize content-list evidence by title, content summary, publish time, interaction counts, media links, and note IDs when present. Use returned note IDs to chain into detail or comment analysis when needed.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: eddieguan801-oss/trend-following (version 1.0.0)

--- name: trend-following description: Trend-following stock analysis using price + volume. Use when user asks to analyze a stock, check a ticker, get buy/sell signals, find support/resistance, or calculate entry/exit targets. Triggers on phrases like "analyze [ticker]", "buy/sell signals", "支撑位", "阻力位", "趋势分析", "目标价", "分析 [股票代码]", "帮我看 [股票]"，or any stock ticker symbol. Supports any Yahoo Finance ticker (e.g., ADBE, ORCL, AAPL, TSLA). --- # Trend Following Strategy (v1.0.0) Price + Volume based trend analysis with buy/sell signals, support/resistance levels, and target pricing. ## Quick Start ```bash python3 skills/trend-following/scripts/trend_strategy.py <TICKER> [PERIOD] ``` Examples: ```bash python3 skills/trend-following/scripts/trend_strategy.py ADBE 1y python3 skills/trend-following/scripts/trend_strategy.py ORCL 6mo python3 skills/trend-following/scripts/trend_strategy.py AAPL ``` ## Indicators Used | Indicator | Purpose | |-----------|---------| | RSI(14) | Overbought/oversold (70+=overbought, 30-=oversold) | | MACD | Trend momentum (histogram crossing 0 = signal) | | MA20/50/200 | Trend direction (price vs moving averages) | | Bollinger Bands | Volatility envelopes | | Volume MA | Volume surges confirm moves | ## Signal Logic ### Buy Signals 🟢 - MACD histogram crosses above 0 (golden cross) - Volume >1.5x avg + price above MA20 - RSI 40-60 + uptrend confirmation - Pullback to MA20 in strong uptrend - RSI oversold + MACD reversal = possible bottom ### Sell Signals 🔴 - RSI >70 (overbought) - Price below MA20 in downtrend - Volume >2x on price decline - MACD bearish (below signal line) - Breaking support level ## Output Sections 1. **Trend Status** — MA20/50/200 alignment 2. **Key Levels** — Resistance and support zones 3. **Signals** — Current buy/sell conditions 4. **Entry & Targets** — Entry price, stop loss, 3 targets with R/R ratio ## Parameters - `TICKER` — Required. Yahoo Finance ticker symbol (e.g., ADBE, ORCL, TSLA) - `PERIOD` — Optional. Data period (default: 1y). Options: 3mo, 6mo, 1y, 2y, 5y ## Notes - Requires `yfinance` (`pip install yfinance`) - Uses swing point detection for support/resistance - Targets are based on measured moves from current price to next S/R level - Always validate with current market data before trading


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: warm-wm/volcengine-image-generate (version 1.0.0)

--- name: volcengine-image-generate description: Using volcengine image_generate.py script to generate image, need to provide clear and specific `prompt`. license: Complete terms in LICENSE.txt --- # Image Generate ## Scenarios When you need to generate an image based on a text description, use this skill to call the `image_generate` function. ## Steps 1. Prepare a clear and specific `prompt`. 2. Run the script `python scripts/image_generate.py "<prompt>"`. Before running, navigate to the corresponding directory. 3. The script will return the generated image URL. ## Authentication and Credentials - First, it will try to read the `MODEL_IMAGE_API_KEY` or `ARK_API_KEY` environment variables. - If not configured, it will try to use `VOLCENGINE_ACCESS_KEY` and `VOLCENGINE_SECRET_KEY` to get the Ark API Key. ## Output Format - The console will output the generated image URL. - If the call fails, it will print the error information. ## Examples ```bash python scripts/image_generate.py "a cute cat" ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: codeman840425-del/mcp-for-beginners (version 1.0.0)

--- name: MCP for Beginners slug: mcp-for-beginners version: 1.0.0 description: Microsoft 出品的 Model Context Protocol (MCP) 入门课程，通过 .NET/Java/TypeScript/JavaScript/Rust/Python 多语言实例教学 homepage: https://github.com/microsoft/mcp-for-beginners source: use-case-candidate capability: 多Agent编排 --- ## When to Use 用户希望学习或快速上手 Model Context Protocol (MCP)，需要了解其核心概念、架构设计以及如何在实际项目中集成 MCP 时使用。 ## What It Does 提供一套完整的 MCP 开源课程，涵盖从基础概念到服务编排的完整学习路径，支持 .NET、Java、TypeScript、JavaScript、Rust 和 Python 多语言示例，帮助开发者构建模块化、可扩展的 AI 工作流。 ## How to Use 1. Fork 仓库：`https://github.com/microsoft/mcp-for-beginners/fork` 2. Clone 仓库：`git clone https://github.com/microsoft/mcp-for-beginners.git` 3. 加入 Discord 社区获取支持：`https://discord.gg/nTYy5BXMWG` 4. 按课程章节顺序学习，从会话配置到服务编排逐步深入 ## References - https://github.com/microsoft/mcp-for-beginners - https://discord.gg/nTYy5BXMWG


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: old-greggyboy/web3-docs (version 1.0.1)

--- name: web3-docs description: | Up-to-date documentation and code patterns for Solidity, Foundry, Hardhat, Viem, Wagmi, ethers.js, and OpenZeppelin. Use when writing smart contracts, debugging Solidity errors, setting up a Foundry project, writing Viem/Wagmi frontend code, or asking about ERC standards, gas optimization, upgradeable contracts, or any EVM development task. Triggers on: Solidity, Foundry, Hardhat, Viem, Wagmi, ethers.js, OpenZeppelin, ERC-20, ERC-721, ERC-4626, UUPS, proxy patterns, ABI, calldata, smart contract, deploy, cast, forge, anvil, or any EVM/blockchain development question. --- # Web3 Docs Current patterns and references for EVM development. Covers the full stack: contracts → testing → deployment → frontend integration. ## Stack Coverage | Layer | Tool | Reference | |-------|------|-----------| | Contracts | Solidity 0.8.x | `references/solidity.md` | | Framework | Foundry (forge/cast/anvil) | `references/foundry.md` | | Framework (alt) | Hardhat | `references/hardhat.md` | | Standards | OpenZeppelin 5.x | `references/openzeppelin.md` | | Standards | ERC-4626 (tokenized vaults) | `references/erc4626.md` | | Frontend (low-level) | Viem 2.x | `references/viem.md` | | Frontend (React) | Wagmi 2.x | `references/wagmi.md` | | Frontend (legacy) | ethers.js 6.x | `references/ethers.md` | ## Quick Lookup **Starting a new Foundry project:** See `references/foundry.md` → Project Setup **Starting a Hardhat project:** See `references/hardhat.md` → Installation **Writing an ERC-20:** See `references/openzeppelin.md` → ERC-20 **Building a yield vault (ERC-4626):** See `references/erc4626.md` → OpenZeppelin Implementation **First depositor attack on vaults:** See `references/erc4626.md` → First Depositor Attack **Connecting a wallet in React:** See `references/wagmi.md` → Quick Start **Reading contract state with Viem:** See `references/viem.md` → Read Contracts **Common Solidity errors:** See `references/solidity.md` → Error Reference **Deploying to Optimism/Base with Hardhat:** See `references/hardhat.md` → hardhat.config.ts ## Fetch Latest Docs `scripts/fetch-docs.js <topic>` pulls live docs from official sources when the reference files may be stale. ```bash node scripts/fetch-docs.js solidity # Solidity docs node scripts/fetch-docs.js foundry # Foundry book node scripts/fetch-docs.js viem # Viem docs node scripts/fetch-docs.js wagmi # Wagmi docs node scripts/fetch-docs.js openzeppelin # OZ docs node scripts/fetch-docs.js hardhat # Hardhat docs node scripts/fetch-docs.js erc4626 # ERC-4626 (OZ vault docs) ``` ## Gas Optimization Quick Rules 1. Use `calldata` instead of `memory` for read-only function params 2. Pack storage variables: multiple `uint128` in one slot beats two separate `uint256` 3. `unchecked` blocks for arithmetic that can't overflow (saves ~30 gas/op) 4. `immutable` > `constant` > storage for values set once 5. Events are cheaper than storage for historical data 6. Batch operations: one tx touching N items beats N txs


Security scan verdicts — ClawScan: clean | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: b-gutman/pipeworx-genderize (version 1.0.0)

--- name: pipeworx-genderize description: Predict the likely gender associated with a first name — with optional country-specific calibration via genderize.io version: 1.0.0 metadata: openclaw: requires: bins: - curl emoji: "👥" homepage: https://pipeworx.io/packs/genderize --- # Genderize Predict the statistical gender distribution of a first name based on a database of millions of records. Optionally calibrate predictions by country, since names like "Andrea" skew differently in Italy vs. the US. ## Tools - **`predict_gender`** — Gender prediction from a first name. Returns the predicted gender and probability (0-1). - **`predict_gender_country`** — Same prediction with country-specific calibration using ISO 3166-1 alpha-2 codes. ## Use cases - Personalizing marketing content based on likely gender of a first name - Demographic analysis of customer databases - Research on name-gender associations across cultures - Form pre-filling where gender context helps UX ## Example ```bash curl -s -X POST https://gateway.pipeworx.io/genderize/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"predict_gender_country","arguments":{"name":"Andrea","country_id":"IT"}}}' ``` ```json { "name": "Andrea", "gender": "male", "probability": 0.98, "count": 54032, "country_id": "IT" } ``` ## Setup ```json { "mcpServers": { "pipeworx-genderize": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/genderize/mcp"] } } } ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: cs995279497-byte/chen-openai-whisper (version 1.0.0)

--- name: chen-openai-whisper description: Local speech-to-text with the Whisper CLI (no API key). homepage: https://openai.com/research/whisper metadata: {"clawdbot":{"emoji":"🎙️","requires":{"bins":["whisper"]},"install":[{"id":"brew","kind":"brew","formula":"openai-whisper","bins":["whisper"],"label":"Install OpenAI Whisper (brew)"}]}} --- # Whisper (CLI) Use `whisper` to transcribe audio locally. Quick start - `whisper /path/audio.mp3 --model medium --output_format txt --output_dir .` - `whisper /path/audio.m4a --task translate --output_format srt` Notes - Models download to `~/.cache/whisper` on first run. - `--model` defaults to `turbo` on this install. - Use smaller models for speed, larger for accuracy.

path: _meta.json
content: ownerId: kn70pywhg0fyz996kpa8xj89s57yhv26
slug: openai-whisper
version: 1.0.0
publishedAt: 1767545365755

Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: young-joey/feishu-wiki-manager (version 1.0.2)

# 飞书知识库 AI 管家 (Feishu Wiki Manager) description: "飞书知识库管家 — 管理飞书知识空间的文档、节点、搜索和整理。支持知识库导航、文档搜索、内容迁移、权限管理。当用户需要管理飞书知识库/Wiki、搜索知识空间内容、整理知识文档、或迁移知识节点时使用。触发词：飞书知识库、飞书Wiki、知识空间、文档搜索、知识管理、feishu wiki、lark knowledge base、知识库整理、飞书文档管理。" ## 角色 你是飞书知识库的智能管家，帮助用户高效管理知识空间、节点组织、内容检索和批量操作。 ## 触发条件 当用户提及以下场景时激活此技能： - 管理飞书知识库/知识空间 - 创建、移动、重命名知识库节点 - 知识库内容搜索 - 批量整理知识库结构 - 知识库导航和查找 ## 核心能力 ### 1. 知识空间浏览 使用 `feishu_wiki` action="spaces" 列出所有可用知识空间。 使用 `feishu_wiki` action="nodes" 浏览指定空间下的节点树。 ### 2. 节点搜索 使用 `feishu_wiki` action="search" 在知识空间内搜索内容。 搜索语法：支持关键词、短语匹配，空格分隔多词。 ### 3. 节点管理 - **创建节点**: `feishu_wiki` action="create" → 在指定位置创建文档/表格/多维表格 - **移动节点**: `feishu_wiki` action="move" → 重新组织知识库结构 - **重命名**: `feishu_wiki` action="rename" → 修改节点标题 - **获取详情**: `feishu_wiki` action="get" → 查看节点完整信息 ### 4. 批量操作 - 批量创建多个节点（串行执行避免限流） - 批量移动节点到目标文件夹 - 知识库结构重组方案 ## 工作流程 ### 场景A：知识库导航 1. 先用 `spaces` 获取用户的所有知识空间 2. 展示空间列表让用户选择 3. 用 `nodes` 展示该空间下的层级结构 4. 提供清晰的树形导航 ### 场景B：知识搜索 1. 确认搜索范围（具体空间或全部） 2. 执行 `search` 操作 3. 格式化展示搜索结果（标题、路径、类型） 4. 提供直达链接 ### 场景C：结构整理 1. 先用 `nodes` 了解当前结构 2. 分析优化空间（过深/过浅的层级、命名不一致等） 3. 提出整理方案 4. 执行 `move` + `rename` 操作 ### 场景D：批量建站 1. 了解用户需要的知识库结构（如：项目文档/周报/设计稿） 2. 规划节点树 3. 从根到叶逐层创建节点 4. 返回完整的知识库地图 ## 最佳实践 ### 知识库结构建议 ``` 知识空间 ├── 📁 项目文档 │ ├── 📁 需求文档 │ ├── 📁 设计文档 │ └── 📁 技术文档 ├── 📁 团队协作 │ ├── 📁 周报 │ ├── 📁 会议纪要 │ └── 📁 复盘总结 └── 📁 知识沉淀 ├── 📁 最佳实践 ├── 📁 故障复盘 └── 📁 学习笔记 ``` ### 搜索技巧 - 精确搜索用英文引号包裹 - 用空格分隔多个关键词 - 先缩小空间范围再搜索，提高效率 ### 操作原则 1. 任何修改操作前先向用户确认 2. 移动/重命名前先用 `get` 确认目标节点 3. 批量操作按顺序执行，避免并发限流 4. 操作完成后展示变更摘要 ## 限制 - 每次 API 调用间隔至少 1 秒（防止限流） - 批量操作不超过 10 个节点/次 - 不能修改节点内容（那是 feishu_doc 的工作） - 不能设置权限（那是 feishu_perm 的工作） ## 与其他技能协同 - 配合 `feishu-bitable-butler`：知识库 + 多维表格数据管理 - 配合 `feishu-doc-ai-writer`：知识库 + 文档内容创作 - 配合 `feishu-doc-translator`：知识库 + 多语言文档管理 - 配合 `feishu-chat-bot`：知识库信息 + 群聊分享

path: references/wiki-templates.md
content: # 飞书知识库结构模板

## 模板 1：团队协作知识库
```
📚 团队知识库
├── 📁 新人入职
│   ├── 📄 团队介绍
│   ├── 📄 开发环境搭建
│   └── 📄 常用工具清单
├── 📁 项目文档
│   ├── 📁 项目A
│   │   ├── 📄 PRD
│   │   ├── 📄 技术方案
│   │   └── 📄 上线记录
│   └── 📁 项目B
│       ├── 📄 PRD
│       └── 📄 复盘
├── 📁 周报月报
│   ├── 📁 2026-Q1
│   └── 📁 2026-Q2
├── 📁 会议纪要
│   ├── 📁 站会
│   ├── 📁 周会
│   └── 📁 复盘会
└── 📁 技术沉淀
    ├── 📁 架构设计
    ├── 📁 故障复盘
    └── 📁 最佳实践
```

## 模板 2：个人知识库
```
📚 个人知识库
├── 📁 学习笔记
│   ├── 📁 前端
│   ├── 📁 后端
│   └── 📁 DevOps
├── 📁 读书笔记
│   ├── 📁 技术类
│   └── 📁 非技术类
├── 📁 工作记录
│   ├── 📁 日报
│   └── 📁 项目经验
└── 📁 资源收藏
    ├── 📁 工具推荐
    ├── 📁 文章收藏
    └── 📁 代码片段
```

## 模板 3：产品知识库
```
📚 产品知识库
├── 📁 产品规划
│   ├── 📄 产品路线图
│   ├── 📄 季度OKR
│   └── 📁 版本计划
├── 📁 需求管理
│   ├── 📁 待评估
│   ├── 📁 开发中
│   └── 📁 已上线
├── 📁 竞品分析
│   ├── 📁 直接竞品
│   └── 📁 间接竞品
├── 📁 用户研究
│   ├── 📁 用户画像
│   ├── 📁 访谈记录
│   └── 📁 可用性测试
└── 📁 数据分析
    ├── 📁 核心指标
    └── 📁 实验报告
```

## 命名规范建议
- 文件夹用 `📁` 前缀
- 文档用 `📄` 前缀
- 日期格式：YYYY-MM-DD
- 避免特殊字符（/ \ : * ? " < > |）
- 标题简洁，无需层级前缀（如 1.1.1）


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: wimi321/code-simplify (version 1.0.0)

--- name: "code_simplifier" description: "Use when changed code should be reviewed for reuse, code quality, and efficiency, then cleaned up before finalizing." --- # Code Simplifier Use this skill after making changes and before wrapping up. ## Workflow 1. Inspect the relevant diff or latest modified files. 2. Review for existing utilities that should be reused. 3. Review for code smell: parameter sprawl, copy-paste, leaky abstractions, or unnecessary comments. 4. Review for efficiency problems: repeated work, unnecessary reads, event churn, and hot-path bloat. 5. Fix confirmed issues and summarize what changed. ## Guardrails - Prefer concrete fixes over broad stylistic churn. - Keep attention on changed code, not the whole codebase. - If no issue exists, say so explicitly. ## Example Requests - Review my diff for duplicate logic and unnecessary complexity. - Clean up this changed code before I ship it. ## Inputs - Relevant diff or changed files - Optional focus area ## Outputs - Concrete cleanup changes - Short summary of improvements ## Success Criteria - Duplication or awkward abstractions were reduced. - Performance regressions were checked. - No unnecessary churn was introduced. ## Non-Goals - Massive style-only rewrites - Review of untouched code with no link to the change ## Source Provenance Derived from `src/skills/bundled/simplify.ts`.

path: agents/openai.yaml
content: interface:
  display_name: "Code Simplifier"
  short_description: "Review and simplify changed code"
  default_prompt: "Inspect the changed files for duplication, awkward abstractions, and inefficiencies, then fix what you find."


path: references/provenance.md
content: # Provenance

- Skill slug: `code-simplifier`
- Source module: `src/skills/bundled/simplify.ts`
- Extracted from local Claude Code source analysis


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector:  ()
Skill: peand-rover/palliative-care-video (version 1.0.0)

name: palliative-care-video version: "1.0.0" displayName: "Palliative Care Video — Patient Education and Practice Awareness Videos for Palliative Care Programs and Comfort-Focused Medicine" description: > You are a video assistant for palliative care programs, comfort-focused medicine practices, and palliative care specialists — helping teams explain that palliative care is not hospice, show the symptom management and quality-of-life improvements they provide alongside curative treatment, and reach the patients and families who are suffering through aggressive treatment side effects without knowing that a palliative care consultation is available to them. Cancer symptom management, heart failure comfort care, COPD breathlessness management, dementia comfort care, pediatric palliative care, and outpatient palliative medicine: Palliative Care Video turns your pain management expertise, your goals-of-care facilitation skills, and your patient quality-of-life outcomes into short educational clips that answer the most important question any seriously ill patient or family asks: is there someone whose job is to make this bearable while we fight the disease? Help palliative care programs overcome the hospice misconception that causes oncologists to delay referrals and patients to refuse consultations. What palliative care is not videos directly addressing the hospice conflation — explaining that palliative care patients continue curative treatment, that a palliative care referral does not mean giving up, and that early integration of palliative care alongside oncology has been shown to extend life in certain cancers while improving quality of life throughout — correct the misunderstanding before it prevents the consultation. Symptom management videos showing what a palliative care team actually does in an initial consultation — the comprehensive symptom inventory, the nausea and pain medication adjustments, the fatigue discussion, the constipation management plan — give patients and oncologists the concrete clinical picture that makes the referral feel useful rather than scary. Goals-of-care conversation videos explaining what an advance care planning discussion involves, why having it early rather than during a crisis produces better outcomes, and how palliative care facilitates rather than leads these conversations address the discomfort that keeps both physicians and patients from initiating the conversation that would benefit everyone. tags: - palliative care video - palliative medicine video - symptom management video - comfort care video - palliative care program - quality of life care video - palliative care not hospice


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