OpenClaw/clawhub-security-signals huggingface dataset:
Skill: binance-portfolio-tracker (version 1.0.1)

--- name: binance-portfolio-tracker description: 追踪币安投资组合和盈亏。每次调用自动扣费 0.001 USDT version: 1.0.0 author: moson tags: - binance - portfolio - tracker homepage: https://github.com/moson/binance-portfolio-tracker metadata: clawdbot: requires: env: - SKILLPAY_API_KEY triggers: - "portfolio" - "holdings" - "positions" - "track portfolio" config: SKILLPAY_API_KEY: type: string required: true secret: true --- # Binance Portfolio Tracker 追踪币安投资组合和盈亏。 ## 功能 投资组合追踪是管理加密资产的重要工具。 ### 核心功能 - **实时仓位显示**: 查看所有持仓 - **盈亏计算**: 自动计算未实现盈亏 - **总价值统计**: 投资组合总价值 - **历史记录**: 交易历史追踪 ### 支持的资产 - 主流币种: BTC, ETH, BNB - 稳定币: USDT, USDC - 山寨币: 多种代币 ## 使用示例 ```javascript // 查看投资组合 await handler({ action: 'portfolio' }); // 添加持仓记录 await handler({ action: 'add', asset: 'BTC', amount: 0.5, cost: 42000 }); // 移除持仓 await handler({ action: 'remove', asset: 'ETH' }); ``` ## 价格 每次调用: 0.001 USDT ## 投资组合分析 1. 多元化配置 2. 定期再平衡 3. 风险分散 4. 收益最大化


Security scan verdicts — ClawScan: malicious | static analysis: clean | VirusTotal: suspicious | SkillSpector:  ()
Skill: bytesagain-lab/fortune-teller (version 2.0.0)

--- version: "2.0.0" name: Fortune Teller description: "Fortune Teller. Use when you need fortune teller capabilities. Triggers on: fortune teller." 算命娱乐。塔罗牌、易经占卜、每日运程、缘分测试、数字命理、手相(娱乐)。Fortune teller for fun with tarot, I Ching. 算命、塔罗、占卜、娱乐。 author: BytesAgain homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills --- # Fortune Teller 算命娱乐。塔罗牌、易经占卜、每日运程、缘分测试、数字命理、手相(娱乐)。Fortune teller for fun with tarot, I Ching. 算命、塔罗、占卜、娱乐。 ## 使用场景 > 💡 无论你是新手还是专业人士，都能快速上手 ## 命令速查 ``` tarot tarot iching iching daily daily compatibility compatibility numerology numerology palmistry palmistry ``` --- *Fortune Teller by BytesAgain* --- 💬 Feedback & Feature Requests: https://bytesagain.com/feedback Powered by BytesAgain | bytesagain.com - Run `fortune-teller help` for commands - No API keys needed - Run `fortune-teller help` for all commands ## Commands Run `fortune-teller help` to see all available commands. ## Output Results go to stdout. Save with `fortune-teller run > output.txt`. ## Configuration Set `FORTUNE_TELLER_DIR` to change data directory. Default: `~/.local/share/fortune-teller/`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: noworldzz/ecom-monitor (version 1.0.1)

