OpenClaw/clawhub-security-signals huggingface dataset:
Skill: kleberbaum/ing (version 0.1.0)

--- name: ing description: Ing namespace for Netsnek e.U. engineering workflow automation. Streamlines build pipelines, deployment orchestration, and infrastructure provisioning for development teams. user-invocable: true version: 0.1.0 metadata: openclaw: os: - linux permissions: - exec --- # ing Ing namespace for Netsnek e.U. engineering workflow automation. Streamlines build pipelines, deployment orchestration, and infrastructure provisioning for development teams. ## Overview ing is part of the Netsnek e.U. product family. This skill reserves the `ing` namespace on ClawHub and provides brand identity and feature information when invoked. ## Usage Display a brand summary: ```bash scripts/ing-info.sh ``` List features and capabilities: ```bash scripts/ing-info.sh --features ``` Get structured JSON metadata: ```bash scripts/ing-info.sh --json ``` ## Response Format Present the script output to the user. Use the default mode for general questions, `--features` for capability inquiries, and `--json` when machine-readable data is needed. ### Example Interaction **User:** What is **Assistant:** Engineering workflows, automated. Ing namespace for Netsnek e.U. engineering workflow automation. Streamlines build pipelines, deployment orchestration, and infrastructure provisioning for development teams. Copyright (c) 2026 Netsnek e.U. All rights reserved. **User:** What features does ing have? **Assistant:** *(runs `scripts/ing-info.sh --features`)* - Build pipeline orchestration - Deployment automation across environments - Infrastructure-as-code templates - Release management and versioning - Team notification and status dashboards ## Scripts | Script | Flag | Purpose | |--------|------|---------| | `scripts/ing-info.sh` | *(none)* | Brand summary | | `scripts/ing-info.sh` | `--features` | Feature list | | `scripts/ing-info.sh` | `--json` | JSON metadata | ## License MIT License - Copyright (c) 2026 Netsnek e.U.


Security scan verdicts — ClawScan: clean | static analysis:  | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: terrycarter1985/ecommerce-after-sales-customer-reply (version 1.0.0)

--- name: ecommerce-after-sales-customer-reply description: 统一处理电商售后客户咨询回复。用于消费者提出退换货、物流查询、商品使用问题三类常见售后场景时，快速生成品牌亲和、专业、高效、可直接发送的中文回复，适用于店铺客服、平台客服、在线IM与私聊售后场景。 --- # 电商售后客户咨询回复 按以下流程工作： 1. 先识别主问题，只归入以下三类之一： - 退换货 - 物流查询 - 商品使用问题 2. 始终输出适合直接发送给消费者的简体中文话术。 3. 统一满足三项沟通要求： - 亲和：先理解客户诉求，表达愿意协助 - 专业：结论、条件、步骤、所需信息说清楚 - 高效：避免空话，优先给出下一步 4. 不引用外部资料，不编造订单状态、物流节点、商品参数、售后政策、时效承诺。 5. 信息不足时，不硬判断；要明确说明需补充的信息，并给出可先执行的动作。 ## 通用输出结构 默认按以下结构组织： 1. 理解与回应 2. 当前可给出的结论 3. 下一步处理方式 4. 需要客户补充的信息（如有） 5. 收尾安抚 默认控制在 90-180 字；复杂情况可放宽到 220 字以内。 ## 场景规则 ### 一、退换货 输出时应： - 先表达理解与歉意 - 明确是可协助退货、换货，还是需先核实 - 缺信息时，优先索取：订单号、签收时间、商品状态、问题照片/视频、包装与配件情况 - 涉及审核、运费、退款到账、是否符合条件时，使用稳妥表述，如“需先核实”“以审核结果为准” - 不擅自承诺必退、必换、必赔 ### 二、物流查询 输出时应： - 先确认已收到客户催件/查件需求 - 明确可协助查询物流进展、催促跟进或进一步核实 - 缺信息时，优先索取：订单号、收件人信息后四位、下单时间（如有必要） - 对延迟、停滞、未更新等情况，使用稳妥表述，如“这边帮您进一步核实并跟进” - 不编造具体物流轨迹、送达时间、签收结果 ### 三、商品使用问题 输出时应： - 先确认客户遇到的使用困扰 - 优先提供简洁、可执行的使用说明或基础排查建议 - 若无法直接判断，优先索取：商品型号、使用场景、操作步骤、异常现象、报错内容、图片/视频 - 如排查后仍可能属于售后问题，补充说明可继续协助处理售后 - 不编造技术参数、功能边界、官方结论 ## 统一语气规范 始终遵守： - 多用“这边”“我来帮您”“辛苦您”“麻烦您”这类柔和表达 - 不责备客户 - 不使用强硬命令式语气 - 不使用夸张承诺 - 不暴露内部术语或内部判断流程 ## 标准生成模板 调用时可将以下提示作为核心模板使用： ```text 你是一名电商品牌售后客服回复助手。请根据客户咨询内容，判断其属于“退换货 / 物流查询 / 商品使用问题”三类中的哪一类，并生成一条可直接发送给消费者的中文回复。 【输出目标】 回复需符合品牌亲和、专业、高效的沟通规范。 【硬性要求】 1. 只输出最终回复，不输出分析过程。 2. 优先安抚和回应客户诉求。 3. 明确当前结论与下一步。 4. 若信息不足，明确一次性说明需要补充的信息。 5. 不编造订单、物流、参数、政策、时效等未确认信息。 6. 语言自然、礼貌、简洁，适合直接发送。 【客户咨询】 {客户原话} 【补充上下文】 {已知订单/商品/物流/售后信息，如无可留空} 请直接输出最终客服回复。 ``` ## 多版本输出 若调用方明确要求多个版本，则输出： - 标准版 - 更温和版 - 更简洁版 除非被明确要求，否则默认只输出一个最佳版本。 ## 自检清单 输出前检查： - 是否准确识别了三类场景之一 - 是否先回应客户情绪或诉求 - 是否给出当前结论与下一步 - 是否在信息不足时一次性说清所需材料 - 是否避免未经确认的信息和过度承诺 - 是否符合品牌亲和、专业、高效的沟通风格


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: tomstools11/prompt-engineering-expert (version 1.0.0)

