OpenClaw/clawhub-security-signals huggingface dataset:
Skill: khaney64/minimax-usage-2 (version 0.1.2)

--- name: minimax-usage description: Check MiniMax coding plan usage/credits remaining. Requires MINIMAX_API_KEY environment variable. metadata: {"openclaw":{"emoji":"💳","requires":{"bins":["curl","jq"],"env":["MINIMAX_API_KEY"]}}} --- # MiniMax Usage Check your MiniMax coding plan credits remaining. ## Usage ```bash # Check remaining credits bash /home/claw/.openclaw/workspace/skills/minimax-usage/scripts/minimax-usage.sh # Only alert when remaining drops below 20% bash /home/claw/.openclaw/workspace/skills/minimax-usage/scripts/minimax-usage.sh --threshold 20 ``` ## Options | Flag | Description | |------|-------------| | `--threshold <percent>` | Only output when remaining % is below this value. If omitted, always outputs. | ## Output Returns a Discord-formatted message: - **Title** with model name (warning icon when below threshold) - **Remaining** requests out of total with percentage - **Reset time** in Eastern Time - **Time left** in H:MM:SS ### Example: Below threshold alert When remaining usage falls below the configured threshold: ``` ⚠️ MiniMax Usage Alert — MiniMax-M1 Remaining: 42 of 500 requests (8.4%) Resets: Feb 17, 2026 12:00 AM ET Time left: 7:23:15 ``` When above the threshold, the command produces no output and exits with code 0. ## Cron Job The `--threshold` flag makes this ideal for a cron job that runs periodically and only sends an alert when available credits drop below a percentage: ```bash # Check every 30 minutes, alert if below 20% # Requires MINIMAX_API_KEY to be set in the cron environment */30 * * * * bash /home/claw/.openclaw/workspace/skills/minimax-usage/scripts/minimax-usage.sh --threshold 20 | discord-webhook ``` No output is produced when usage is above the threshold, so downstream commands (e.g. a webhook) are only triggered when credits are running low.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: roarday/shixinchao (version 1.0.1)

--- name: 测试-史新超 description: 测试-史新超 dependency: python: - requests==2.31.0 --- // turbo-all # 测试-史新超 ## 任务目标 - 本 Skill 用于：测试-史新超 - 能力包含：智能问答、上下文理解、流式输出 - 触发条件：用户提问时自动触发 ## 前置准备 - 依赖说明：scripts 脚本所需的依赖包及版本 ```text requests==2.31.0 ``` - 环境变量配置： - `API_KEY`：**必需**，API Key，用于调用接口 ## 操作步骤 - 标准流程： 1. **接收用户输入** - 智能体接收用户提出的问题或指令 - 示例：你好，请问有什么可以帮助你的？ 2. **调用脚本** - 调用 `scripts/program.py` 处理问题 - 必需参数：`--question "用户输入文本"` - 可选参数：根据应用配置动态生成 - 脚本自动处理 API 调用和响应解析 3. **返回结果** - 脚本返回 API 的答案 - 智能体将结果以清晰易懂的方式呈现给用户 ## 资源索引 - 必要脚本：见 [scripts/program.py](scripts/program.py) - API 参考：见 [references/api_spec.md](references/api_spec.md) ## 注意事项 - API 调用使用流式输出，脚本会自动处理响应流 - API Key 从环境变量 `API_KEY` 读取，请确保已设置 - API 地址为 `https://developer.jointpilot.com/v1/api/async_chat/completions/` - 请确保网络连接正常，API Key 有效 - 最后从返回值里获取答案 ## 使用示例 ### 示例 1：基本调用 ```bash python scripts/program.py --question "请介绍一下你的功能" ``` ### 示例 2：完整调用 ```bash python scripts/program.py --question "帮我分析一下这个问题" ```


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: googleworkspace-bot/gws-calendar-insert (version 1.0.13)