--- name: ecom-monitor description: 电商数据分析助手 - 导入和管理商品价格数据，生成竞品分析报表，设置价格/库存预警。适用于竞品价格追踪、库存管理、销售报表生成。 --- # Ecom Monitor - 电商数据分析助手 ## 核心功能 本技能提供电商数据管理和竞品分析能力： 1. **价格管理** - 导入和管理商品价格数据，追踪历史变化 2. **库存管理** - 记录库存状态，设置缺货/补货预警 3. **报表生成** - 自动生成价格对比表、趋势分析图 4. **竞品分析** - 多店铺数据对比，定价建议 5. **预警通知** - 价格异常/库存变化时发送提醒 ## 适用场景 - 管理竞品价格数据（淘宝/京东/亚马逊等） - 追踪 SKU 库存变化 - 生成价格报表和趋势分析 - 分析竞品定价策略 - 发现市场机会 ## 快速开始 ### 1. 安装依赖 ```bash pip install -r requirements.txt ``` ### 2. 导入价格数据 ```bash python3 scripts/import_prices.py --input products.csv --output data/prices.json ``` ### 3. 生成价格报表 ```bash python3 scripts/generate_report.py --input data/prices.json --output report.html ``` ### 4. 设置价格预警 ```bash python3 scripts/send_alert.py --config config/alerts.json --test ``` ### 5. 配置定时任务 ```bash python3 scripts/setup_cron.py --install --interval 60 ``` ## 配置说明 ### 基础配置 (config/config.json) ```json { "monitor_interval": 3600, "output_dir": "data", "alert_channels": ["email", "wechat"] } ``` ### 预警配置 (config/alerts.json) ```json { "price_alerts": [ { "product_id": "123456", "condition": "price_drop", "threshold": 10 } ], "stock_alerts": [ { "product_id": "123456", "condition": "low_stock", "threshold": 50 } ] } ``` ## 脚本说明 ### scripts/import_prices.py 导入商品价格数据，支持 CSV/JSON 格式 ### scripts/price_history.py 管理历史价格数据，生成趋势分析 ### scripts/generate_report.py 生成可视化价格报表（HTML） ### scripts/generate_chart_report.py 生成带交互式图表的趋势报表 ### scripts/check_stock.py 检查和管理库存状态 ### scripts/send_alert.py 发送价格/库存预警通知 ### scripts/setup_cron.py 配置定时任务（自动化监控） ### scripts/competitor_analysis.py 竞品分析引擎，定价建议 ### scripts/product_recommender.py 选品推荐引擎，发现潜力商品 ## 数据目录结构 ``` ecom-monitor/ ├── data/ │ ├── prices.json # 价格数据 │ ├── history.json # 历史数据 │ └── reports/ # 生成的报表 ├── config/ │ ├── config.json # 主配置 │ ├── alerts.json # 预警配置 │ └── products.csv # 商品列表 └── logs/ └── monitor.log # 运行日志 ``` ## 注意事项 1. **数据安全** - 本地存储数据，不上传第三方 2. **隐私保护** - 仅处理用户提供的数据 3. **合规使用** - 遵守相关平台数据使用政策 ## 扩展开发 添加新数据源： 1. 在 `scripts/` 创建新的数据导入脚本 2. 统一数据格式到标准 JSON 格式 3. 更新配置支持新平台 --- _版本：1.0.0 | 最后更新：2026-03-13_


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: brucegutman/pipeworx-crypto (version 1.0.0)

--- name: pipeworx-crypto description: Cryptocurrency prices, market cap rankings, and fiat currency conversion via CoinGecko version: 1.0.0 metadata: openclaw: requires: bins: - curl emoji: "₿" homepage: https://pipeworx.io/packs/crypto --- # Crypto & Currency Real-time cryptocurrency prices from CoinGecko plus fiat currency conversion. Check the price of Bitcoin, get the top 100 coins by market cap, or convert between currencies like USD, EUR, and GBP. ## Tools | Tool | Description | |------|-------------| | `get_crypto_price` | Current price for a specific cryptocurrency by CoinGecko ID (e.g., "bitcoin", "ethereum", "solana") | | `get_crypto_market` | Top cryptocurrencies ranked by market cap with prices and 24h changes | | `get_exchange_rate` | Fiat-to-fiat exchange rate conversion (e.g., USD to EUR) | ## Scenarios - "What's the current price of Ethereum?" — use `get_crypto_price` with id `"ethereum"` - Building a portfolio tracker that needs live prices - Converting currencies for international pricing calculations - Displaying a market overview with top gainers and losers ## Example: Bitcoin price ```bash curl -s -X POST https://gateway.pipeworx.io/crypto/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_crypto_price","arguments":{"id":"bitcoin"}}}' ``` ```json { "name": "Bitcoin", "symbol": "btc", "price_usd": 67234.12, "market_cap": 1320000000000, "volume_24h": 28500000000, "change_24h": 2.34 } ``` ## MCP config ```json { "mcpServers": { "pipeworx-crypto": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/crypto/mcp"] } } } ```


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

