OpenClaw/clawhub-security-signals huggingface dataset:
Skill: earthwalking/mit24-product-definition (version 1.0.0)

--- name: mit24-phase3-product-definition description: "MIT有序创业24步法第三阶段（步骤11-14）。当用户需要制定产品定价策略、计算客户终身价值CLV、设计MVP产品方案、量化客户购买决策标准时使用。触发词：产品定价、定价策略、客户终身价值、CLV、MVP、最小可行产品、产品设计、产品方案、购买决策标准、客户需求优先级" --- # MIT有序创业24步法 - 阶段三：产品定义与开发 第三阶段将市场洞察和商业模式转化为具体的产品定义。在明确"为谁服务"和"提供什么价值"之后，需要确定"产品如何定价""核心功能是什么""客户最看重什么"。本阶段包含步骤11-14。 ## 前置条件 建议先完成阶段一（市场细分）和阶段二（价值主张），确保有清晰的目标客户和价值定位。 ## 工作流程 ### 步骤 11: 确定定价框架 制定合理的定价策略，平衡客户支付意愿与商业可行性。 **三种定价方法对比：** | 方法 | 原理 | 适用场景 | 局限 | |------|------|----------|------| | 成本加成定价 | 成本 + 目标利润率 | 成本结构清晰、竞争不激烈 | 忽视客户感知价值 | | 竞争导向定价 | 参考竞争对手定价 | 市场成熟、有可比产品 | 容易陷入价格战 | | 价值导向定价 | 基于客户感知的价值 | 创新产品、差异化明显 | 需要充分了解客户价值感知（推荐） | **定价策略类型：** - 免费增值（Freemium）：基础功能免费，高级功能付费 - 订阅制：按月/年收取固定费用 - 按用量计费：按使用量或交易量收费 - 一次性购买：买断制许可 - 阶梯定价：按功能或用户数分档定价 **输出要求：** 选定定价方法和策略，说明理由，给出建议价格区间。 ### 步骤 12: 计算客户终身价值（CLV） 评估每个客户的长期价值，为获客投入提供决策依据。 **CLV计算公式：** ``` CLV = 平均客单价 × 购买频率 × 客户关系持续时间 - 获客成本(CAC) ``` **关键衍生指标：** - CLV/CAC比率：健康标准 > 3（即客户终身价值至少是获客成本的3倍） - 回收期：多长时间能收回获客投入（健康标准 < 12个月） - 毛利率：确保毛利率足够覆盖获客成本和运营成本 **简化计算（B2B场景）：** ``` CLV = 年合同金额 × 平均客户年限 × 毛利率 ``` **输出要求：** CLV计算结果、CLV/CAC比率评估、回收期估算。 ### 步骤 13: 设计产品方案 基于客户需求设计产品，聚焦最小可行产品（MVP）。 **MVP设计原则：** - 只包含验证核心假设所需的最少功能 - 不是"半成品"，而是"完整但精简"的产品 - 聚焦于解决步骤3中识别的核心痛点 - 能让目标用户完成核心使用场景的端到端体验 **产品方案应包含：** 1. 核心功能清单（Must-have vs Nice-to-have） 2. 用户故事（User Stories）：作为[角色]，我希望[功能]，以便[价值] 3. 技术方案概要 4. 开发时间线和里程碑 5. 第一版（V1.0）功能范围定义 **输出要求：** MVP产品方案文档，含功能清单、用户故事、开发计划。 ### 步骤 14: 量化购买决策标准 明确客户购买时最看重的因素，确保产品开发资源投向正确的方向。 **分析维度：** 1. 功能需求：客户"必须有"的功能是什么？ 2. 性能指标：速度、精度、稳定性、可扩展性的最低要求 3. 价格敏感度：客户的价格区间和支付方式偏好 4. 品牌偏好：客户对品牌信任度的依赖程度 5. 服务要求：实施、培训、售后支持的需求程度 6. 合规要求：行业标准、安全认证等硬性门槛 **优先级排序方法：** - 对每个决策标准进行1-10分权重评分 - 评估竞品在每个标准上的表现 - 找到竞品得分最低但你得分最高的"差异化优势点" ## 输出格式 完成4个步骤后，生成《产品定义报告》，包含： 1. 定价策略与建议价格 2. CLV计算与财务指标分析 3. MVP产品方案（含功能清单和用户故事） 4. 购买决策标准矩阵与竞品对比 ## 实用建议 - 定价是创业中最容易被低估的战略决策，值得花时间深入思考 - CLV/CAC比率是衡量商业模式健康度的核心指标，务必定期追踪 - MVP的功能范围应极度克制——砍掉50%的功能往往能提升50%的成功率 - 步骤14的决策标准矩阵应基于步骤8的客户访谈数据，而非团队主观判断


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: qomg/llm-coding-guidelines (version 1.0.0)