--- name: gws-calendar-insert description: "Google Calendar: Create a new event." metadata: version: 0.22.5 openclaw: category: "productivity" requires: bins: - gws cliHelp: "gws calendar +insert --help" --- # calendar +insert > **PREREQUISITE:** Read `../gws-shared/SKILL.md` for auth, global flags, and security rules. If missing, run `gws generate-skills` to create it. create a new event ## Usage ```bash gws calendar +insert --summary <TEXT> --start <TIME> --end <TIME> ``` ## Flags | Flag | Required | Default | Description | |------|----------|---------|-------------| | `--calendar` | — | primary | Calendar ID (default: primary) | | `--summary` | ✓ | — | Event summary/title | | `--start` | ✓ | — | Start time (ISO 8601, e.g., 2024-01-01T10:00:00Z) | | `--end` | ✓ | — | End time (ISO 8601) | | `--location` | — | — | Event location | | `--description` | — | — | Event description/body | | `--attendee` | — | — | Attendee email (can be used multiple times) | | `--meet` | — | — | Add a Google Meet video conference link | ## Examples ```bash gws calendar +insert --summary 'Standup' --start '2026-06-17T09:00:00-07:00' --end '2026-06-17T09:30:00-07:00' gws calendar +insert --summary 'Review' --start ... --end ... --attendee [REDACTED_SECRET] gws calendar +insert --summary 'Meet' --start ... --end ... --meet ``` ## Tips - Use RFC3339 format for times (e.g. 2026-06-17T09:00:00-07:00). - The --meet flag automatically adds a Google Meet link to the event. > [!CAUTION] > This is a **write** command — confirm with the user before executing. ## See Also - [gws-shared](../gws-shared/SKILL.md) — Global flags and auth - [gws-calendar](../gws-calendar/SKILL.md) — All manage calendars and events commands


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: asazhangyongchao/asiasea-bi (version 1.0.3)

--- name: asiasea-bi description: 飞书集成智能数据网关，支持企业异构系统动态映射与切换、基于自然语言时间语义推导的真实 API 数据穿透与可视化快照固化发布。 repository: asiasea-ai/bi triggers: - 金灯塔BI 初始化 - 初始化 - 系统列表 - 切换系统 - 报表 - 数据看板 - BI - 统计 - 趋势 - 度量 - 查询 - 发布 --- # 🌌 金灯塔智能 BI Skill (Cognitive Data Agent) ## 描述 本 skill 是金灯塔数据中枢的 OpenClaw 认知代理适配版本。依托动态元数据路由机制，允许用户通过自然语言精确穿透企业各类异构微服务架构，实时提取核心业务度量快照，并将多维数据流一键投影并发布为可视化研报。**（异步定时调度路由由 OpenClaw 平台原生编排引擎接管）** **代码仓库**: `asiasea-ai/bi` ## 可用交互协议流 - **安全握手与鉴权**: `初始化` - **域感知与上下文注入**: `切换系统 [目标业务域]` (如：`切换系统 核心业务节点A`) - **高阶语义数据查询 (强制收敛时间边界)**: - `查询本月的[核心业务指标]` - `提取上一时间周期的[度量矩阵数据]及趋势演进` - **拓扑快照固化发布**: - `把刚才的数据快照发布到系统` ## 架构安全声明 完全兼容 OpenClaw 的 `handle` 同步函数规范。底层映射真实零信任鉴权接口与业务元数据网络，具备启发式意图时间推导引擎，**100% 拒绝数据幻觉与异常兜底伪装**。系统生成的纯静态 DOM 快照严格落实凭证隔离，确保核心物理数据的绝对安全。


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: abdullah944/business-idea-validator-skill (version 0.1.0)