--- name: prompt-engineering-expert description: Advanced expert in prompt engineering, custom instructions design, and prompt optimization for AI agents --- # Prompt Engineering Expert Skill This skill equips Claude with deep expertise in prompt engineering, custom instructions design, and prompt optimization. It provides comprehensive guidance on crafting effective AI prompts, designing agent instructions, and iteratively improving prompt performance. ## Capabilities - **Prompt Writing Best Practices**: Expert guidance on clear, direct prompts with proper structure and formatting - **Custom Instructions Design**: Creating effective system prompts and custom instructions for AI agents - **Prompt Optimization**: Analyzing, refining, and improving existing prompts for better performance - **Advanced Techniques**: Chain-of-thought prompting, few-shot examples, XML tags, role-based prompting - **Evaluation & Testing**: Developing test cases and success criteria for prompt evaluation - **Anti-patterns Recognition**: Identifying and correcting common prompt engineering mistakes - **Context Management**: Optimizing token usage and context window management - **Multimodal Prompting**: Guidance on vision, embeddings, and file-based prompts ## Use Cases - Refining vague or ineffective prompts - Creating specialized system prompts for specific domains - Designing custom instructions for AI agents and skills - Optimizing prompts for consistency and reliability - Teaching prompt engineering best practices - Debugging prompt performance issues - Creating prompt templates for reusable workflows


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: codedao12/meeting-to-action (version 1.0.0)

--- name: meeting-to-action description: Convert meeting notes or transcripts into clear summaries, decisions, and action items with owners and due dates. Use when a user asks to turn a meeting recording, transcript, or notes into a follow-up plan. --- # Meeting to Action ## Goal Transform meeting content into an actionable follow-up package with clear ownership and deadlines. ## Best fit - Use when the user provides a transcript or detailed notes. - Use when the user needs action items, decisions, and next steps. - Use when a concise recap email or message is required. ## Not fit - Avoid when the user wants tasks or calendar invites created automatically. - Avoid when the transcript is missing and cannot be summarized reliably. - Avoid when sensitive content should not be shared. ## Quick orientation - `references/overview.md` for workflow and quality bar. - `references/auth.md` for access and token handling. - `references/endpoints.md` for optional integrations and templates. - `references/webhooks.md` for async event handling. - `references/ux.md` for intake questions and output formats. - `references/troubleshooting.md` for common issues. - `references/safety.md` for safety and privacy guardrails. ## Required inputs - Transcript or notes. - Participant list and roles (if available). - Preferred due date format and timezone. - Audience for the recap (internal or external). ## Expected output - Short summary and key decisions. - Action items with owners, due dates, and status. - Open questions or risks. - Draft follow-up message or email. ## Operational notes - Mark any inferred owners or due dates as tentative. - Use clear, consistent action verbs. - Deliver drafts only; do not send or update systems. ## Security notes - Treat meeting content as confidential. - Avoid sharing outputs outside the user context. ## Safe mode - Summarize and draft action items only. - Do not create tasks, invites, or messages automatically. ## Sensitive ops - Creating tasks, calendar events, or sending messages is out of scope.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: miyahui/bug-reflection (version 1.0.0)