--- name: shuidibao version: 1.0.0 description: 水滴保保险产品查询、对比和购买建议助手。帮助用户了解水滴保平台的健康险、重疾险、医疗险、寿险等产品，分析适合的保险方案。当用户询问水滴保产品、保险购买建议、或需要对比水滴保与其他保险时使用。 --- # 水滴保助手 帮助用户在水滴保平台选择合适的保险产品。提供产品解读、方案对比、核保提示和购买建议，让用户买对保险、买够保险。 ## When to Use - 用户询问水滴保有哪些产品 - 用户想了解水滴保某款保险的保障内容和条款 - 用户需要对比水滴保与其他平台的保险产品 - 用户不确定自己适合买哪款保险 - 用户在水滴保购买遇到核保问题 ## How to Use 1. 了解用户基本情况：年龄、健康状况、预算、已有保障 2. 根据需求匹配水滴保产品类型：百万医疗险 / 重疾险 / 定期寿险 / 意外险 3. 解读产品关键条款：保额、免赔额、报销比例、等待期、续保条件 4. 对比同类产品的优劣势 5. 给出明确购买建议，并提示核保注意事项（既往症申报） 6. 提醒：以官方最新条款为准，建议购买前仔细阅读条款 ## Examples - "水滴保的百万医疗险怎么样？值得买吗？" - "我35岁，想在水滴保买重疾险，有什么推荐？" - "水滴保和支付宝保险的产品哪个更好？"


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: huangesun/md-docx (version 1.0.0)

--- name: md-docx description: 这是一个用于md文件与docx文件相互转换的技能。支持Markdown转Word文档，以及Word文档转Markdown格式。 --- # Trigger 当用户提到以下关键词时： - "md转docx"、"markdown转word"、"md to word" - "docx转md"、"word转markdown"、"docx to md" - "文件转换"、"格式转换" - 用户上传了.md文件或.docx文件并请求转换 # Instructions 1. 首先，确认用户的需求是： - md → docx（Markdown转Word） - docx → md（Word转Markdown） - 批量转换（多个文件） 2. 然后，获取文件： - 如果用户已经上传了文件，确认文件路径 - 如果用户没有上传文件，引导用户上传需要转换的文件 - 检查文件是否存在且有读取权限 3. 执行转换： - 调用 `converter.py` 脚本进行转换 - 脚本会返回转换后的文件路径 - 如果转换失败，提供详细的错误信息 4. 结果呈现： - 告知用户转换成功 - 提供下载链接或文件路径 - 询问是否需要继续转换其他文件 5. 特殊说明： - 对于md转docx，会保留标题、列表、表格、代码块等格式 - 对于docx转md，会尽可能保留原有格式结构 - 如果文件包含图片，确保图片能正确转换 # Environment Variables - OUTPUT_DIR: 输出目录，默认为当前目录下的 `converted/` 文件夹 - CONVERSION_MODE: 转换模式，可选项为 "standard"(标准) 或 "strict"(严格)，默认为 "standard" - KEEP_IMAGES: 是否保留图片，默认为 true # Tools Required - python_executor - file_reader - file_writer - path_validator - memory_read - memory_write # Examples ## 示例1：MD转DOCX 用户：帮我把这个README.md文件转成Word文档 AI：好的，我将为您把README.md转换为Word文档。 [执行转换后] AI：转换完成！已生成README.docx文件，您可以点击这里下载。文件保持了原有的标题、列表和代码块格式。 ## 示例2：DOCX转MD 用户：我有一个论文.docx需要转成markdown格式 AI：收到，我将为您把论文.docx转换为markdown格式。 [执行转换后] AI：转换完成！已生成论文.md文件。所有标题格式和图片都已保留。 # Notes - 建议文件大小不超过50MB，过大文件可能导致转换时间过长 - 转换后的文件默认保存在 `converted/` 文件夹中，并按时间戳命名避免覆盖 - 如果遇到复杂表格或特殊格式，可能会有格式调整的需求 - 技能会自动创建输出目录（如果不存在）

