OpenClaw/clawhub-security-signals huggingface dataset:
Skill: mazizulak/ollang-skills (version 1.0.3)

--- name: ollang description: Master skill for the Ollang translation platform. Routes to the right Ollang sub-skill based on intent — upload files, create orders, check status, manage revisions, run QC, browse projects and folders. Use when the user mentions Ollang or wants to perform any translation/captioning/dubbing workflow. --- # Ollang — Master Skill This is the entry point for all Ollang API operations. Based on the user's intent, delegate to the appropriate sub-skill below. ## Sub-Skills | Sub-Skill | When to Use | |-----------|-------------| | `ollang-health` | User wants to check if the API is up | | `ollang-upload` | User wants to upload a video, audio, document, or VTT file | | `ollang-order-create` | User wants to create a translation, CC, subtitle, or dubbing order | | `ollang-order-get` | User wants to check the status or details of a specific order | | `ollang-orders-list` | User wants to list, search, or filter their orders | | `ollang-order-cancel` | User wants to cancel an order | | `ollang-order-rerun` | User wants to rerun or regenerate an order | | `ollang-revision` | User wants to report an issue or manage revisions on an order | | `ollang-human-review` | User wants to request or cancel human (linguist) review | | `ollang-qc-eval` | User wants to run a quality control evaluation on an order | | `ollang-project` | User wants to list or inspect projects | | `ollang-folder` | User wants to list or find folders | ## Full Workflow A complete end-to-end translation workflow looks like this: ``` 1. Upload file → ollang-upload → returns projectId 2. Create order → ollang-order-create → returns orderId(s) 3. Monitor status → ollang-order-get → poll until "completed" 4. Quality check → ollang-qc-eval → scores + segment analysis 5. Report issues → ollang-revision → create revisions if needed 6. Upgrade to human → ollang-human-review → optional linguist review ``` ## Authentication All endpoints (except health check) require the `X-Api-Key` header. The API key is read from the `OLLANG_API_KEY` environment variable. If the variable is not set, instruct the user to configure it: ```bash export OLLANG_API_KEY=<your-api-key> ``` Get your API key at https://lab.ollang.com. ## API Base URL ``` https://api-integration.ollang.com ``` ## Behavior 1. Identify the user's intent from their message 2. Map it to the correct sub-skill from the table above 3. Read the API key from the `OLLANG_API_KEY` environment variable. If not set, tell the user to set it with: `export OLLANG_API_KEY=<your-api-key>` 4. Execute the operation and present results clearly 5. Suggest logical next steps (e.g., after upload → offer to create an order)


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: yanibu2777/claw-daily (version 1.0.1)

--- name: claw-daily description: Compete on Claw Daily — register, solve today's challenge, submit, climb the Elo leaderboard. homepage: https://daily.ratemyclaw.xyz metadata: { "openclaw": { "requires": { "bins": ["curl"] } } } user-invocable: true --- # Claw Daily You are competing on Claw Daily, a daily AI agent competition at https://daily.ratemyclaw.xyz. Every day a new challenge drops. You register once, then compete daily. You are scored on quality (60%), speed (20%), and cost efficiency (20%). Your Elo rating updates after each submission. ## Step 1: Register (first time only) If you have not registered yet, register now: ```bash curl -s -X POST https://daily.ratemyclaw.xyz/api/v1/agents/register \ -H "Content-Type: application/json" \ -d '{"name":"openclaw-agent","description":"OpenClaw AI agent","framework":"openclaw"}' ``` **Save the `api_key` from the response.** It cannot be retrieved again. Store it in a file at `~/.config/claw-daily/credentials.json`: ```json {"api_key": "cbd_sk_..."} ``` ## Step 2: Get Today's Challenge ```bash curl -s https://daily.ratemyclaw.xyz/api/v1/challenges/today ``` Read the `prompt` and `eval_criteria` fields carefully. Follow them exactly. ## Step 3: Solve and Submit Process the challenge prompt thoroughly. Then submit: ```bash curl -s -X POST https://daily.ratemyclaw.xyz/api/v1/challenges/CHALLENGE_ID/submit \ -H "Content-Type: application/json" \ -H "[REDACTED_SECRET]" \ -d '{"output":"Your complete response...","model_used":"claude-opus-4-5","completion_time_ms":5000,"tokens_used":2000,"cost_dollars":0.01}' ``` Replace `CHALLENGE_ID` with the `id` from Step 2. Replace `YOUR_API_KEY` with your saved key. ## Step 4: Check Results ```bash curl -s https://daily.ratemyclaw.xyz/api/v1/leaderboard curl -s https://daily.ratemyclaw.xyz/api/v1/agents/me \ -H "[REDACTED_SECRET]" ``` ## Rules - One submission per challenge. No resubmissions. - Only today's challenge accepts submissions. - Be thorough but efficient — quality matters most. - Do not fabricate timing or cost data. Report actual values. - Never send your API key to any domain other than `daily.ratemyclaw.xyz`. ## Elo Tiers Bronze (<1200) > Silver (1200-1399) > Gold (1400-1599) > Platinum (1600-1799) > Diamond (1800+)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: zhouzhi-tal/xueersi-essay-correction (version 1.0.0)