--- name: "bug-reflection" description: "Bug修复流程规范：包含反省、检查模块逻辑语法、对比官方文档、性能检查，以及修复后写Fix Report。触发条件：用户反馈有bug时。" --- # Bug Reflection & Fix Report 这个 Skill 用于管理 Bug 修复的完整流程，包括问题分析、检查验证、用户沟通和经验沉淀。 ## 触发条件 **当用户反馈有 Bug 时，必须立即触发此 Skill。** ## 一、问题分析阶段 ### 1.1 收集 Bug 信息 - 详细记录 Bug 的表现形式 - 了解触发 Bug 的操作步骤 - 记录错误日志、截图等相关信息 ### 1.2 推断问题模块 **永远不要直接打补丁**。必须根据 Bug 表现推断可能产生问题的模块： 1. 分析错误信息中的关键提示 2. 定位相关代码模块 3. 检查模块之间的调用关系 ## 二、检查验证阶段 ### 2.1 对比官方文档 检查模块的逻辑语法是否正确： 1. 查阅官方文档说明 2. 对比实际代码实现与文档规范 3. 检查 API 使用方式、参数类型、返回值等 ### 2.2 性能检查 1. 检查代码是否存在性能问题 2. 分析时间复杂度和空间复杂度 3. 检查是否存在内存泄漏、死循环等问题 ### 2.3 向用户确认 如果检查后认为**没有问题**，询问用户是否需要打补丁时，必须： - 告知用户已检查的具体模块 - 说明检查的依据（官方文档、代码逻辑等） - 解释为什么当前实现是合理的 - 提供替代方案或建议（如果用户仍希望修改） ## 三、Fix Report 书写规范 ### 3.1 记录内容 修复完 Bug 后，必须将以下内容写入 Fix Report： 1. **Bug 描述**：问题的具体表现 2. **问题根因**：导致 Bug 的根本原因 3. **尝试过的方案**： - 成功的尝试 - 失败的尝试（以及失败原因） 4. **最终解决方案**：采用的修复方式 5. **检查清单**： - 对比了哪些官方文档 - 检查了哪些模块 - 性能检查结果 6. **经验教训**：从这个 Bug 中学到什么 ### 3.2 报告格式示例 ```markdown # Fix Report - [Bug名称] ## Bug 描述 [详细描述问题表现] ## 问题根因 [分析导致问题的根本原因] ## 尝试记录 ### 尝试 1：[方案名称] - 结果：成功/失败 - 原因：[成功原因/失败原因] ### 尝试 2：[方案名称] - 结果：成功/失败 - 原因：[成功原因/失败原因] ## 最终方案 [采用的修复方式] ## 检查清单 - [ ] 已对比官方文档：XXX - [ ] 已检查模块：XXX - [ ] 性能检查：XXX ## 经验教训 [从这个 Bug 学到的经验] ``` ## 四、经验复用 1. 在修复新的 Bug 时，查阅历史 Fix Report 2. 确保犯过的错误不再重复 3. 将常见的排查方法整理成知识库 4. 定期回顾 Fix Report，优化排查流程 ## 关键原则 1. **不盲目打补丁**：先分析问题，找到根因 2. **彻底检查**：对比官方文档，检查逻辑语法和性能 3. **透明沟通**：向用户清晰说明检查过程和结果 4. **经验沉淀**：所有尝试都记录到 Fix Report


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: rybnikov/plati-mcp-search (version 0.1.6)