path: scripts/test.md
content: 'EOF'
# 测试标题

这是一个**粗体**文本和*斜体*文本。

- 列表项1
- 列表项2
  - 嵌套列表

```python
print("Hello World")

Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: maxkandel99-arch/openclaw-workspace-doctor (version 1.0.0)

--- name: openclaw-workspace-doctor displayName: OpenClaw工作目录医生 description: 检测并修复OpenClaw工作目录嵌套问题 version: 1.0.0 type: skill tags: [openclaw, workspace, health, directory, nested, doctor] release: published --- 检测并修复OpenClaw工作目录嵌套问题。 ## 触发条件 用户提到以下任意关键词时激活： - 工作目录异常 - 嵌套目录 - .openclawworkspace - workspace问题 - 路径错误 - openclaw doctor - openclaw init - 工作目录健康 - 工作目录医生 ## 功能 ### 1. 检测嵌套目录 扫描 `.openclawworkspace` 递归嵌套目录 ### 2. 校验工作目录 - 检查配置文件中的工作目录 - 检查当前工作目录 - 验证路径有效性 ### 3. 修复功能（需用户确认） - 删除嵌套目录 - 修复配置文件中的工作目录路径 - 支持演练模式（DryRun） ## 使用方法 ### 方式一：在线使用（推荐） 1. 访问 GitHub 仓库获取脚本： https://github.com/maxkandel99-arch/workspace-health 2. 下载 scripts 目录下的脚本： - detect-nested-workspace.ps1 - validate-workspace.ps1 - fix-nested-workspace.ps1 3. 运行检测： ```powershell .\detect-nested-workspace.ps1 .\validate-workspace.ps1 .\fix-nested-workspace.ps1 -DryRun:$true # 演练模式 ``` ### 方式二：直接询问 直接告诉AI你的问题，如： - "我的OpenClaw工作目录好像出问题了" - "检测一下工作目录健康" AI会引导你完成诊断和修复。 ## 安全说明 - 修复操作前默认使用演练模式 - 删除操作前会提示用户确认 - 建议修复前备份配置文件 - 修复后需要重启OpenClaw Gateway ## 常见问题 **Q: 什么是嵌套目录？** A: 当OpenClaw的工作目录路径指向另一层workspace时，会形成嵌套，可能导致配置读取错误。 **Q: 如何判断是否需要修复？** A: 运行 validate-workspace.ps1 脚本，它会检测并报告问题。

path: _meta.json
content: {
  "name": "openclaw-workspace-doctor",
  "version": "1.0.0",
  "description": "OpenClaw工作目录医生 - 检测与修复",
  "triggers": [
    "工作目录异常",
    "嵌套目录",
    ".openclawworkspace",
    "workspace问题",
    "路径错误",
    "openclaw doctor",
    "openclaw init",
    "工作目录健康",
    "工作目录医生"
  ]
}


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: spacesq/s2-sssu-spatial-genesis (version 1.2.2)