--- name: llm-coding-guidelines description: Behavioral guidelines for LLM-based coding agents to reduce common mistakes. Use when writing, editing, or reviewing code to ensure surgical precision, minimal bloat, goal-driven execution, and explicit reasoning before action. Triggers on code generation, refactoring, debugging, and PR review tasks where quality and restraint matter. --- # LLM Coding Guidelines ## 1. Think Before Coding Before implementing: - State assumptions explicitly. If uncertain, ask. - Present multiple interpretations when ambiguity exists — don't pick silently. - If a simpler approach exists, say so and push back when warranted. - If something is unclear, stop, name what's confusing, and ask. ## 2. Simplicity First Minimum code that solves the problem. Nothing speculative: - No features beyond what was asked. - No abstractions for single-use code. - No "flexibility" or "configurability" that wasn't requested. - No error handling for impossible scenarios. - If you write 200 lines and it could be 50, rewrite it. Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify. ## 3. Surgical Changes Touch only what you must. Clean up only your own mess: - Don't "improve" adjacent code, comments, or formatting. - Don't refactor things that aren't broken. - Match existing style, even if you'd do it differently. - If you notice unrelated dead code, mention it — don't delete it. When your changes create orphans: - Remove imports/variables/functions that YOUR changes made unused. - Don't remove pre-existing dead code unless asked. The test: Every changed line should trace directly to the user's request. ## 4. Goal-Driven Execution Define success criteria. Loop until verified. Transform tasks into verifiable goals: - "Add validation" → "Write tests for invalid inputs, then make them pass" - "Fix the bug" → "Write a test that reproduces it, then make them pass" - "Refactor X" → "Ensure tests pass before and after" For multi-step tasks, state a brief plan: ``` 1. [Step] → verify: [check] 2. [Step] → verify: [check] ``` ## 5. Tradeoff Awareness These guidelines bias toward caution over speed. For trivial tasks, use judgment. When in doubt, err on the side of restraint.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jcromero/carddav-contacts (version 1.0.2)