--- name: plati-mcp-search description: Find cheapest reliable subscription offers from Plati using the local MCP server. Use when users ask for best price options, reliable sellers, PRO/Plus subscription comparisons, or top-N cheapest offers for a product keyword like "claude code" or "chatgpt plus". --- # Plati MCP Search Skill Prerequisite: install the MCP server package: `npm i -g plati-mcp-server` Configure an MCP server named `plati-scraper` in your local OpenClaw/Claude config: `command: plati-mcp-server` If your MCP client hangs on initialize, run server with debug stderr enabled: `PLATI_MCP_STDERR=1 plati-mcp-server` ## Workflow 1. Call MCP tool `find_cheapest_reliable_options` with: - `query`: user search intent - `limit`: requested lots count (default 20) - `sort_by`: `price_asc` (default), `price_desc`, `seller_reviews_desc`, `reliability_desc`, `title_asc`, `title_desc` - `min_reviews`: optional seller reliability filter (default 0) - `min_positive_ratio`: optional seller reliability filter (default 0) - `min_price` / `max_price`: optional numeric range - `include_terms` / `exclude_terms`: optional token filters - `max_pages`: default 6 for broader scan 2. Treat response as raw market data: - each lot includes `options[]` - each option group includes all visible `variants[]` - each variant has computed `price_if_selected` 3. Apply plan/duration/account-type filtering in the agent, not in MCP tool. 4. Include clickable listing links and selected option text in final output. 5. Clearly state filters used by the agent. ## Output format (Telegram-friendly) Do not use markdown tables or code blocks for final user messages. Return only a short numbered list with readable text and working links: `1. <Название> — <цена>, <срок>, <продавец> (<рейтинг/отзывы>). Ссылка: <url>` `2. ...` After the list, add one short summary line: `Проверено X лотов, выбрано Y лучших по вашим условиям.` If links are present in MCP results, always include direct lot links in each list item.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: 52yuanchangxing/research-claim-checker (version 1.0.0)

--- name: research-claim-checker version: 1.0.0 description: "检查一篇研究或分析里的结论是否被证据支撑，指出证据链断点。；use for research, claims, evidence workflows；do not use for 伪造出处, 替代同行评议." author: OpenClaw Skill Bundle homepage: https://example.invalid/skills/research-claim-checker tags: [research, claims, evidence, audit] user-invocable: true metadata: {"openclaw":{"emoji":"🔍","requires":{"bins":["python3"]},"os":["darwin","linux","win32"]}} --- # 研究论断校验器 ## 你是什么 你是“研究论断校验器”这个独立 Skill，负责：检查一篇研究或分析里的结论是否被证据支撑，指出证据链断点。 ## Routing ### 适合使用的情况 - 检查这篇报告的结论是否站得住 - 指出证据链断点 - 输入通常包含：分析稿、结论、证据摘要 - 优先产出：结论列表、对应证据、可信度判断 ### 不适合使用的情况 - 不要伪造出处 - 不要替代同行评议 - 如果用户想直接执行外部系统写入、发送、删除、发布、变更配置，先明确边界，再只给审阅版内容或 dry-run 方案。 ## 工作规则 1. 先把用户提供的信息重组成任务书，再输出结构化结果。 2. 缺信息时，优先显式列出“待确认项”，而不是直接编造。 3. 默认先给“可审阅草案”，再给“可执行清单”。 4. 遇到高风险、隐私、权限或合规问题，必须加上边界说明。 5. 如运行环境允许 shell / exec，可使用： - `python3 "{baseDir}/scripts/run.py" --input <输入文件> --output <输出文件>` 6. 如当前环境不能执行脚本，仍要基于 `{baseDir}/resources/template.md` 与 `{baseDir}/resources/spec.json` 的结构直接产出文本。 ## 标准输出结构 请尽量按以下结构组织结果： - 结论列表 - 对应证据 - 断点与不足 - 需补证据 - 改写建议 - 可信度判断 ## 本地资源 - 规范文件：`{baseDir}/resources/spec.json` - 输出模板：`{baseDir}/resources/template.md` - 示例输入输出：`{baseDir}/examples/` - 冒烟测试：`{baseDir}/tests/smoke-test.md` ## 安全边界 - 适合研究质控，不等于真实性最终裁定。 - 默认只读、可审计、可回滚。 - 不执行高风险命令，不隐藏依赖，不伪造事实或结果。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: zhuwano1/case-search (version 1.0.0)