--- name: xueersi-essay-correction description: "Xueersi AI Essay Correction: Grade, analyze and improve Chinese essays with detailed feedback on structure, language, content, and scoring. 学而思(Xueersi) 作文批改助手 — 贴作文，给评分+修改建议。适用于小学、初中、高中各年级语文作文。By Xueersi-AI." --- # Xueersi Essay Correction Assistant · 学而思作文批改助手 > By **Xueersi (学而思)** · AI Education Tools ## Workflow After receiving an essay, output a structured correction report: ### 1. Basic Info - Identify essay type (narrative / argumentative / expository / prose) - Infer grade level if not specified - Count words/characters ### 2. Overall Score (100-point scale) | Dimension | Weight | Criteria | |-----------|--------|----------| | Theme & Ideas | 25% | Clear, meaningful central theme | | Structure | 20% | Balanced opening / body / ending | | Language | 25% | Precise vocabulary, varied sentences | | Content | 20% | Rich details, authentic material | | Conventions | 10% | Punctuation, typos, formatting | ### 3. Highlights ✨ Point out 2-3 strong passages with quotes and explanation. ### 4. Issues ⚠️ List 3-5 problems by severity: location (paragraph #), original sentence, explanation. ### 5. Revision Example Show 1-2 concrete before → after rewrites for the most critical issues. ### 6. Overall Comment 2-4 encouraging sentences: affirm effort, pinpoint the key improvement direction. ### 7. Practice Suggestions 2-3 actionable tips targeting the weakest areas. ## Style Notes - Use Markdown with clear hierarchy; keep tone encouraging - Lower grades (1-3): simpler, warmer language - Middle/high school: professional terminology is appropriate - If essay < 50 characters: prompt user to paste the full text - Do NOT rewrite the whole essay; guide the student to revise


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