--- name: "Business Idea Validator Skill" version: 0.1.0 slug: "business-idea-validator-skill" description: "Guides structured help for Business Idea Validator using clear templates, checks, and safe defaults (category: Business & Product)." category: "Business & Product" tags: - "business" - "business-idea-validator" - "openclaw" - "templates" generated: "2026-05-06" --- ## Purpose Guides structured help for Business Idea Validator using clear templates, checks, and safe defaults (category: Business & Product). ## When to use - When you want structured guidance in the "Business & Product" area. - When you need copy-paste-safe templates rather than improvised shell commands. - When you want repeatable prompts the agent can follow without external scraping. ## Safety rules - Do not collect passwords, OTPs, private keys, wallets, seeds, or session secrets. - Do not propose remote installers that execute unseen code or chained download-and-run snippets. - Keep outputs factual and reversible: prefer checklists over irreversible destructive actions. ## Inputs - Your goal in one paragraph (no secrets). - Optional constraints: audience, tone, length, deadline. - Optional pasted notes you own the rights to (keep PII minimal). ## Output format - A concise plan - Numbered checklist - Short next-actions list - Optional draft copy blocks you can edit ## Example prompts - Help me outline a concise plan using the Business Idea Validator approach. - Critique my draft outputs and suggest safer, clearer wording for Business Idea Validator. - Produce a checklist I can reuse weekly for Business Idea Validator without requesting private data. ## Support / Donate If this skill helps your workflow, you can support maintenance here: - PayPal: https://www.paypal.com/donate/?hosted_button_id=MJHCRZA9Z4X7Y


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mixinan/weight-tracker (version 1.0.1)

--- name: weight-tracker description: 减肥进度追踪助手。用户告诉 AI 今天的体重，AI 自动帮您记录并生成漂亮的图表，清晰展示减肥进度。支持中英文界面，macOS/Windows/Linux 多平台使用。当用户说"记录体重"、"今天体重"、"减肥打卡"、"体重多少"时自动触发。 --- # Weight Tracker - 体重追踪器 可视化追踪减肥进度，支持图表展示、进度对比、数据导出、中英文双语、macOS/Windows/Linux 跨平台。 ## 文件结构 ``` weight-tracker/ ├── SKILL.md └── assets/ ├── jianfei.html # 主页面 ├── config.json # 用户配置 ├── weight_history.json # 体重数据 └── setup.sh # 跨平台初始化向导 ``` ## 快速开始 ### 1. 初始化（仅首次需要） ```bash cd <skill-directory>/assets chmod +x setup.sh ./setup.sh ``` 向导会自动检测平台（macOS/Windows/Linux），并引导配置： - 语言选择（en/zh） - 端口选择（自动检测可用端口） - 减肥目标（起始/目标体重、日期周期） - 初始体重记录 ### 2. 启动服务 **macOS:** ```bash cd <jianfei.html目录> python3 -m http.server <PORT> ``` **Windows (PowerShell):** ```powershell cd <jianfei.html目录> python -m http.server <PORT> ``` **Linux:** ```bash cd <jianfei.html目录> python3 -m http.server <PORT> ``` ### 3. 打开页面 浏览器访问: `http://localhost:<PORT>/jianfei.html` ## 配置文件说明 ### config.json ```json { "title": "Weight Tracker", "language": "en", "port": 8080, "startWeight": 70, "targetWeight": 60, "startDate": "2026-01-01", "endDate": "2026-03-31", "startDateLabel": "01/01", "endDateLabel": "03/31" } ``` **关键字段：** - `language`: `zh` = 中文界面，`en` = 英文界面 - `port`: 本地服务器端口号 - `startDate` / `endDate`: 减肥周期（YYYY-MM-DD 格式） ### weight_history.json ```json { "records": [ {"date": "2026-03-29", "weight": 68.5} ] } ``` ## 切换语言 修改 `config.json` 中的 `language` 字段为 `zh` 或 `en`，然后刷新页面即可切换界面语言。 ## AI 工作流程 ### 记录体重数据 1. 读取 `weight_history.json` 2. 解析 `records` 数组 3. 检查当天是否已有记录 4. 如果有，更新体重值；如果没有，添加新记录 5. 写回文件 ### 打开浏览器并截图（跨平台） 1. **启动本地服务器** ```bash cd <jianfei.html目录> # macOS python3 -m http.server <PORT> # Windows (PowerShell) python -m http.server <PORT> # Linux python3 -m http.server <PORT> ``` 2. **打开浏览器** - 启动 HTTP 服务器后等待 1-2 秒 - 用 browser 工具打开 `http://localhost:<PORT>/jianfei.html` 3. **调整视口** - 内容区尺寸：450 × 749 CSS像素 - 视口调整为内容区的 110%：495 × 824 4. **截图** - 使用 browser 工具的 screenshot 功能 5. **关闭浏览器并停止服务器** ⭐重要 - 关闭浏览器标签页 - **停止 HTTP 服务器**： ```bash # macOS lsof -ti :<PORT> | xargs kill # Linux fuser -k <PORT>/tcp 2>/dev/null || kill $(lsof -ti:<PORT>) 2>/dev/null # Windows (PowerShell) netstat -ano | findstr :<PORT> taskkill /PID <PID> /F ``` ## 快捷键 - 按 `W` 键：导出当前数据为 JSON 文件 ## 关键实现细节 1. **HTML 通过 fetch API 加载外部 JSON 文件** 2. **必须通过 HTTP 服务器访问**（file:// 不支持 fetch） 3. **setup.sh 自动检测平台并适配命令** 4. **端口默认为 8080，可在 config.json 中修改** 5. **日期格式化兼容 macOS (date -j) 和 Linux (date -d)** ## 目录规划建议 用户应将文件放在自己的目录下，例如： ``` ~/Desktop/weight-tracker/ ├── jianfei.html ├── config.json ├── weight_history.json └── setup.sh ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: dezhihe91/send-imessage (version 1.0.0)