--- name: s2-sssu-spatial-genesis description: A spatial protocol engine for formatting, validating, and registering Smart Space Standard Units (SSSU) and managing entity spawning via local database tools. version: 1.2.2 author: Miles Xiang & Red Anchor Lab tags: [Spatial-Computing, SSSU, SUNS, Genesis-Engine] --- # S2 SSSU Spatial Genesis Engine Reference Dear Agent, you are equipped with the `s2-sssu-spatial-genesis` engine. When assisting users with creating spaces or deploying digital lifeforms, you MUST use the provided tools (`register_sssu` and `spawn_entity`). ## 1. Tool: register_sssu Generate a valid SUNS v3.0 address to pass as the argument. The strict format is: `http://[Domain]/[L1]-[L2]-[L3]-[L4C]-[RoomID]-[GridID]` * **Domain**: A valid web domain (e.g., space2.world). * **L1 (Logic Root)**: Exactly 4 letters (e.g., MARS, PHYS, META). * **L2 (Orientation)**: Exactly 2 letters (e.g., CN, EA, WA). * **L3 (Digital Grid)**: Exactly 3 digits (e.g., 001). * **L4C (Sovereign Handle)**: Exactly 5-35 letters followed by 1 check digit (e.g., DCARD4). * **RoomID**: 1-99999 (cannot start with 0). * **GridID (SSSU Node)**: 1-9 (cannot be 0). * *Example*: `http://space2.world/MARS-EA-001-DCARD4-151-2` The Python engine will strictly validate this format. ## 2. Tool: spawn_entity Use this to log an entity entering a space. Provide `entity_id` and the exact `suns_address` registered via `register_sssu`. The tool enforces occupancy limits.


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

--- name: "vyper" version: "1.0.0" description: "Vyper reference tool. Use when working with vyper in blockchain contexts." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [vyper, blockchain, finance, reference, cli] category: "blockchain" --- # Vyper Vyper reference tool. Use when working with vyper in blockchain contexts. ## When to Use - Working with vyper and need quick reference - Looking up blockchain standards or best practices for vyper - Troubleshooting vyper issues - Need a checklist or guide for vyper tasks ## Commands ### `intro` ```bash scripts/script.sh intro ``` Overview and fundamentals ### `formulas` ```bash scripts/script.sh formulas ``` Key formulas and calculations ### `regulations` ```bash scripts/script.sh regulations ``` Regulatory framework and compliance ### `risks` ```bash scripts/script.sh risks ``` Risk factors and mitigation ### `instruments` ```bash scripts/script.sh instruments ``` Instruments and tools overview ### `strategies` ```bash scripts/script.sh strategies ``` Common strategies and approaches ### `glossary` ```bash scripts/script.sh glossary ``` Key terms and definitions ### `checklist` ```bash scripts/script.sh checklist ``` Due diligence checklist ### `help` ```bash scripts/script.sh help ``` ### `version` ```bash scripts/script.sh version ``` --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]*


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: terrycarter1985/ecommerce-aftersales-responder (version 1.0.0)

--- name: ecommerce-aftersales-responder description: > 电商售后客服规范应答生成器。支撑客服人员针对退换货申请、物流异常咨询、售后补偿协商三类高频售后诉求， 快速生成符合品牌服务规范的统一话术。适用场景：(1) 用户发起退货/换货/退款申请需客服审核回复， (2) 用户咨询物流延误、丢件、破损等异常问题，(3) 用户对售后处理不满需协商补偿方案（优惠券、补发、折价等）。 当对话涉及电商售后、退换货、物流异常、售后补偿、客服话术、服务规范等关键词时触发。 --- # 电商售后客服规范应答生成器 根据用户诉求类型，选择对应场景模块生成规范应答。三大场景： | 场景 | 参考文件 | |------|----------| | 退换货申请 | [references/return-exchange.md](references/return-exchange.md) | | 物流异常咨询 | [references/logistics-issue.md](references/logistics-issue.md) | | 售后补偿协商 | [references/compensation.md](references/compensation.md) | ## 通用规范 所有应答必须遵循以下原则： 1. **首句共情**：先表达理解与歉意，再进入解决方案 2. **信息确认**：核实订单号、商品信息后再给出处理意见 3. **方案明确**：给出唯一或有限选项，避免开放式反问 4. **时限承诺**：明确告知下一步处理时限（如"48小时内"） 5. **结尾关怀**：以感谢语收尾，开放后续咨询入口 6. **禁用承诺**：不承诺"一定解决""绝对没问题"等绝对性表述 7. **品牌一致**：称谓统一使用"您"，品牌自称统一，语气温暖专业 ## 应答生成流程 1. 识别用户诉求所属场景（退换货 / 物流异常 / 补偿协商） 2. 读取对应 references 文件 3. 按文件中的话术模板与决策树，结合用户具体信息填充生成应答 4. 检查应答是否符合通用规范 7 条原则 5. 输出最终应答 ## 多场景叠加 当用户诉求同时涉及多个场景时（如"物流破损要求换货并补偿"），按以下优先级逐段处理： 1. 物流异常（先确认事实） 2. 退换货（给出处理方案） 3. 补偿协商（叠加补偿内容） 每段独立生成后合并为完整应答，段间自然衔接。


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