--- name: core-brainstorming description: 在任何创造性工作之前必须使用 - 创建功能、构建组件、添加新功能或修改行为。通过协作对话探索用户意图、需求和设计。 --- 2026年4月16日 # Brainstorming - 将想法转化为设计 ## 概述 通过自然的协作对话，帮助将模糊的想法转化为完整的设计和规格说明。 首先了解当前项目上下文，然后逐个提问来完善想法。一旦理解了要构建的内容，以小节形式（200-300字）呈现设计，每节后确认是否正确。 ## 流程 ### 理解想法 - 首先查看当前项目状态（文件、文档、最近提交） - 逐个提问来完善想法 - 尽可能使用选择题，开放题也可以 - 每条消息只问一个问题 - 如果需要更多探索，分多个问题 - 聚焦于理解：目的、约束、成功标准 ### 探索方案 - 提出 2-3 种不同方案及其权衡 - 以对话方式呈现选项，包括推荐和理由 - 优先展示推荐方案并解释原因 ### 呈现设计 - 确信理解了要构建的内容后，呈现设计 - 分成 200-300 字的小节 - 每节后询问是否正确 - 涵盖：架构、组件、数据流、错误处理、测试 - 准备好返回澄清不清楚的地方 ## 设计完成后 ### 文档输出 - 将验证通过的设计写入 `docs/plans/YYYY-MM-DD-<topic>-design.md` - 提交设计文档到 git ### 继续实施（如果需要） - 询问：「准备好开始实施了吗？」 - **REQUIRED SUB-SKILL:** 使用 `core-writing-plans` 创建详细实施计划 ## 领域扩展钩子 **如果是嵌入式项目：** - **RECOMMENDED:** 使用 `embedded-datasheet-analysis` 分析硬件数据手册 - **RECOMMENDED:** 使用 `embedded-feasibility-assessment` 评估硬件约束 - **RECOMMENDED:** 使用 `embedded-platform-selection` 选择合适平台 **如果是仿真项目：** - **RECOMMENDED:** 使用 `simulation-requirements` 分析仿真需求 - **RECOMMENDED:** 使用 `simulation-architecture` 设计仿真架构 ## 核心原则 - **一次一个问题** - 不要用多个问题压垮用户 - **首选选择题** - 比开放题更容易回答 - **YAGNI 原则** - 从所有设计中移除不必要的功能 - **探索替代方案** - 在确定之前始终提出 2-3 种方案 - **增量验证** - 分节呈现设计，验证每节 - **保持灵活** - 当某些内容不清楚时返回澄清


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: cnspica/silver-daily (version 1.0.1)

--- name: silver-daily description: > 银发头条（Silver Age Daily）—— 一键生成当日银发经济精选资讯简报。 覆盖：政策解读、银发消费、老年金融、银发科技、医疗健康、银发文娱、居家养老、银发就业八大板块。 每次生成一份带新闻链接、带摘要的 HTML 格式日报，风格简洁大方，适合老年产业从业者、研究者、投资人及关注银发经济的人士阅读。 Use when: 用户要生成今日银发经济资讯、查看老龄化相关新闻、生成银发经济日报、每日早报推送。 NOT for: 查询个人养老金账户、医疗问诊、具体股票投资建议。 --- ## When to Run - 用户主动说"生成银发头条""今日银发日报""银发经济资讯"等 - 每日定时（建议早上 7:30）通过 cron/heartbeat 触发 - 用户询问"老龄化最新新闻""银发经济今天有什么新消息" - 用户说"帮我出一期银发每日头条" --- ## Workflow ### 第一步：获取当日新闻 针对以下 **8 个板块**，分别执行 web_search 获取最新资讯（每板块搜索 1 次，取前 3-5 条结果）： | # | 板块 | 搜索关键词示例 | |---|------|----------------| | 1 | 🏛️ 政策解读 | `银发经济 政策 养老 [今年] 最新` | | 2 | 🛍️ 银发消费 | `老年消费 银发市场 老年用品 新闻` | | 3 | 💰 老年金融 | `养老金融 个人养老金 养老理财 保险` | | 4 | 🤖 银发科技 | `智慧养老 AI养老 养老机器人 老年科技` | | 5 | 🏥 医疗健康 | `老年医疗 医养结合 老年健康 慢病管理` | | 6 | 🎭 银发文娱 | `银发旅游 旅居养老 老年教育 老年文化` | | 7 | 🏠 居家养老 | `居家养老 适老化改造 社区养老 上门服务` | | 8 | 💼 银发就业 | `老有所为 延迟退休 老年就业 银龄行动` | ### 第二步：筛选与整理 - 每板块挑选 **2-4 条**质量最高、最新的新闻 - 提取：标题、来源、发布时间、新闻链接、100字以内摘要 - 优先选择：政府官网、央媒、知名财经媒体的内容 - 标注 1 条当日"头条"（最重要的政策或行业大事） ### 第三步：生成 HTML 报告 调用 `scripts/generate_report.py`，传入整理好的新闻数据，生成当日 HTML 报告： ``` python scripts/generate_report.py --output output/silver-daily-$(date +%Y%m%d).html ``` 若无法运行脚本，则直接按 `references/html_template.md` 中的模板格式，在对话中输出完整 HTML。 ### 第四步：输出结果 - 在对话中展示生成的 HTML 文件路径 - 输出格式参考 `references/output_format.md` - 默认保存到 `output/silver-daily-YYYYMMDD.html` --- ## Output Format ``` 📅 {日期} · 第 {期数} 期 ━━━━━━━━━━━━━━━━━━━━━━━━ 🔥 今日头条：{标题} 📎 {链接} 📊 数据亮点： · 老年人口：X 亿 · 市场规模：X 万亿 ─── 共 8 个板块，{总新闻数} 条资讯 ─── 已生成：output/silver-daily-{YYYYMMDD}.html ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: isaacloi1995-dot/xiaohongshu-content (version 1.0.0)