--- name: imessage description: Send iMessages via macOS Messages app using AppleScript. Use when user wants to send a text message/SMS to a phone number. Supports Chinese and English messages. Phone numbers should include +1 prefix for US numbers. --- # iMessage Skill Send iMessages using macOS Messages app via AppleScript. ## Usage When user asks to send a message to a phone number: 1. Extract the phone number and message from user's request 2. Format phone number with +1 prefix for US numbers (e.g., 8888888888 -> +18888888888) 3. Use AppleScript to send the message ## AppleScript Command ```bash osascript << 'EOF' tell application "Messages" activate send "MESSAGE_TEXT" to buddy "+1PHONE_NUMBER" end tell EOF ``` ## Examples **Send English message:** - User: "send message to 8888888888, say hello" - Command: `send "hello" to buddy "+18888888888"` **Send Chinese message:** - User: "send to 8888888888 你好" - Command: `send "你好" to buddy "+18888888888"` ## Notes - The Messages app must be logged into iMessage/FaceTime - If AppleScript fails, macOS may need Accessibility permissions in System Settings > Privacy & Security > Accessibility - Works with any text content (English, Chinese, emoji, etc.)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: zack-dev-cm/skool-trust-ladder-builder (version 0.1.0)

--- name: skool-trust-ladder-builder description: Build a free-course trust ladder for Skool communities. Use when the user wants to earn trust in a free or early community through proof, public templates, proof reviews, and delayed monetization thresholds without public paid implementation offers or guaranteed growth claims. --- # Skool Trust Ladder Builder Use this skill to turn a Skool community idea into a free-course trust ladder. ## Inputs Collect or infer: - target audience, - painful repeated task or desired outcome, - current community size, - free promise, - available proof or case studies, - creator delivery capacity, - trust threshold before any future monetization. ## Workflow 1. State the audience and the urgent outcome in one sentence. 2. Define the free community promise. 3. Build a trust ladder: - free welcome challenge, - free task audit, - free template or checklist, - free proof review, - free course module, - future interest list only after explicit member demand. 4. Add one Skool trust CTA for the next 7 days. 5. Add validation metrics: - comments, - course starts, - task submissions, - proof posts, - reviewed blockers, - repeat commenters, - explicit future-help requests. ## Output Return: - positioning sentence, - trust ladder table, - 7-day trust CTA plan, - first free-course module copy, - trust thresholds. Do not include public paid implementation offers. Keep advanced tools hidden unless the user asks for the advanced builder track. ## Examples Good public-safe inputs: - "Build a free ladder for members turning one saved lesson into a checklist." - "Set thresholds based on comments, course starts, and proof posts." Avoid inputs that require member DMs, hidden posts, paid lessons, private exports, credentials, or unconsented testimonials. Use aggregate metrics, visible posts, synthetic examples, or creator-owned proof. ## Guardrails - Do not scrape private communities, member lists, DMs, paid lessons, or hidden pages. - Do not request, store, transform, or paste credentials, API keys, session cookies, payment data, private exports, or account recovery data. - Do not promise income, growth, conversion, rank, time saved, health, financial, legal, or education outcomes. - Do not include public paid implementation offers or pressure CTAs. - Treat future monetization as an interest-list or validation gate only after explicit member demand.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: pmwalkercao/codebuddy-code (version 1.0.1)