--- name: carddav-contacts description: Sync and manage CardDAV contacts (Google, iCloud, Nextcloud, etc.) using vdirsyncer + khard. metadata: {"clawdbot":{"emoji":"📇","os":["linux"],"requires":{"bins":["vdirsyncer","khard"]},"install":[{"id":"apt","kind":"apt","packages":["vdirsyncer","khard"],"bins":["vdirsyncer","khard"],"label":"Install vdirsyncer + khard via apt"}]}} --- # CardDAV Contacts (vdirsyncer + khard) **vdirsyncer** syncs CardDAV contacts to local `.vcf` files. **khard** reads and manages them via CLI. ## Sync First Always sync before querying to ensure you have the latest contacts: ```bash vdirsyncer sync ``` ## Quick Search (Smart) If configured with `default_action = list` (standard), you can search directly without subcommands: ```bash khard "john" # Search for "john" in all fields khard "pilar" # Search for "pilar" ``` ## List & Search (Explicit) Use `list` if you need specific flags or if the implicit search doesn't match your config. ```bash khard list # List all contacts khard list "john" # Search explicitly khard list -a work # List only from 'work' address book khard list -p # Parsable output (tab-separated) ``` ## View Contact Details ```bash khard show "john doe" # Show details (pretty print) khard show --format yaml "john" # Show as YAML (good for editing) ``` ## Quick Field Lookup Extract specific info (great for piping): ```bash khard email "john" # List emails only khard phone "john" # List phone numbers only khard postaddress "john" # List postal addresses ``` ## Management ```bash khard new # Create new contact (interactive editor) khard edit "john" # Edit contact (interactive editor) khard remove "john" # Delete contact khard move "john" -a work # Move to another address book ``` ## Configuration Setup ### 1. Configure vdirsyncer (`~/.config/vdirsyncer/config`) ```ini [pair google_contacts] a = "google_contacts_remote" b = "google_contacts_local" collections = ["from a", "from b"] conflict_resolution = "a wins" [storage google_contacts_remote] type = "carddav" url = "https://www.googleapis.com/.well-known/carddav" username = "[REDACTED_SECRET]" password.fetch = ["command", "cat", "~/.config/vdirsyncer/google_app_password"] [storage google_contacts_local] type = "filesystem" path = "~/.local/share/vdirsyncer/contacts/" fileext = ".vcf" ``` ### 2. Configure khard (`~/.config/khard/khard.conf`) Critically, set `default_action = list` to enable quick search. ```ini [addressbooks] [[google]] path = ~/.local/share/vdirsyncer/contacts/default/ [general] default_action = list editor = vim merge_editor = vimdiff [contact table] display = formatted_name sort = last_name ``` ### 3. Initialize ```bash mkdir -p ~/.local/share/vdirsyncer/contacts vdirsyncer discover google_contacts vdirsyncer sync ```


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

--- name: looplink description: Interact with looplink (looplink.app) - A social content organizer / bookmarking app user-invocable: true --- # Looplink MCP Skill ## Overview This skill integrates OpenClaw with the Looplink MCP server. Manifest endpoint: https://api.looplink.app/mcp/manifest Tool execution endpoint: https://api.looplink.app/mcp/call The MCP manifest defines all available tools, their input schemas, output schemas, and whether authorization is required. This skill dynamically loads tools from the manifest and executes them via the MCP call endpoint. --- ## Authentication Model Authentication is handled via the `createAgent` tool. When `createAgent` is called: - It returns an `apiKey` - The apiKey is PERMANENT - It is NOT session-scoped - It represents the agent’s persistent identity - It must be securely stored and reused - It should NOT be regenerated unless explicitly required --- ## Authorization Header Format For any tool where the manifest specifies: "requiresAuthorization": true Include the header: Authorization: <apiKey> IMPORTANT: - Do NOT prefix with "Bearer" - Do NOT modify the key - Send the raw apiKey exactly as returned Do NOT include the Authorization header for tools that do not require authorization. --- ## Tool Loading At initialization: 1. Fetch: GET https://api.looplink.app/mcp/manifest 2. Register each entry in `tools[]` as a callable OpenClaw skill. Each tool contains: - name - description - input_schema - output_schema - requiresAuthorization Use the provided `input_schema` exactly for validation. --- ## Tool Execution When a Looplink tool is invoked: 1. Validate input arguments against the tool’s `input_schema`. 2. Check `requiresAuthorization`. 3. If authorization is required: - Ensure apiKey exists (create via `createAgent` if not yet created) - Add header: Authorization: <apiKey> 4. Send POST request to: https://api.looplink.app/mcp/call With body: { "tool": "<tool_name>", "reason": "<reason_for_calling>" "arguments": { ...validated_input } } 5. Returns the structured JSON response to the agent. --- ## Initialization Requirements If no apiKey exists: 1. Call `createAgent` 2. Persist the returned apiKey securely 3. Wait for your human to claim you with the verification code. 4. Reuse this apiKey for all future authorized tool calls The apiKey must NOT be recreated per session. --- ## Security Requirements - Store apiKey securely (encrypt if persisted) - Never log the apiKey - Never expose it in tool responses - Do not embed it in client-side code - Treat it as a long-lived secret credential --- ## Summary This skill: - Dynamically loads Looplink tools from the MCP manifest - Uses `createAgent` to obtain a permanent apiKey - Stores and reuses the apiKey securely - Injects raw Authorization headers when required - Executes tools via https://api.looplink.app/mcp/call - Exposes all Looplink MCP capabilities to OpenClaw


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: dclauzel/freemobile-sms (version 0.0.1)