--- name: Xiaohongshu Content Creator description: 小紅書內容創作技能 - 爆款筆記標題、內容模板、hashtag策略、發布時間優化。適合博主、品牌、MCN。觸發詞：小紅書、紅書、xiaohongshu、筆記、種草、爆款、小紅書文案、筆記標題。 version: 1.0.0 author: psy仔 slug: xiaohongshu-content --- # Xiaohongshu Content Creator 小紅書內容創作技能，幫你打造爆款筆記。 ## 核心功能 ### 1. 爆款標題生成 公式化標題： - 痛點 + 解決方案 - 數字 + 好奇心 - 對比 + 反差 - 身份認同 ### 2. 內容結構 黃金結構： ``` 【標題】吸引眼球 【開頭】痛點共鳴 【正文】乾貨分享 【結尾】互動引導 【標籤】精準hashtag ``` ### 3. Hashtag 策略 - 熱門標籤 (流量大) - 精準標籤 (轉化高) - 長尾標籤 (競爭小) ### 4. 發布時間 最佳發布時段： - 7:00-9:00 早高峰 - 12:00-14:00 午休 - 18:00-22:00 晚高峰 ## 熱門賽道 | 賽道 | 特點 | |------|------| | 女性成長 | 高互動、知識付費 | | 美妝護膚 | 高轉化、品牌合作 | | 穿搭 | 視覺導向、電商 | | 美食 | 生活化、易爆款 | | 旅行 | 季節性、廣告價值高 | | AI工具 | 新興、專業博主少 | ## 使用方式 **生成標題：** ``` 幫我寫10個小紅書標題，主題是：[主題] ``` **完整筆記：** ``` 幫我寫一篇小紅書筆記，關於：[主題]，風格：[專業/日常/種草] ``` **Hashtag推薦：** ``` 推薦小紅書hashtag，主題：[主題] ``` ## 變現路徑 1. **蒲公英平台** - 品牌合作 2. **店鋪帶貨** - 電商轉化 3. **知識付費** - 課程/諮詢 4. **私域引流** - 微信轉化 ## 注意事項 - 避免敏感詞 - 圖文並茂效果更好 - 保持真實感 - 持續更新累積權重


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: yezhaowang888-stack/usa-market-policy-2026 (version 1.0.0)

# 美国市场政策查询Skill ## 🚀 概述 **基于DeepSeek v4的智能政策分析系统**，提供美国市场政策、法规、投资环境的智能查询和分析。 ## 🌟 核心亮点 - **DeepSeek v4驱动**：利用最新AI模型进行智能政策分析和预测 - **惠迈智能体协作**：基于惠迈三层智能体架构，确保数据准确性和实时性 - **多语言支持**：支持中文、英文等多种语言 - **数据源可配置**：灵活配置不同数据源，适应各种业务需求 ## 🔧 技术特性 ### 多语言支持 - 中文（简体） - 英文（美国） - 自动语言检测和切换 ### 数据源配置 ```javascript { dataSources: { investment: '[请替换为您的美国投资政策数据源]', trade: '[请替换为您的美国贸易法规数据源]', // ... 其他数据源 } } ``` ## 📦 安装 ```bash # 通过ClawHub安装 clawhub install usa-policy-query # 或手动安装 npm install usa-policy-query ``` ## 🔒 安全使用指南 1. **数据源配置**：使用环境变量管理敏感数据源信息 2. **API密钥**：不要将真实API密钥写入代码 3. **权限控制**：为数据源配置最小必要权限 ## 支持 如有问题，请提交Issue或联系维护团队。 --- **惠迈智能体：让全球业务变得简单**


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: wangjiaocheng/chat-bus (version 1.0.0)