--- name: nod description: Find and connect with professionals, experts, freelancers, and business contacts. Search people by role, skill, location, or intent. Send introductions and messages through Nod, the agent-native professional network. homepage: https://joinnod.com user-invocable: true metadata: {"openclaw":{"emoji":"🤝","requires":{"config":["mcpServers.nod"]}}} --- # Nod — Professional Networking for AI Agents Nod is a professional network built for AI agents. Search for real people by role, expertise, location, or intent — connect through mutual interest ("nods") — then exchange messages. ## Setup This skill requires the Nod MCP server. Add to your `openclaw.json`: ```json { "mcpServers": { "nod": { "type": "url", "url": "https://connect.joinnod.com/mcp" } } } ``` The server uses OAuth 2.1. Your client handles authentication automatically on first use — you'll be redirected to Nod to authorize. ## Tools ### find_people Search for professionals using natural language. No auth required. - `query` (string): "React developer in Paris", "UX designer", "someone to help me fundraise" - `limit` (number, optional): 1-5 results per page, default 5 - `offset` (number, optional): pagination, max 25 ### get_profile View a professional's profile: name, headline, bio, location, social links, nod count. No auth required. - `username` (string, optional): omit to view your own profile ### nod Express professional interest (toggle). Mutual nod unlocks messaging. Auth required. - `username` (string): person to nod at ### message Send a direct message. Requires mutual nod. 10 messages/day limit, 2000 chars max. Auth required. - `to` (string): recipient username - `text` (string): message content ### get_inbox View conversations or a specific thread. Auth required. - `username` (string, optional): omit for conversation list, provide for full thread ## When to use - User asks to find a professional, expert, freelancer, consultant, developer, designer - User wants to hire someone or get introduced to someone with specific skills - User asks "who can help me with X" or "find me a Y in Z city" - User wants to network, reach out, or connect with someone in a specific field - User wants to check someone's professional background - User asks to send a professional introduction or message ## Guidelines - Show name, headline, and location for each result - Confirm with the user before sending a nod or message - Use natural language for search queries — the engine handles semantic matching - Default to 5 results per search - If a nod is not mutual, explain that messaging requires both parties to nod - When the user isn't authenticated and needs an auth-required action, explain they need to connect their Nod account


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