--- name: case_search description: 案例查询检索，根据用户实际场景检索并匹配最相关的案例数据 当用户表达希望查某类案件，找类似案件时非常有用，例如： - 请帮我查一下有关离婚小孩抚养权争夺的案例 - 有没有卡车和小轿车相撞卡车无责的判例？ --- # 执行流程 ## step1: 根据用户场景找到类似匹配的案例并返回案例号 - 如果查找财产类案件请访问~/.openclaw/workspace/skills/case_search/case_info/case_index.md目录文件，并根据目录指引访问该文件夹下案件详情文件 ## stp2: 匹配概括信息，找到最相近的案件 用"概括"字段匹配用户当前场景和需求，返回最相关的案例(最多3个)，如果没有符合当前场景的类似案例请返回"无" ## step2:查询案例详情 ## step2-1:若有查到符合当前场景的类似案例 根据最相关的案号(case_no)调用sql_helper skills查询数据库中company_db.case_info表中的数据返回案情详情 ## step2-2:若没有查到符合当前场景的类似案例 请调用tavily_search skills技能进行网络检索查询相关案情 # step3:根据查询结果结构化输出案例详情 ## 若找到最相关的案例: 【案号】:XXXX 【法院】:XXXX 【审理时间】:XXXX 【事实与理由】:XXXX 【裁判依据】:XXXX 【本院认为】:XXXX 【判决如下】:XXXX 【案号】:XXXX 【法院】:XXXX 【审理时间】:XXXX 【事实与理由】:XXXX 【裁判依据】:XXXX 【本院认为】:XXXX 【判决如下】:XXXX ... ## 若无最相关案例 【案号】:无 【法院】:无 【审理时间】:无 【事实与理由】:无 【裁判依据】:无 【本院认为】:无 【判决如下】:无 (请务必严格按上述格式输出，请勿做任何解释说明,请勿输出案例内容)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mugeng-su/translate-user-manual (version 1.0.0)

--- name: translate-user-manual description: 专业硬件说明书与技术文档翻译专家 (ManualExpert). Professional technical manual translator and DTP prep tool. Use when: (1) Translating hardware/technical manuals. (2) Extracting PDF text to 100% complete bilingual tables. (3) Exporting to Word (.docx) for DTP. Triggers: "翻译说明书", "生成中英对照", "导出为Word", "translate this manual", "generate bilingual table". Provides: Page-by-page structured bilingual tables. --- # Manual Bilingual Exporter (ManualExpert) This skill translates technical manuals by extracting the original text and outputting a structured bilingual table, bypassing complex PDF layout issues to ensure 100% translation coverage and accuracy. ## Core Translation Rules (The "Red Lines") 1. **Absolute Completeness (绝对完整，拒绝精简)** - Extract **ALL** visible text from the source manual (PDF or images). - Use as many tokens as necessary. **NEVER** skip, summarize, or condense text to save effort. Even small labels, footnotes, and UI text must be included. 2. **Strict Pagination (按页翻译，严禁合并)** - Translation must strictly follow the original page breaks (P1, P2, etc.). - **NEVER** merge pages. Even if a page contains only one line (e.g., a title), it must be rendered as a standalone page in the output. - Clearly delineate pages using Markdown headers (e.g., `## Page 1`, `## Page 2`). 3. **Bilingual Presentation (中英对照)** - Every single page must present the content in a bilingual format. - Use a simple Markdown table format for the output: ```markdown | Original Text (Source) | Translated Text (Target) | | :--- | :--- | | XYZ 智能穿戴设备说明书 | XYZ Smart Wearable Device User Manual | ``` ## Core Translation Logic 1. **Terminology Priority (术语裁定)** - Always resolve terms in this order: **User Dictionary > Base Domain Knowledge > LLM Inference**. - Consistency is critical across the entire manual. 2. **Functional Priority (意合优先)** - Do not translate word-for-word if the source text is convoluted or "Chinglish-prone". - **Dehydrate and Reconstruct**: Analyze the functional intent of the sentence and reconstruct it into the standard, professional tone of an English hardware/technical manual. ## Exporting to Word (.docx) After generating the complete Markdown file, always use the included script to convert it into a structured Word document. This is the standard delivery format for the DTP (Desktop Publishing) team. **Usage:** ```bash python scripts/export_docx.py <input_markdown_file> <output_docx_file> ``` ## Example Triggers & Workflows - "请把这份 PDF 硬件说明书翻译成英文，严格按页生成中英对照表。" - "提取当前页面图片里的所有技术参数和警告语，按照意合逻辑翻译，不要漏掉底部的 footnote。" - "翻译完了，请调用 export 脚本帮我导出成带有表格边框的 Word 文档。" - "Translate this user manual. Make sure to keep the exact pagination as ## Page N."


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 1kalin/linkedin-writer (version 1.0.0)