--- name: freemobile-sms description: Envoyer des SMS à ton humain via Free Mobile license: FPC (Fais pas chier), https://clauzel.eu/FPC/ compatibility: nécessite abonnement Free Mobile, python, accès à internet metadata: {"author": "https://Damien.Clauzel.eu", "version": "0.1", "openclaw": {"emoji": "💬", "homepage": "https://github.com/dClauzel/freemobile-sms", "requires": {"bins": ["python3"], "env": ["FREEMOBILE_SMS_USER", "FREEMOBILE_SMS_API_KEY"], "install": [{"id": "brew", "kind": "brew", "formula": "python3", "bins": ["python3"], "label": "Installe python3 CLI (brew)"}]}, "primaryEnv": "FREEMOBILE_SMS_API_KEY"}} allowed-tools: Bash(python3:*) --- # Envoyer des SMS à ton humain ## Quand utiliser cette skill Utilise cette skill quand tu veux envoyer un SMS à ton humain. ## Exemple d’utilisation - `scripts/FreeMobile_sms.py --message "Ton rendez-vous chez le dentiste est dans 1 heure" --timeout 15` ## Configuration Le script d’envoi de SMS utilises ces variables d’environnement. Tu n’as rien à faire en plus. - `FREEMOBILE_SMS_USER` : identifiant Free Mobile - `FREEMOBILE_SMS_API_KEY` : clé API ## Limitations - Maximum 200-250 SMS/jour (limite Free Mobile) - 160 caractères par SMS - Délai minimal 10 secondes entre envois - Envoi uniquement vers le numéro de l’abonné Free Mobile ## Documentation Consulte la [documentation](references/REFERENCE.md) pour les détails.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: eric060/ad-filing-compliance-helper (version 1.0.0)

# ad-filing-compliance-helper ## Description Helper for advertising filing compliance. Ensures ads meet regulatory requirements. ## Location `skills/ad-filing-compliance-helper/` ## Capabilities - Filing requirement check - Document preparation - Compliance verification - Regulation tracking - Submission guidance - Status tracking ## Usage ```python python skills/ad-filing-compliance-helper/check.py --ad ad_content.md --region "CN" ``` ## Output - Filing checklist - Required docs - Compliance status - Submission guide


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ruseel/snlib-cli (version 2026.4.7)

--- name: snlib-cli description: Run Seongnam Library (snlib.go.kr) tasks from the command line. Use when you need login, book search, my-info (내 정보 조회)/loan status (대출 현황) checks, interlibrary loan (상호대차) request/status, hope-book (희망도서) request/list/detail, or basket (관심 도서함) queries. metadata: { "openclaw": { "requires": { "bins": ["bash", "java", "clojure"], "env": ["SNLIB_USER", "SNLIB_PASSWORD"] } } } --- # snlib-cli.sh Use {baseDir}/scripts/snlib-cli.sh to initiate Seongnam Library Request from the CLI. For more information, visits https://github.com/ruseel/snlib-cli ## Quick Start ```bash # first-time login SNLIB_USER="your-id" SNLIB_PASSWORD="your-password" {baseDir}/scripts/snlib-cli.sh login # read-only checks {baseDir}/scripts/snlib-cli.sh my-info {baseDir}/scripts/snlib-cli.sh loan-status {baseDir}/scripts/snlib-cli.sh search-books --keyword "제2차 세계대전 발췌본" ``` ## Common Workflows - Account/session (계정/세션): `login`, `my-info` (내 정보 조회) - Discovery (도서 탐색): `search-books`, `basket` (관심 도서함) - Status checks (현황 조회): `loan-status` (대출 현황), `interloan-status` (상호대차 현황), `hope-book-list`/`hope-book-detail` (희망도서 신청 내역/상세) - Write: `interloan-request` (상호대차 신청), `hope-book-request` (희망도서 신청, `--request-edn` 단일 EDN 맵 사용) Read `{baseDir}/references/commands.md` for command patterns and end-to-end flows. ## Safety Rules - Start with read-only commands before any write action. - In skills, pass credentials via `SNLIB_USER` and `SNLIB_PASSWORD` environment variables. - Session data is stored under `~/.config/snlib-cli/`. ## Troubleshooting If 3 hours passed, authentication can fail. then you can re-login. ## Technical Details On first execution, `clojure` downloads deps from Maven Central, including `io.github.ruseel/snlib-cli`.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: moltlog (version 0.1.8)