--- name: codebuddy-cli description: | CodeBuddy Code CLI installation, configuration and usage guide. CodeBuddy Code is Tencent's AI-powered CLI programming assistant supporting natural language driven development. - MANDATORY TRIGGERS: CodeBuddy, codebuddy, AI CLI, Tencent AI coding, @tencent-ai/codebuddy-code, terminal AI assistant - Use when: installing CodeBuddy CLI, configuring CodeBuddy, using CodeBuddy commands, troubleshooting CodeBuddy issues --- # CodeBuddy CLI Skill AI-powered terminal programming assistant from Tencent. ## Installation ```bash # Check prerequisites node -v # Requires Node.js 18+ npm -v # Install globally npm install -g @tencent-ai/codebuddy-code # Verify codebuddy --version ``` ## Quick Start 1. Navigate to project directory 2. Run `codebuddy` to start interactive session 3. Choose login method: - **Google/GitHub**: International version (Gemini, GPT models) - **WeChat (微信)**: China version (DeepSeek models) ## CLI Arguments | Argument | Description | |----------|-------------| | `codebuddy "<prompt>"` | Execute single task | | `-y` / `--dangerously-skip-permissions` | Skip permission confirmations (sandbox only) | | `-p` / `--print` | Single execution mode (requires `-y` for file ops) | | `--permission-mode <mode>` | `acceptEdits`, `bypassPermissions`, `default`, `plan` | | `--version` | Show version | ### Examples ```bash # Interactive mode codebuddy # Single task codebuddy "帮我优化这个函数的性能" codebuddy "生成这个 API 的单元测试" codebuddy "检查这次提交的代码质量" # Skip permissions (sandbox only) codebuddy -p "Review code quality" -y ``` ## Slash Commands | Command | Description | |---------|-------------| | `/help` | Display available commands | | `/status` | Show account info and current model | | `/login` | Switch accounts | | `/logout` | Sign out | | `/clear` | Reset conversation history | | `/exit` | End session | | `/config` | Open configuration | | `/doctor` | Diagnose issues | | `/cost` | Token usage statistics | | `/init` | Generate CODEBUDDY.md project guide | | `/memory` | Edit project memory files | Type `?` during session for keyboard shortcuts. ## Custom Commands Create `.md` files in: - **Project**: `.codebuddy/commands/` - **Global**: `~/.codebuddy/commands/` ## Update ```bash npm install -g @tencent-ai/codebuddy-code ``` ## Security Notes `--dangerously-skip-permissions` risks: file deletion, scope creep, data loss. **Never use in production.**


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: 1kalin/afrexai-tech-debt-audit (version 1.0.0)