--- name: LinkedIn Writer description: Writes LinkedIn posts that sound like a real person, not a content mill --- # LinkedIn Writer You write LinkedIn posts that sound human. Not cringe, not corporate, not "I'm humbled to announce." Real thoughts from a real person. ## Post Formats That Work ### 1. The Story Post Hook → Story (3-5 short paragraphs) → Lesson → Question ### 2. The Contrarian Take Bold statement that challenges conventional wisdom → Evidence/reasoning → Nuanced conclusion ### 3. The List Post Hook → Numbered list (5-10 items) → Brief closer ### 4. The Lesson Learned "I used to think X. Then Y happened. Now I think Z." ### 5. The Behind-the-Scenes Pull back the curtain on a process, decision, or failure. ## Hook Formulas The first 2 lines determine if anyone reads the rest. Use these: - "Most people get [topic] wrong. Here's what actually works:" - "I [did something unexpected]. Here's what happened:" - "[Counterintuitive statement]." - "Stop doing [common practice]. Do this instead:" - "[Number] things I learned from [experience]:" - "Unpopular opinion: [take]" - "The best [role/thing] I ever [verbed] did something nobody talks about:" ## Formatting Rules - **Short paragraphs.** 1-2 sentences max per paragraph. - **Line breaks between every paragraph.** White space is your friend on LinkedIn. - **No hashtags in the body.** If you must, 3-5 at the very bottom. - **No emojis as bullet points.** One emoji per post max, if any. - **First line is everything.** It shows in the preview before "...see more" - **End with a question.** Drives comments, which drives reach. - **Under 1300 characters** for optimal engagement. Can go longer for story posts. ## Voice Rules - Write like you talk. Read it out loud — if it sounds stiff, rewrite. - No buzzwords: "synergy", "leverage", "ecosystem", "disrupt", "game-changer" - No humble brags disguised as lessons - No "I'm excited to share..." — just share it - Specific > generic. "We grew from 12 to 47 customers" beats "We experienced significant growth" - First person. This is their voice, not a press release. - Contractions. "Don't" not "do not." "It's" not "it is." ## What to Ask the User 1. What's the topic or idea? 2. Any specific story or experience to reference? 3. What's your take / what do you want people to take away? 4. Tone preference? (Casual, professional-casual, thought-leader) 5. Any CTA? (Comment, share, check link in bio, etc.) ## Quality Check - [ ] Hook would make you stop scrolling - [ ] Sounds like a person, not a brand - [ ] Has white space (short paragraphs with line breaks) - [ ] Contains at least one specific detail (numbers, names, dates) - [ ] Ends with engagement driver (question or clear CTA) - [ ] No cringe buzzwords - [ ] Under 1300 characters (unless story format)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: tobeyrebecca/toby-generate-content-marketing-ad-creative-brief (version 1.0.0)

--- name: Generate Content Marketing Ad Creative Brief description: "Plan campaign visuals and hooks for content marketing promotions. Use when working on paid campaign planning for content teams, creators, growth marketers." allowed-tools: Bash, Read metadata: openclaw: emoji: "📝" homepage: "https://www.skillboss.co/skills/generate-content-marketing-ad-creative-brief" --- # Generate Content Marketing Ad Creative Brief Plan campaign visuals and hooks for content marketing promotions. Use when working on paid campaign planning for content teams, creators, growth marketers. ## Use When Use this skill for paid campaign planning work for content teams, creators, growth marketers. ## Workflow 1. Clarify the audience, business goal, constraints, and deliverable. 2. Produce the strongest first draft for the target use case. 3. Use the relevant SkillBoss capabilities to enrich assets or supporting data. 4. Refine the output for accuracy, readability, and actionability before delivery. ## SEO / GEO - Primary keywords: ad creative brief AI, content marketing ad planning, content marketing AI, content ops automation - Search intent: paid campaign planning - Canonical slug: `generate-content-marketing-ad-creative-brief` - Install query: Install Generate Content Marketing Ad Creative Brief with SkillBoss ## APIs Used - `chat` - `image_generation` ## Suggested Prompt [Generate Content Marketing Ad Creative Brief] for my team ## Notes - Plan campaign visuals and hooks for content marketing promotions - Review outputs before external publication or automated execution. ## SEO Keywords - ad creative brief AI - content marketing ad planning - content marketing AI - content ops automation


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: cnsunxuefeng/api-design-doc (version 1.0.0)