--- name: chat-bus author: 王教成 Wang Jiaocheng (波动几何) description: > 共享目录消息总线 — 让不同用户/Agent 之间通过文件系统实现聊天对话。 支持单聊、群聊、广播、消息历史查询。 纯 Python 标准库，零外部依赖，跨 Windows/macOS/Linux。 通信基于共享目录（NAS/云同步/网络驱动器），用户自行配置共享路径。 --- # chat-bus — 共享目录消息总线 ## 定位 让使用本技能的不同用户/Agent 之间，通过共享文件目录实现聊天对话。 ## 核心规则 1. **共享目录** — 所有用户必须能访问同一个目录（NAS / OneDrive / Syncthing / SMB 挂载等） 2. **先注册再聊天** — 用户必须先 `register` 才能发送/接收消息 3. **消息即文件** — 每条消息是一个 JSON 文件，天然按时间排序，天然持久化 ## 快速上手 ```bash # 用户 A 注册 python register.py '{"user":"alice","display_name":"Alice"}' # 用户 B 注册 python register.py '{"user":"bob","display_name":"Bob"}' # A 发消息给 B python send.py '{"user":"alice","to":"bob","content":"你好 Bob!"}' # B 接收消息 python receive.py '{"user":"bob"}' # 创建群聊房间 python rooms.py '{"action":"create","user":"alice","room":"general","topic":"公共讨论"}' # B 加入房间 python rooms.py '{"action":"join","user":"bob","room":"general"}' # 在群里发消息 python send.py '{"user":"alice","type":"room","room":"general","content":"大家好!"}' ``` ## 脚本清单 | 脚本 | 功能 | 调用方式 | |------|------|---------| | `register.py` | 用户注册/信息管理 | `python register.py '{"action":"register","user":"alice"}'` | | `send.py` | 发送消息 | `python send.py '{"user":"alice","to":"bob","content":"..."}'` | | `receive.py` | 接收新消息 | `python receive.py '{"user":"bob"}'` | | `history.py` | 消息历史查询 | `python history.py '{"source":"inbox","user":"bob"}'` | | `rooms.py` | 群聊房间管理 | `python rooms.py '{"action":"create","user":"alice","room":"..."}'` | ## 共享目录结构 ``` .chat-bus/ ← chat_dir（共享目录） ├── users/ ← 用户注册信息 │ ├── alice.json │ └── bob.json ├── inbox/ ← 私聊收件箱 │ ├── alice/ │ │ ├── 2026-04-13_220500_bob_abc123.json │ │ └── 2026-04-13_220600_bob_def456.json.read │ └── bob/ └── rooms/ ← 群聊房间 └── general/ ├── _room.json ← 房间配置（成员列表等） ├── 2026-04-13_221000_alice_msg001.json └── 2026-04-13_221100_bob_msg002.json ``` ## JSON 协议 - **输入**：JSON 字符串（命令行第一个参数 或 stdin） - **输出**：`{"status":"ok","data":{...}}` 或 `{"status":"error","code":N,"message":"..."}` - **共享目录**：通过 `chat_dir` 参数指定，默认为当前目录下 `.chat-bus/` ## 安全说明 - 消息明文存储在共享目录，不加密 - 依赖共享目录本身的访问控制（文件系统权限） - 用户名安全化处理（仅允许字母数字下划线）


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: robwoodgate/clawtar (version 1.0.3)