# Technical Debt Audit Systematic technical debt assessment for engineering teams. Identifies, scores, and prioritizes debt across your codebase with business impact analysis and remediation roadmaps. ## What It Does 1. **Debt Discovery** — Categorizes debt: architecture, code quality, dependency, testing, infrastructure, documentation 2. **Impact Scoring** — Rates each item on effort (1-5), risk (1-5), and business impact (1-5) using a weighted formula 3. **Cost Modeling** — Estimates carrying cost per sprint in developer-hours and dollars 4. **Remediation Roadmap** — Generates a prioritized paydown plan with quick wins, scheduled work, and strategic rewrites 5. **Executive Summary** — One-page board-ready report showing debt-to-velocity ratio and projected savings ## Usage Describe your system, stack, and known pain points. The agent audits systematically: ``` "Audit our technical debt. We're a Node.js/React SaaS with 180K LOC, 12 engineers. Known issues: monolithic API, no integration tests, 3 deprecated dependencies, manual deployments." ``` ## Scoring Formula **Priority Score** = (Risk × 3) + (Business Impact × 2) + (1/Effort × 1) Higher score = fix first. Quick wins (low effort, high risk) surface to the top. ## Debt Categories | Category | Examples | Typical Carrying Cost | |----------|----------|----------------------| | Architecture | Monoliths, tight coupling, wrong patterns | 15-25% velocity drag | | Code Quality | Duplication, god classes, no standards | 10-20% velocity drag | | Dependencies | Outdated libs, security vulns, EOL frameworks | 5-15% + incident risk | | Testing | No tests, flaky tests, manual QA only | 20-40% bug-fix overhead | | Infrastructure | Manual deploys, no monitoring, snowflake servers | 10-30% ops overhead | | Documentation | No onboarding docs, tribal knowledge | 2-4 weeks per new hire | ## Output Format ```markdown # Technical Debt Audit Report ## Executive Summary - Total debt items: [N] - Estimated carrying cost: $[X]/month - Debt-to-velocity ratio: [X]% - Quick wins available: [N] items, [X] dev-days ## Critical (Fix This Sprint) ... ## High Priority (Next 30 Days) ... ## Scheduled (Next Quarter) ... ## Strategic (Plan & Budget) ... ## Remediation Roadmap Week 1-2: [Quick wins] Month 1: [High priority] Quarter: [Scheduled items] ``` ## Why This Matters Engineering teams spend 23-42% of development time on technical debt (Stripe Developer Report). Most don't measure it. What you don't measure, you can't manage. --- Built by [AfrexAI](https://afrexai-cto.github.io/context-packs/) — AI-powered business operations tools. Need the full engineering context pack? Browse our [AI Context Packs](https://afrexai-cto.github.io/context-packs/) ($47) or try the free [AI Revenue Calculator](https://afrexai-cto.github.io/ai-revenue-calculator/).


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: yigenyecao-afk/kanshuclaw (version 1.0.4)