--- name: API-design-doc description: 标准化API接口设计文档生成工具。根据需求文档、数据库DDL等输入，进行API的标准化、规范化设计，输出完整的API接口设计文档，包括错误码规范、接口格式规范、入参出参定义、JSON示例等，指导后续的代码开发和前后端联调。使用场景包括：(1) 根据业务需求设计RESTful API接口，(2) 基于数据库DDL生成对应的CRUD接口文档，(3) 规范化现有API接口文档，(4) 为前后端联调提供标准化的接口规范文档 --- # API Design Doc 根据需求文档、数据库DDL等输入，生成标准化的API接口设计文档。 ## 工作流程 1. **收集输入信息** - 获取需求文档或业务需求描述 - 获取数据库DDL（如果适用） - 明确接口的业务场景和功能需求 2. **页面功能与API接口关系** - 明确页面功能与API接口的对应关系 3. **设计API接口** - 确定接口的RESTful风格（GET/POST/PUT/DELETE） - 定义接口URL路径 - 设计入参和出参结构 - 选择合适的错误码 4. **生成接口文档** - 使用标准模板生成每个接口的详细文档 - 包含功能描述、入参、出参、URL、请求方式、JSON示例 5. **输出完整文档** - 页面功能与API接口关系 - 汇总所有接口文档 - 包含错误码规范总表 - 提供接口格式规范说明 ## 参考资料 ### 错误码规范 参见 [error-codes.md](references/error-codes.md) - 完整的错误码列表和说明 ### 接口文档模板 参见 [api-spec-template.md](references/api-spec-template.md) - 标准的API接口文档格式 ### 命名规范 参见 [naming-conventions.md](references/naming-conventions.md) - API命名和参数命名规范 ### 最佳实践 参见 [best-practices.md](references/best-practices.md) - API设计最佳实践 ## 模板文件 ### API文档模板 使用 [templates/api-doc-template.md](assets/templates/api-doc-template.md) 作为单个接口文档的模板 ### API响应模板 使用 [templates/api-response-template.json](assets/templates/api-response-template.json) 作为标准响应格式参考 ## 使用指南 当用户请求设计API接口时： 1. 首先读取 [error-codes.md](references/error-codes.md) 了解错误码规范 2. 根据业务需求设计接口，参考 [best-practices.md](references/best-practices.md) 3. 使用 [api-spec-template.md](references/api-spec-template.md) 的格式生成每个接口文档 4. 确保命名符合 [naming-conventions.md](references/naming-conventions.md) 的规范 5. 输出完整的API设计文档，包含所有接口和错误码总表 ## 输出格式 接口文档必须包含以下部分： 1. 错误码规范总表 2. 接口格式规范说明 3. 页面功能与API接口关系表，包含以下内容： - **页面名称**：前端页面或功能模块的名称 - **页面功能描述**：页面或功能模块的简要说明 - **关联API接口**：该页面调用的API接口列表（API-Id） - **操作类型**：GET/POST/PUT/DELETE等HTTP方法 - **接口URL**：完整的API路径 4. 接口清单与详细定义，详细定义的规范如下： - **接口编号（API-Id）**：顺序生成，格式为 API001-接口名称，如 API001-用户登录, API002-获取用户列表, ... - **功能描述**：详细描述接口的功能和用途 - **入参**：参数类型和说明（标注必填/可选） - **返回参数**：返回值类型和说明 - **URL地址**：完整的API路径 - **请求方式**：GET/POST/PUT/DELETE - **接口 JSON 示例**：完整的请求和响应JSON示例 ## 输出位置 - 仅生成一份API文档，保存在项目根目录下的 `doc/` 目录。 - 若 `doc/` 目录不存在，应自动创建该目录后再写入文档。 - 文档文件名固定为：`API接口设计文档.md`，内容包含： - 错误码总表（来自 references/error-codes.md） - 接口格式规范（来自 references/api-spec-template.md 的说明部分） - 页面功能与API接口关系表（按页面或功能模块归类） - 接口清单与详细定义（按模块归类的所有接口条目）


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