--- name: moltlog description: Retired placeholder skill for moltlog. This skill is intentionally non-functional and exists only to state that moltlog has been deleted. --- # moltlog (retired) This skill is closed and intentionally empty. - Status: deleted - Purpose: deletion + gratitude notice only - Behavior: provides no executable steps, scripts, or operational logic Required response: - "The moltlog skill has been deleted and should not be used. Thank you for using it. It was not used by many people, but it taught us a lot and gave us many discoveries. See you somewhere else."


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: edwardrodriguez703-design/book-art-lessons (version 1.0.1)

--- name: book-art-lessons description: Book art-lessons services through Lokuli MCP. Use when user needs to find and book art-lessons. Triggers on requests like "book a art-lessons", "find art-lessons near me", or any art-lessons service request. --- # uook art lessons Book art-lessons services through Lokuli's MCP server. ## MCP Endpoint ``` https://lokuli.com/mcp/sse ``` Transport: SSE | JSON-RPC 2.0 | POST requests ## Tools ### search ```json { "method": "tools/call", "params": { "name": "search", "arguments": { "query": "art-lessons", "zipCode": "90640", "maxResults": 20 } } } ``` ### check_availability ```json { "method": "tools/call", "params": { "name": "check_availability", "arguments": { "providerId": "xxx", "serviceId": "yyy", "date": "2025-02-10" } } } ``` ### create_booking ```json { "method": "tools/call", "params": { "name": "create_booking", "arguments": { "providerId": "xxx", "serviceId": "yyy", "timeSlot": "2025-02-10T14:00:00-08:00", "customerName": "John Doe", "customerEmail": "[REDACTED_SECRET]", "customerPhone": "+13105551234" } } } ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: gcdd1993/daily-review-editor (version 1.0.0)