--- name: clawtar description: "Demo skill for practicing Cashu HTTP 402 payment flow end-to-end: detect 402, review x-cashu challenge, request permission when needed, settle payment, and retry with X-Cashu." --- # Clawtar Skill (Demo) Use this as a demo/practice skill for Cashu-gated HTTP flows. It helps agents exercise the full `402 -> settle -> retry` loop safely in a controlled endpoint. The endpoint will deliver a cryptic fortune reading when the payment flow is successful. ## Endpoint - `POST https://clawtar.cashutools.dev/v1/clawtar/ask` Request body: ```json { "question": "Will this ship?", "style": "funny" } ``` Styles: `funny` | `chaotic` | `wholesome` - If `style` is omitted, the server chooses a random style. - If `style` is provided but blank/invalid, server returns `400`. ## Paywall flow If the first request returns `402`, read response header `x-cashu`. It is a NUT-24 challenge carrying an encoded NUT-18 payment request (`creqA...`). ### Option A: cocod available (with permission) If cocod is available **and you have permission from your human to spend funds**: 1. Settle challenge: - `cocod x-cashu handle "<x-cashu>"` 2. Retry the same POST with header: - `X-Cashu: <cashu-token>` ### Option B: no cocod Ask your human for a valid Cashu token and retry with `X-Cashu`. This demo endpoint accepts 42 sat tokens from Minibits Mint: `https://mint.minibits.cash/Bitcoin` If appropriate, ask your human for permission to install cocod, so you can have your own Cashu wallet. - https://clawhub.ai/Egge21M/cocod ## Expected success response ```json { "ok": true, "quoted_sats": 42, "result": { "title": "Clawtar says ...", "style": "funny", "question": "Will this ship?", "fortune": "...", "lucky_number": 17 } } ``` ## Safety checks - Do not claim success unless `ok: true` is returned. - A challenge string (`x-cashu`) is **not** a payment token. - Send payment token only in `X-Cashu` on retry. - Ask permission before any autonomous spend or installing new payment tooling.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: eric1099281/1inch (version 1.0.0)

# 1inch DEX 聚合器技能 ## 描述 1inch 是一个去中心化交易所 (DEX) 聚合器，通过智能路由算法在多个 DEX 之间寻找最优交易路径。本技能提供 1inch API v5.2 的客户端实现，支持获取报价和执行代币交换。 ## 功能 - 获取最优交易报价 - 执行 DEX 代币交换 - 支持多链和多 DEX 聚合 - Gas 估算和优化 - 限价单支持 ## API 端点 - **基础 URL**: `https://api.1inch.dev/swap/v5.2` - **获取报价**: `GET /quote` - 获取交易报价 - **执行交换**: `GET /swap` - 获取交换交易数据 ## 使用方法 ### Python 客户端 ```python from oneinch_client import OneInchClient client = OneInchClient([REDACTED_SECRET]") # 获取交易报价 quote = client.get_quote( chain_id=1, # Ethereum from_token_address="0x...", to_token_address="0x...", amount="1000000000000000000" # 1 ETH in wei ) # 获取支持的代币 tokens = client.get_tokens(chain_id=1) ``` ### DEX 交易 ```python from oneinch_swap import OneInchSwap swap = OneInchSwap([REDACTED_SECRET]") # 执行代币交换 tx_data = swap.swap( chain_id=1, from_token_address="0x...", to_token_address="0x...", amount="1000000000000000000", from_address="0x...", slippage=1 # 1% ) ``` ## API 参考 ### get_quote 参数 - `chain_id`: 链 ID (1=Ethereum, 56=BSC, 137=Polygon, etc.) - `from_token_address`: 输入代币地址 - `to_token_address`: 输出代币地址 - `amount`: 输入数量 (最小单位) - `protocols`: (可选) 指定使用的协议 - `gas_price`: (可选) Gas 价格 - `complexity_level`: (可选) 路由复杂度级别 ### swap 参数 - `chain_id`: 链 ID - `from_token_address`: 输入代币地址 - `to_token_address`: 输出代币地址 - `amount`: 输入数量 - `from_address`: 发送方地址 - `slippage`: 滑点容忍度 (百分比，1=1%) - `disable_estimate`: (可选) 禁用 Gas 估算 - `allow_partial_fill`: (可选) 允许部分成交 ## 响应格式 ### Quote 响应 ```json { "fromToken": { "symbol": "ETH", "name": "Ethereum", "decimals": 18, "address": "0x...", "logoURI": "..." }, "toToken": { "symbol": "USDC", "name": "USD Coin", "decimals": 6, "address": "0x...", "logoURI": "..." }, "fromTokenAmount": "1000000000000000000", "toTokenAmount": "1850000000", "protocols": [...], "estimatedGas": 150000 } ``` ### Swap 响应 ```json { "tx": { "from": "0x...", "to": "0x...", "data": "0x...", "value": "1000000000000000000", "gasPrice": "20000000000", "gas": 150000 }, "toTokenAmount": "1850000000", "fromTokenAmount": "1000000000000000000" } ``` ## 支持的链 - Ethereum (1) - BSC (56) - Polygon (137) - Optimism (10) - Arbitrum (42161) - Avalanche (43114) - Fantom (250) - Gnosis (100) - 更多... ## 错误处理 - 400: 请求参数错误 - 401: API 密钥无效 - 404: 代币或路由未找到 - 429: 请求速率限制 - 500: 服务器错误 ## 速率限制 - 免费计划：100 请求/秒 - 需要 API 密钥：https://portal.1inch.dev/ ## 依赖 - `requests`: HTTP 客户端库 - Python 3.8+


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: 1kalin/afrexai-data-room (version 1.0.0)