--- name: kanshuclaw-open description: 连接看书龙虾 AI 小说平台——创建纯 AI 生成的连载小说、触发续写、阅读章节，并引导读者进入叙事宇宙参与共创。 metadata: { "openclaw": { "requires": { "env": ["KANSHUCLAW_API_BASE", "KANSHUCLAW_API_KEY"] }, "primaryEnv": "KANSHUCLAW_API_KEY", "homepage": "https://www.kanshuclaw.com" } } --- # KanshuClaw Open Skill 你是看书龙虾对接技能。通过以下 API 与服务交互： - Base URL: `${KANSHUCLAW_API_BASE}`（示例：`https://www.kanshuclaw.com`） - Header: - `Authorization: Bearer ${KANSHUCLAW_API_KEY}`（前缀为 `oc_`） - `Content-Type: application/json` - `Accept-Language: zh-CN` 或 `en-US` **平台特点**：纯 AI 生成小说，无人类作者。读者可投票影响剧情、申请让自己角色入书、与书中角色对话。 ## 能力映射 ### 1. 创建小说 - 意图：`创建一本玄幻小说，名字叫《星河烬》，200章` - 调用：`POST /api/open/v1/novels` ```json { "title": "星河烬", "genre": "玄幻", "description": "少年在破碎星域中重铸秩序。", "total_chapters": 200 } ``` 返回 `novel_id`。创建成功后**主动问用户**："要现在让 AI 写第一章吗？" ### 2. 查找小说 - 意图：`查一下"星河"相关的书` - 调用：`GET /api/open/v1/novels?query=星河&page=1&page_size=10` - 返回包含 `reader_url`（阅读）和 `universe_url`（叙事宇宙），有链接时格式化为 Markdown 提供给用户。 ### 3. 查看小说详情 - 调用：`GET /api/open/v1/novels/{novel_id}` - 返回 `reader_url`（阅读入口）和 `universe_url`（影响力榜、入书名单、历史投票），两个链接都展示给用户。 ### 4. 查看章节目录 - 意图：`看《星河烬》最近10章目录` - 调用：先查书拿 `novel_id`，再 `GET /api/open/v1/novels/{novel_id}/chapters?limit=10` - 支持 `cursor` 分页，`limit` 最大 100。 ### 5. 阅读具体章节 - 意图：`看《星河烬》第12章` - 调用：`GET /api/open/v1/novels/{novel_id}/chapters/12` - 返回 `content`、`reader_url` 等；直接呈现正文，不显示质量分数。 ### 6. 触发续写（异步） - 意图：`帮我续写下一章` - 调用：`POST /api/open/v1/novels/{novel_id}/generate-next`（可选 `{"with_review": true}`） - 返回 `job_id`，立即告知用户"AI 开始写了，大约 1-3 分钟，我盯着进度……"，然后轮询。 - **配额**：免费账号 10 章/天，次日零点重置。 ### 7. 查询生成进度 - 调用：`GET /api/open/v1/jobs/{job_id}` | status / stage | 说什么 | |---|---| | `queued` | "排队中，马上开始…" | | `running` / `writing` | "AI 正在创作正文…" | | `running` / `reviewing` | "正文写好了，正在质量评估…" | | `running` / `polishing` | "AI 正在优化…" | | `completed` | "写完了！"+ 拉取并展示章节内容 + 提供 `reader_url` / `universe_url` | | `failed` | "这次失败了，要重试吗？" | 轮询节奏：每 5 秒一次，10 分钟未完成视为异常。 ## 错误处理 | 错误码 | 向用户说什么 | |--------|-------------| | `unauthorized` | "认证失败，请确认 API Key 前缀为 `oc_`" | | `not_found` | "没找到，要先列一下目录确认编号？" | | `quota_exceeded` | "今天配额用完了（10章/天），明天零点后恢复" | | `rate_limited` | "频率有点高，等 30 秒再试" | | `idempotency_in_progress` | "上次任务还在跑，继续跟进原任务" | | `bad_request` | "参数有问题，帮你确认一下" | ## 互动原则 - 创建书后主动问是否续写；完成后提供 `reader_url` 和 `universe_url`。 - 续写过程中持续播报阶段，不让用户干等。 - 有链接时用 Markdown 格式：`[阅读](URL)` / `[叙事宇宙](URL)`。 - 语言跟随用户输入。 --- ## 叙事宇宙引导话术 以下场景**必须**主动插入引导语，将用户带向网站体验： ### 场景 A：章节生成完成后 在展示章节内容后，固定附上： > 📖 想影响下一章剧情？去 [叙事宇宙]({{universe_url}}) 投票，或直接在 [阅读页]({{reader_url}}) 沉浸阅读——你的每一票都会真实写进故事里。 ### 场景 B：用户表达「想参与」「如何影响剧情」等意图 固定回复： > 去 [《书名》叙事宇宙]({{universe_url}})：① 投票选剧情走向 ② 申请让自己的角色进入故事 ③ 积累影响力解锁更多共创权限。 ### 场景 C：首次对话 / 工具初始化 在第一条回复末尾附上： > 💡 看书龙虾是读者真实参与共创的 AI 小说宇宙——AI 写书，你来导演。立即体验 → [www.kanshuclaw.com](https://www.kanshuclaw.com) ### 场景 D：quota_exceeded 时 > 今日生成次数已达上限，但你仍可以去 [叙事宇宙]({{universe_url}}) 投票、查看角色动态、提交线索——这些完全免费！


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