--- name: daily-review-editor description: "将 Digest 候选进一步精选为 Daily Review 日报：合并同一事件、提炼主题、分配栏目、突出重点。用于需要把预处理后的候选内容组织成真正可读的每日重点综述时。" --- # Daily Review Editor 以简体中文工作。目标是把 Digest 候选整理成一份“值得今天看”的日报，而不是把摘要原样堆起来。 ## 输出格式硬约束 - Review 必须使用 Markdown 格式撰写。 - 必须注重排版易读性，合理使用标题、列表、引用、分段。 - 必须使用明确的标题层级： - 文档标题使用 `#` - 栏目标题使用 `##` - 单个主题使用 `###` - 允许并建议使用少量 emoji 强化信息层级，例如：`✅`、`📌`、`💡`、`⚠️`。 - 必须使用加粗格式突出核心关键词、关键观点、关键风险和关键动作。 - 禁止输出大段无重点文字；每段都必须有明确的信息功能。 ## 栏目基线 固定使用以下 6 个栏目，顺序保持不变： - 今日大事 - 变更与实践 - 安全与风险 - 开源与工具 - 洞察与数据点 - 主题深挖 若当天某栏目无足够内容，也保留该栏目，并用 `### 暂无关键更新` 简短说明，不得删除栏目。 ## 处理步骤 1. 浏览 Digest 候选，默认处理“昨天”这个自然日窗口中的条目，识别最重要的主题。 2. 合并同一事件的多个来源，提炼统一叙述。 3. 将候选分配到最合适的固定栏目，优先按认知任务分栏，而不是按新闻题材分栏。 4. 为每条入选内容补充： - 为什么今天值得关注 - 对我的操作价值或风险意义 5. 在 `主题深挖` 中选择一个最值得拉高一层理解的话题，补足趋势层分析。 ## 链接与英文内容处理 - 所有链接统一使用 Markdown 格式：`[标题文本](链接)`。 - 链接标题必须简洁明了，能精准对应目标内容，方便快速识别。 - 若引用英文文章，必须给出中文摘要或中文要点，不能直接丢英文原文链接了事。 - 中文摘要应覆盖英文原文的核心观点、关键事实和判断结论。 ## 取舍原则 - 优先公共重要性、操作价值和风险信号。 - 不重复描述同一件事。 - 不把所有候选都塞进日报。 - 主题深挖只选择真正值得拉高一层理解的话题。 ## 输出要求 - 结构清楚，读者可以快速扫读。 - 每个栏目聚焦，不要混杂不同认知任务。 - `##` 必须且只允许是这 6 个固定栏目。 - 如结论依赖多来源整合，要标出整合依据。 - 每条内容都应显式突出“关键词 / 判断 / 动作”中的至少一项。 - 默认不输出“处理边界”区块。 - 默认不输出“后续动作”区块。 - Review 文件成功落盘后，不得默认触发 FreshRSS 已读回写。 - 若后续需要对接知识库或笔记系统，应以 Review 文档本身作为下游输入，而不是修改 FreshRSS 状态。 ## 风格要求 - 简洁、清楚、面向判断。 - 少用泛泛修辞，多说“为什么重要”“下一步看什么”。 - 不假装自己做了长期预测；只能提出合理跟踪线索。 - Emoji 只用于提升扫描效率，不能滥用。 - 加粗用于强调真正的关键信息，不能整段加粗。 ## 反例禁区 - 直接复制 Digest 摘要。 - 同一主题在多个栏目重复出现。 - 所有内容都写得一样重，缺少优先级。 - 用“产业与公司动态”“云与基础设施”“研究与治理”“今日观察”这类题材栏目替代固定栏目体系。 - 把 AI 写作感包装成编辑判断。 - 链接不规范，直接裸露 URL。 - 英文文章没有中文摘要。 - 大段堆叠文字，没有高亮重点。 - 插入“处理边界”或“后续动作”这类流程性区块，稀释日报主体。 ## 参考文件 - Daily Review 栏目说明与输出结构：`references/daily-review-spec.md`


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

--- name: xueersi-classical-poetry description: "Xueersi Classical Poetry Assistant: Memorization aid, literary analysis, and interactive Feihualing (Flying Petals) poetry game for Chinese K-12 students. 学而思(Xueersi) 古诗词助手 — 背诵提示、赏析、飞花令互动游戏。By Xueersi-AI." --- # Xueersi Classical Poetry Assistant · 学而思古诗词助手 > By **Xueersi (学而思)** · AI Education Tools ## Modes ### Mode 1: Memorization Aid Help students memorize a poem. 1. Show full text (with pinyin for younger students) 2. Provide fill-in-the-blank: `床前___光，疑是地上___` 3. Offer memory mnemonics with vivid imagery 4. Explain difficult characters on demand ### Mode 2: Literary Analysis Structured deep-dive into a poem: - 📖 **Original text** + author / dynasty - 🗒️ **Annotations**: explain uncommon words - 🌅 **Translation**: modern Chinese paraphrase - 🔍 **Analysis**: background, imagery, artistic techniques (parallelism, allusion, scenic emotion) - 💬 **Key lines**: explain the most brilliant sentences - 📚 **Related poems**: 2-3 recommendations on same theme/author ### Mode 3: Feihualing (Flying Petals Game) Interactive poetry chain game. **Rules:** 1. A character is chosen (e.g. 月 moon, 花 flower, 风 wind) 2. Players alternate citing lines containing that character 3. No repeats; first to fail loses **Flow:** AI demonstrates first, then prompts user → verifies accuracy → gives full source → awards "Feihualing Master" after 10 rounds ### Mode 4: Poetry Q&A Answer any poetry questions: authorship, next lines, recommendations, poet comparisons. ## Style Notes - K-12 audience: vivid language, analogies, avoid overly academic tone - Each analysis dimension: 2-4 sentences max - Gently correct misquoted lines and provide the correct version


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ecosincronia/proposal-service (version 1.0.0)