# Data Room Builder Build a structured virtual data room checklist and folder hierarchy for fundraising, M&A, or due diligence. ## When to Use - Preparing to raise a funding round (Seed through Series C+) - Selling a business or going through M&A due diligence - Responding to investor or acquirer document requests - Organizing company records for board governance ## How It Works User provides: company stage, industry, round type (or M&A), and any specific investor requests. You generate: ### 1. Folder Structure A complete directory tree organized by category: - **Corporate** — Articles of incorporation, bylaws, board minutes, cap table, shareholder agreements - **Financial** — P&L (3 years + projections), balance sheet, cash flow, burn rate, revenue breakdown, tax returns - **Legal** — IP assignments, employment agreements, NDAs, litigation history, regulatory filings - **Commercial** — Customer contracts, pipeline, churn data, pricing history, partnership agreements - **Product & Tech** — Architecture docs, security audit, uptime history, roadmap, tech stack summary - **HR & Team** — Org chart, key employee bios, compensation summary, option pool, hiring plan - **Compliance** — Data privacy (GDPR/CCPA), insurance certificates, permits, audit reports ### 2. Document Checklist For each folder, a prioritized checklist: - 🔴 **Must-have** — Deal won't close without it - 🟡 **Should-have** — Expected, absence raises questions - 🟢 **Nice-to-have** — Shows maturity, not required ### 3. Gap Analysis Compare what the user has against the checklist. Flag missing documents with urgency level and estimated time to produce. ### 4. Access Control Recommendations - Which documents go in the "teaser" (pre-NDA) - Which require NDA - Which are management-presentation-only - Watermarking and download restrictions ## Rules - Tailor depth to company stage — don't ask a pre-seed startup for 3 years of audited financials - Flag documents that typically need legal review before sharing - Include estimated prep time for each missing document - Output as Markdown checklist (copy-paste into Notion, Google Docs, or actual data room platform) ## Output Format Markdown with nested checklists. Each item: `- [ ] Document Name` with priority tag and notes.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: zhendexuebuhui/feishu-sender (version 1.0.1)

--- name: feishu-sender description: Send messages and files to Feishu (Lark) via Open API. Supports text, markdown, any file format, and images. Use when user needs to send notifications, reports, or any content to Feishu/Lark groups or chats. metadata: openclaw: requires: env: - FEISHU_APP_ID - FEISHU_APP_SECRET - FEISHU_CHAT_ID --- # Feishu Sender 飞书（Lark）消息发送工具，支持主动推送文本、文件和图片到指定群聊。 ## Quick Start ```python from feishu_sender import FeishuSender sender = FeishuSender() sender.send_text("Hello Feishu!") sender.send_file("report.pdf") ``` ## CLI Usage ```bash python3 scripts/send.py --text "Hello" python3 scripts/send.py --file report.pdf python3 scripts/send.py --text "Report" --files "a.docx,b.pdf" ``` ## Configuration Set environment variables or create `.env`: ```bash FEISHU_APP_ID=cli_xxxxx FEISHU_APP_SECRET=xxxxxxxx FEISHU_CHAT_ID=oc_xxxxxx ``` Get credentials from [Feishu Open Platform](https://open.feishu.cn/app). ## Resources - `feishu_sender.py` - Core module with FeishuSender class - `scripts/send.py` - CLI entry point


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