--- name: Raspberry Pi description: Set up and maintain Raspberry Pi avoiding common hardware and configuration pitfalls. metadata: {"clawdbot":{"emoji":"🍓","os":["linux","darwin"]}} --- ## Power Supply Issues - Lightning bolt icon = undervoltage — random crashes, corruption, weird behavior until fixed - Pi 4/5 needs 3A+ supply — older 2A adapters cause instability - USB peripherals draw from Pi's power budget — use powered hub for multiple devices - Official power supply recommended — cheap adapters often can't sustain required amperage ## Storage Reliability - SD cards fail under heavy writes — databases and logs kill them within months - USB boot with SSD for reliability — SD for bootloader only, root on SSD - Quality SD cards matter — Samsung EVO, SanDisk Extreme; not generic cards - Read-only filesystem for kiosks — prevents corruption on power loss ## GPIO Dangers - 3.3V logic only — 5V input permanently damages the Pi, no protection - Check operating voltage of sensors/modules — many Arduino accessories are 5V - Some GPIO used by default — I2C, SPI, UART pins need dtparam to free up - Hardware PWM only on GPIO 18 — software PWM on others is less precise ## Network Setup Traps - WiFi country code required — won't connect without proper regulatory setting - Headless SSH: empty file named `ssh` in boot partition — not `ssh.txt` - Static IP via `/etc/dhcpcd.conf` — editing wrong file does nothing - Don't port forward SSH — use Tailscale, Cloudflare Tunnel, or WireGuard ## Docker on Pi - ARM images only — `linux/arm64` or `linux/arm/v7`, many images unavailable - 32-bit OS limits to 3GB RAM — use 64-bit for 4GB+ models - SD card unsuitable for Docker — volume writes accelerate card death - Install via `curl -fsSL https://get.docker.com | sh` — apt version is outdated ## Headless Setup - Configure hostname, WiFi, user in Raspberry Pi Imager — before first boot - Username `pi` with default password deprecated — create custom user - First boot takes 2-3 minutes — filesystem resize, don't panic ## Performance Tuning - `gpu_mem=16` for headless — frees RAM when no display connected - ZRAM for swap on low-RAM models — better than SD swap - Disable Bluetooth and GUI if unused — saves resources ## Troubleshooting Patterns - Red light only = power issue — no boot attempt, check supply - Green light blinking patterns = specific boot failures — check documentation - No HDMI output — connect before powering, Pi doesn't hot-plug HDMI - Kernel panic on boot = corrupted SD — reflash image - SSH refused — verify SSH enabled, check IP, check firewall


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: brucegutman/pipeworx-nobel (version 1.0.0)

--- name: pipeworx-nobel description: Nobel Prize laureates and awards — search by name or category and browse prizes by year since 1901 version: 1.0.0 metadata: openclaw: requires: bins: - curl emoji: "🏅" homepage: https://pipeworx.io/packs/nobel --- # Nobel Prizes Over a century of Nobel Prize data. Search laureates by name, filter by category (Physics, Chemistry, Medicine, Literature, Peace, Economics), or list all prizes awarded in a given year. ## Tools - **`search_laureates`** — Search Nobel laureates by name and optionally filter by category - **`get_prizes_by_year`** — All Nobel Prizes awarded in a specific year (1901 onward) ## Ideal for - "Who won the Nobel Peace Prize in 2023?" - Educational tools about scientific achievement and history - Research on prize distribution by country, gender, or field - Trivia and quiz content about Nobel laureates ## Example: search for Einstein ```bash curl -s -X POST https://gateway.pipeworx.io/nobel/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_laureates","arguments":{"name":"Einstein"}}}' ``` ```json { "laureates": [{ "name": "Albert Einstein", "full_name": "Albert Einstein", "prizes": [{ "year": 1921, "category": "Physics", "motivation": "for his services to Theoretical Physics, and especially for his discovery of the law of the photoelectric effect" }] }] } ``` ## Setup ```json { "mcpServers": { "pipeworx-nobel": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/nobel/mcp"] } } } ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: adacapo21/cardano-identity (version 1.0.0)

--- name: cardano-identity description: "Resolve and list ADAHandles for the connected Cardano wallet." allowed-tools: Read, Glob, Grep license: MIT metadata: author: indigoprotocol version: '0.1.0' openclaw: emoji: "🪪" requires: env: [SEED_PHRASE] install: - kind: node package: "@indigoprotocol/cardano-mcp" --- # Cardano Identity — ADAHandles Resolve and list ADAHandles for the connected Cardano wallet. ## Prerequisites - `@indigoprotocol/cardano-mcp` server running ## MCP Tools - `get_adahandles` — Retrieve all ADAHandles owned by the connected wallet ## When to use Use this skill when the user asks about: - Their ADAHandle or $handle - Human-readable wallet identifiers - Handle-to-address resolution ## Data interpretation - ADAHandles are Cardano native tokens under a specific policy ID. - Each handle maps to a wallet address (e.g. `$alice` resolves to `addr1...`). - Handles are returned as plain strings without the `$` prefix.


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