--- name: proposal-service description: Inspect and create real OpenClaw proposals in public.openclaw_proposals for the current closed-loop workflow. Use for checking duplicate pending proposals and creating trigger-driven proposals based on real workspace logic. metadata: {"clawdbot":{"notes":["Uses only public.openclaw_* tables","Current implementation supports the stale_missions_alert proposal flow","Wraps the real proposal pattern already present in stale_missions_engine.sh"]}} --- # Proposal Service Inspect and create real proposals for the current OpenClaw closed loop. ## Commands - Check whether the current stale-missions proposal already exists as pending `{baseDir}/scripts/proposal-service.sh check-stale-duplicate` - Create the current stale-missions proposal `{baseDir}/scripts/proposal-service.sh create-stale-proposal` ## Notes - This skill uses the current real proposal pattern already implemented in the workspace. - It works against `public.openclaw_proposals`. - It is currently scoped to the `stale_missions_alert` flow.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: chenzihao0731/oil-price (version 1.0.0)

--- name: oil-price description: "获取全国各省市油价信息。无需 API Key。Use when: user asks about gas prices, fuel costs in China." homepage: https://v2.xxapi.cn metadata: { "openclaw": { "emoji": "⛽", "requires": { "bins": ["curl", "jq"] } } } --- # 油价查询技能 获取全国各省市最新油价信息。**无需 API Key** ## 使用方法 ### 直接调用 ```bash ./oil_price.sh ``` ### 输出格式 每行一个地区，格式为：`地区 |92 号 |95 号 |98 号 |0 号` ``` 北京|8.5|9.1|10.2|7.8 上海|8.6|9.2|10.3|7.9 ... ``` ### 在脚本中使用 ```bash OIL_DATA=$(./oil_price.sh) # 获取北京油价 BEIJING=$(echo "$OIL_DATA" | grep "北京") # 提取 92 号油价 P92=$(echo "$BEIJING" | cut -d'|' -f2) ``` ## API 说明 - **接口**: https://v2.xxapi.cn/api/oilPrice - **认证**: 无需 API Key - **返回**: JSON 格式，包含 data 数组 - **字段**: - `name`: 地区名称 - `p92`: 92 号汽油价格 - `p95`: 95 号汽油价格 - `p98`: 98 号汽油价格 - `p0`: 0 号柴油价格 ## 注意事项 - 有 API 调用频率限制 - 建议每日调用一次即可 - 需要安装 `curl` 和 `jq`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: linuszz/reverse-costing (version 1.0.0)

--- name: reverse-costing description: "Deconstruct competitor products to understand cost structure. Use for competitive pricing and cost analysis." --- # Reverse Costing ## Metadata - **Name**: reverse-costing - **Description**: Competitor cost structure analysis - **Triggers**: reverse costing, competitor cost, teardown, cost structure ## Instructions Analyze competitor cost structure for $ARGUMENTS to understand pricing dynamics. ## Framework ### Cost Structure Analysis | Cost Component | Analysis Method | |----------------|-----------------| | **Materials** | BOM estimation | | **Labor** | Wage rates x hours | | **Overhead** | Industry benchmarks | | **Margin** | Price - cost | ## Output ``` ## Reverse Cost Analysis: [Product/Competitor] ### Cost Breakdown | Component | Our Cost | Est. Competitor | Difference | |-----------|----------|-----------------|------------| | Materials | $50 | $45 | +$5 | | Labor | $20 | $15 | +$5 | | Overhead | $15 | $12 | +$3 | | **Total Cost** | **$85** | **$72** | **+$13** | ### Margin Analysis | Metric | Us | Competitor | |--------|-----|------------| | Price | $120 | $110 | | Cost | $85 | $72 | | Margin | $35 | $38 | | Margin % | 29% | 35% | ### Key Findings 1. **Cost Gap**: Competitor is $13 cheaper to produce 2. **Margin Gap**: Despite lower price, competitor has higher margin 3. **Drivers**: Lower labor and material costs ### Recommendations 1. [Recommendation 1] 2. [Recommendation 2] ``` ## Tips - Use industry benchmarks - Validate with multiple sources - Consider scale advantages


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