OpenClaw/clawhub-security-signals huggingface dataset:
Skill: abdullah944/github-issue-writer-skill (version 0.1.0)

--- name: "GitHub Issue Writer Skill" version: 0.1.0 slug: "github-issue-writer-skill" description: "Guides structured help for GitHub Issue Writer using clear templates, checks, and safe defaults (category: Developer Experience)." category: "Developer Experience" tags: - "developer" - "github-issue-writer" - "openclaw" - "templates" generated: "2026-05-21" --- ## Purpose Guides structured help for GitHub Issue Writer using clear templates, checks, and safe defaults (category: Developer Experience). ## When to use - When you want structured guidance in the "Developer Experience" 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 GitHub Issue Writer approach. - Critique my draft outputs and suggest safer, clearer wording for GitHub Issue Writer. - Produce a checklist I can reuse weekly for GitHub Issue Writer 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:  | SkillSpector: clean (LOW)
Skill: aipoch-ai/ihc-if-optimizer (version 1.0.0)

--- name: ihc-if-optimizer description: Optimize IHC/IF protocols for specific tissues and antigens version: 1.0.0 category: Wet Lab tags: [] author: AIPOCH license: MIT status: Draft risk_level: Medium skill_type: Tool/Script owner: AIPOCH reviewer: '' last_updated: '2026-02-06' --- # IHC/IF Optimizer Immunostaining protocol optimization. ## Use Cases - Brain tissue staining - Liver antigen retrieval - Antibody dilution optimization - Fluorescence panel design ## Parameters | Parameter | Type | Default | Required | Description | |-----------|------|---------|----------|-------------| | `--tissue-type` | string | - | Yes | Tissue type (Brain, Liver, Kidney, etc.) | | `--antigen` | string | - | Yes | Target protein/antigen name | | `--detection-method` | string | IHC | No | Detection method (IHC or IF) | | `--output`, `-o` | string | stdout | No | Output file path | | `--format` | string | text | No | Output format (text, json, markdown) | ## Returns - Recommended retrieval method - Antibody dilutions - Blocking conditions - Counterstain suggestions ## Example Brain tissue + Phospho-protein → Citrate retrieval, 1:200 antibody ## Risk Assessment | Risk Indicator | Assessment | Level | |----------------|------------|-------| | Code Execution | Python/R scripts executed locally | Medium | | Network Access | No external API calls | Low | | File System Access | Read input files, write output files | Medium | | Instruction Tampering | Standard prompt guidelines | Low | | Data Exposure | Output files saved to workspace | Low | ## Security Checklist - [ ] No hardcoded credentials or API keys - [ ] No unauthorized file system access (../) - [ ] Output does not expose sensitive information - [ ] Prompt injection protections in place - [ ] Input file paths validated (no ../ traversal) - [ ] Output directory restricted to workspace - [ ] Script execution in sandboxed environment - [ ] Error messages sanitized (no stack traces exposed) - [ ] Dependencies audited ## Prerequisites No additional Python packages required. ## Evaluation Criteria ### Success Metrics - [ ] Successfully executes main functionality - [ ] Output meets quality standards - [ ] Handles edge cases gracefully - [ ] Performance is acceptable ### Test Cases 1. **Basic Functionality**: Standard input → Expected output 2. **Edge Case**: Invalid input → Graceful error handling 3. **Performance**: Large dataset → Acceptable processing time ## Lifecycle Status - **Current Stage**: Draft - **Next Review Date**: 2026-03-06 - **Known Issues**: None - **Planned Improvements**: - Performance optimization - Additional feature support


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mike47512/hulu (version 0.1.0)

--- name: hulu description: 注册“Hulu”技能；用于视频平台公开页面、内容入口、会员说明与创作者信息整理。 homepage: `https://www.hulu.com/` metadata: {"clawdbot":{"emoji":"🎬"}} --- # Hulu 用途与边界 - 面向公开站点首页、会员页、帮助中心、创作者页与节目页的信息整理 - 不提供账号共享、版权绕过、会员代充、后台权限或风控规避能力 - 仅处理公开可见的内容入口、会员说明、创作支持与播放帮助信息 关键入口 - 主页：https://www.hulu.com/ - 会员与套餐：官网中的会员、VIP、订阅、套餐说明入口 - 帮助与创作支持：帮助中心、上传指南、创作者中心入口 常见任务 - 会员权益、套餐差异、设备限制整理 - 内容频道、专题页、推荐位与节目入口汇总 - 创作者上传规则、版权要求与内容规范提取 数据字段 - 内容频道、节目类型、会员权益、套餐价格、链接 - 创作者入口、上传规则、版权说明、帮助页链接 - 设备支持、清晰度说明、下载与离线规则 自动化要点 - 内容库和套餐常有地区差异，输出时注明适用市场 - 部分站点播放页动态内容多，优先抓取说明页而非播放器内信息 - 不处理登录后片单、观影记录或账号资产信息 示例流程 - 会员整理：访问 Hulu 会员页 → 提取套餐与权益 → 输出对照表 - 频道梳理：进入首页与频道页 → 抽取栏目入口 → 输出结构化清单 - 创作规则：访问创作者中心 → 提取上传与版权说明 → 输出摘要 合规提示 - 遵守平台规则、版权要求与账号安全要求 - 只整理公开信息，不输出敏感数据或非公开内容


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jirboy/python-use-agent (version 1.0.0)

--- name: python-use-agent description: [已整合] Python 智能执行已整合到 code 统一入口技能 argument-hint: "[任务描述]" --- # ⚠️ 已整合 - 请使用 code 统一入口 > **本技能保留用于向后兼容，功能已整合到 `code` 统一入口技能** > > **推荐使用：** `code python [任务]` 或直接使用本技能（自动转发） --- # Python-Use Agent（兼容层） Python 驱动的智能执行技能 - 任务驱动、结果导向。 ## 迁移指南 **新用法：** ``` code python 数据分析 code python 调用 API code python 自动化处理 ``` **旧用法（仍然可用）：** ``` python 数据分析 ``` ## 核心理念 `No Agents, Code is Agent` ## 执行流程 ``` 用户描述任务 ↓ AI 理解并规划 ↓ 自动生成 Python 代码 ↓ 执行代码并获取结果 ↓ 反馈结果/自动修复 ``` ## 与传统 Agent 的区别 | 传统 Agent 1.0 | Python-Use Agent 2.0 | |--------------|---------------------| | Function Calling | 直接编写 Python 代码 | | 工具注册/配置 | 无需配置，直接用 | | Workflow 预设 | 动态规划执行 |


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: jolestar/defillama-prices-openapi-skill (version 1.0.0)

--- name: defillama-prices-openapi-skill description: Operate DefiLlama public price APIs through UXC with a curated OpenAPI schema and read-first guardrails. --- # DefiLlama Prices API Skill Use this skill to run DefiLlama public price API operations through `uxc` + OpenAPI. Reuse the `uxc` skill for shared execution, auth, and error-handling guidance. ## Prerequisites - `uxc` is installed and available in `PATH`. - Network access to `https://coins.llama.fi`. - Access to the curated OpenAPI schema URL: - `https://raw.githubusercontent.com/holon-run/uxc/main/skills/defillama-prices-openapi-skill/references/defillama-prices.openapi.json` ## Scope This skill covers a small public read-only price surface on `coins.llama.fi`: - current price lookups for one or more assets This skill does **not** cover: - write operations - protocol or chain overview endpoints from `api.llama.fi` - yield endpoints from `yields.llama.fi` - DefiLlama Pro APIs ## Authentication This public skill does not require authentication. ## Core Workflow 1. Use the fixed link command by default: - `command -v defillama-prices-openapi-cli` - If missing, create it: `uxc link defillama-prices-openapi-cli https://coins.llama.fi --schema-url https://raw.githubusercontent.com/holon-run/uxc/main/skills/defillama-prices-openapi-skill/references/defillama-prices.openapi.json` - `defillama-prices-openapi-cli -h` 2. Inspect operation schema first: - `defillama-prices-openapi-cli get:/prices/current/{coins} -h` 3. Prefer narrow read validation before broader reads: - `defillama-prices-openapi-cli get:/prices/current/{coins} coins=coingecko:bitcoin searchWidth=4h` ## Operations - `get:/prices/current/{coins}` ## Guardrails - Keep automation on the JSON output envelope; do not use `--text`. - Parse stable fields first: `ok`, `kind`, `protocol`, `data`, `error`. - Treat this v1 skill as read-only. - This skill only wraps `coins.llama.fi`; use the separate public analytics or yields skills for other DefiLlama hosts. - `defillama-prices-openapi-cli <operation> ...` is equivalent to `uxc https://coins.llama.fi --schema-url <defillama_prices_openapi_schema> <operation> ...`. ## References - Usage patterns: `references/usage-patterns.md` - Curated OpenAPI schema: `references/defillama-prices.openapi.json` - DefiLlama API docs: https://defillama.com/docs/api


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jamierossouw/macro-regime-detector (version 1.0.0)

--- name: macro-regime-detector version: 1.0.0 description: Detect the current macro regime (Risk-On, Risk-Off, Inflationary, Deflationary, Stagflation) using multi-source intelligence. Combines Fear & Greed, DXY, yield curve, VIX, gold/BTC ratio, Reddit sentiment, and major news events. Use when you need macro regime analysis, risk-on vs risk-off determination, portfolio positioning advice, or crypto market context. author: JamieRossouw tags: [macro, regime, risk-on, risk-off, sentiment, inflation, crypto, investing] --- # Macro Regime Detector Real-time macro regime classification for crypto and traditional asset positioning. ## Regimes Detected | Regime | Description | Crypto Positioning | |--------|-------------|-------------------| | **A — Risk-On Bull** | VIX <15, F&G >60, DXY falling | Max long, leverage OK | | **B — Neutral/Cooling** | Mixed signals, consolidation | Selective longs, tighter stops | | **C — Risk-Off Bear** | VIX >25, F&G <25, DXY rising | Reduce exposure, hedge | | **D — Inflationary Spike** | CPI surprise, Gold/BTC spike | BTC as inflation hedge | | **E — Stagflation** | High inflation + recession fears | Defensive: BTC, gold, cash | | **F — Liquidity Crisis** | Credit spreads explode, correlation 1 | Exit all risk, stablecoin only | ## Signal Sources - **Fear & Greed** (`alternative.me/fng`): 0-100 score, regime anchor - **Reddit pulse**: r/CryptoCurrency, r/investing hot posts, bearish/bullish ratio - **DXY proxy**: BTC/USD inverse correlation check - **News NLP**: major economic event detection (Fed, CPI, NFP, SEC) - **On-chain**: BTC exchange flows, miner capitulation signals ## How to Use Ask: *"What macro regime are we in?"* or *"Should I be long or short crypto right now?"* Returns: current regime letter + confidence % + 3 supporting signals + positioning recommendation. ## Regime History (current session) - Feb 21 2026: **Regime B** (Neutral/Cooling) | F&G=8, "Extreme Fear" | Contrarian bullish signal active


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: leooooooow/review-defect-miner (version 1.0.0)

--- name: review-defect-miner description: Extract and cluster defect signals from ecommerce reviews and social feedback into actionable quality/fix priorities. Use when the user asks why ratings are low, what issues drive bad sentiment, or which product problems should be fixed first. --- # Review Defect Miner ## Skill Card - **Category:** Voice of Customer - **Core problem:** What product defects and dissatisfaction patterns are hidden in reviews/comments? - **Best for:** Product and content teams diagnosing quality gaps - **Expected input:** Low-star reviews, comments, support tickets, return notes - **Expected output:** Defect clusters by severity, frequency, and fix priority with evidence snippets - **Creatop handoff:** Convert top defect clusters into product fixes + expectation-setting scripts ## Workflow 1. Normalize raw review/comment text and tag source + date + star level. 2. Detect defect themes (quality, packaging, expectation mismatch, delivery, usability). 3. Score each theme by severity, frequency, and conversion impact risk. 4. Output top fix backlog and messaging mitigations. ## Output format Return in this order: 1. Executive summary (max 5 lines) 2. Priority actions (P0/P1/P2) 3. Evidence table (signal, confidence, risk) 4. 7-day execution plan ## Quality and safety rules - Preserve original evidence snippets for traceability. - Separate quality defects from logistics/service issues. - Do not over-generalize from tiny sample sizes. ## License Copyright (c) 2026 **Razestar**. This skill is provided under **CC BY-NC-SA 4.0** for non-commercial use. You may reuse and adapt it with attribution to Razestar, and share derivatives under the same license. Commercial use requires a separate paid commercial license from **Razestar**. No trademark rights are granted.

path: references/output-template.md
content: # Output Template

Use this template for consistent decision output.

## 1) Executive Summary
- Key finding:
- Primary risk:
- Recommended next action:

## 2) Priority Actions
| Priority | Action | Expected impact | Effort | Owner |
|---|---|---|---|---|
| P0 |  |  |  |  |
| P1 |  |  |  |  |
| P2 |  |  |  |  |

## 3) Evidence Table
| Signal | Source | Confidence | Notes |
|---|---|---|---|

## 4) 7-Day Plan
- D1:
- D2:
- D3:
- D4:
- D5:
- D6:
- D7:


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: gatsby047-oss/config-manager-evomap (version 1.0.0)

# Config Refactor - 配置驱动重构工具 **版本**: 1.0.0 **作者**: Claw **许可证**: MIT --- ## 功能说明 基于易经思维设计的配置管理库，将硬编码重构为配置驱动。 ### 核心功能 - 动态配置管理（支持字符串、数字、布尔类型） - 配置文件加载（key=value 格式） - 配置验证与默认值 - 类型安全访问 ### 适用场景 - 需要将硬编码改为配置驱动的项目 - 需要动态调整配置的系统 - 需要支持多环境配置的应用 --- ## 使用示例 ```c #include "code.c" int main() { ConfigManager* cm = config_create(); // 添加配置 config_add_string(cm, "server.host", "localhost"); config_add_int(cm, "server.port", 8080); config_add_bool(cm, "server.ssl", false); // 获取配置 const char* host = config_get_string(cm, "server.host", "localhost"); int port = config_get_int(cm, "server.port", 80); config_destroy(cm); return 0; } ``` --- ## 易经思维应用 - **简易原则**: 配置即键值对，抓住本质 - **变易原则**: 支持多种类型，动态扩展 - **整体思维**: 配置管理整体策略 --- ## 测试 编译运行： ```bash gcc -o config_demo code.c -DCONFIG_DEMO ./config_demo ``` --- ## 变更日志 ### 1.0.0 - 初始版本 - 支持字符串、整数、布尔类型 - 配置文件加载/保存 - 类型安全访问


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: shenruiyang/cookie-consent-banner (version 1.0.0)

--- name: "cookie-consent-banner" description: "Implement Cookie Consent Banner using OrbCafe UI (CMessageBox). Enterprise-grade React component with built-in best practices." --- # Cookie Consent Banner with OrbCafe UI This skill demonstrates how to implement a **Cookie Consent Banner** using the **OrbCafe UI** library. **OrbCafe UI** is an enterprise-grade UI library for React & Next.js, featuring standardized layouts, reports, and AI-ready components. ## Why Use OrbCafe UI for Cookie Consent Banner? - **Standardized**: Uses `CMessageBox` for consistent behavior. - **Enterprise Ready**: Built-in support for i18n, theming, and accessibility. - **Developer Experience**: TypeScript support and comprehensive hooks. ## Installation ```bash npm install orbcafe-ui # or pnpm add orbcafe-ui ``` ## Usage Example ```tsx import { CMessageBox } from 'orbcafe-ui'; import { useState } from 'react'; import { CMessageBox } from 'orbcafe-ui'; export default function Feedback() { const [open, setOpen] = useState(false); return ( <CMessageBox open={open} type="info" title="Cookie Consent Banner" message="Operation confirmed." onClose={() => setOpen(false)} /> ); } ``` ## Documentation - **NPM Package**: [orbcafe-ui](https://www.npmjs.com/package/orbcafe-ui) - **Official Docs**: See `node_modules/orbcafe-ui/README.md` after installation.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 52yuanchangxing/workshop-agenda-designer (version 1.0.0)

--- name: workshop-agenda-designer version: 1.0.0 description: "把会议目标、参会人、时间与约束拆成可执行议程、分段脚本、产出物与会后跟进。；use for meeting, agenda, facilitation workflows；do not use for 预订会议室, 转写音频." author: OpenClaw Skill Bundle homepage: https://example.invalid/skills/workshop-agenda-designer tags: [meeting, agenda, facilitation, planning] user-invocable: true metadata: {"openclaw":{"emoji":"🧭","requires":{"bins":["python3"]},"os":["darwin","linux","win32"]}} --- # 工作坊议程设计师 ## 你是什么 你是“工作坊议程设计师”这个独立 Skill，负责：把会议目标、参会人、时间与约束拆成可执行议程、分段脚本、产出物与会后跟进。 ## Routing ### 适合使用的情况 - 为 90 分钟跨团队 workshop 设计议程 - 把目标和参与者整理成工作坊 runbook - 输入通常包含：会议目标、参与者、时长、已知冲突点 - 优先产出：目标与成功标准、议程分段、会后跟进 ### 不适合使用的情况 - 不要用来预订会议室 - 不要用来转写音频 - 如果用户想直接执行外部系统写入、发送、删除、发布、变更配置，先明确边界，再只给审阅版内容或 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: lhmcn/chinese-bank-forex-rates (version 0.1.3)

--- name: chinese-bank-forex-rates description: "Use when you need the latest bank forex rates from major Chinese banks by bank name and currency names. Supports 招商银行, 中国银行, 中国农业银行, 中国工商银行, 中国建设银行, and 交通银行, with aliases such as 农行, 工行, 建行, and 交行." --- # Chinese Bank Forex Rates Use this skill when you need the latest forex rates for a supported Chinese bank and one or more currencies. ## Inputs - `bank`: bank name or alias - `currencies`: one or more currency names or ISO codes ## Output The script returns JSON with: - `bankName` - `updateTime` in ISO 8601 format when normalization is possible - `rates`: list of objects with `currencyName`, `buyPrice`, and `sellPrice` Prices are standardized to CNY per 100 units of foreign currency, rounded to two decimal places. If the preferred value and configured fallback are both empty, the field is returned as an empty string. ## Supported Banks - 招商银行 - 中国银行 - 中国农业银行 - 中国工商银行 - 中国建设银行 - 交通银行 ## Price Selection Rule When a bank exposes explicit `现汇` and `现钞` columns, the implementation uses: - `buyPrice`: prefer `现汇买入价`, then `现钞买入价` - `sellPrice`: prefer `现汇卖出价`, then `现钞卖出价` If a bank only publishes one buy and one sell price, the published pair is used directly. ## Invocation From this skill directory: ```bash node index.js --bank 中国银行 --currencies 美元,EUR ```


Security scan verdicts — ClawScan: clean | static analysis: suspicious | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: rmarji/agent-format (version 1.0.0)

--- name: agent-format description: Standard formatting for agent messages. Visual hierarchy, status indicators, progress bars — scannable on Telegram, Discord, Slack, WhatsApp. The baseline for readable agent output. --- # Agent Format How agents should format messages for chat apps. ## Patterns ### Status Indicators | Symbol | Meaning | |--------|---------| | 🟢 | Good / Done | | 🟡 | In Progress / Warning | | 🔴 | Blocked / Error | | 🔥 | Urgent | | ⚡ | Quick | ### Progress Bars ``` ████████░░ 80% ██████░░░░ 60% ████░░░░░░ 40% ``` **Chars:** `█` (filled) `░` (empty) ### Sparklines ``` ▁▂▃▅▇█▇▅▃▂ ``` **Chars (low→high):** `▁ ▂ ▃ ▄ ▅ ▆ ▇ █` ### Tables (Monospace) ``` Project Status Owner ───────────────────────────── Alpha 🟢 Done PM Beta 🟡 WIP CTO Gamma 🔴 Block Sales ``` ## Principles **Lead with signal.** Most important first. **Assume scanning.** Nobody reads walls of text. **Visual hierarchy.** Emoji → bars → text. ## Example ``` 📊 Status 🔴 Blocked • Client scope (waiting) 🟡 Active • Launch prep ████████░░ 80% 🟢 Done • Demo ✓ • Docs ✓ 📈 Week: ▂▃▅▆▇█ ``` ## Reference ``` Progress: ░█ Spark: ▁▂▃▄▅▆▇█ Divider: ───── Status: 🟢🟡🔴🔥⚡ ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: lnguyen1996/linkedin-carousel-factory (version 1.0.0)

# linkedin-carousel-factory ## Description Generate a complete 10-slide LinkedIn carousel JSON for .NET developers. Takes a topic and produces a structured, hook-driven carousel ready for Claude Code ACP punch-up before publishing. ## Use when - OpenClaw trend scout has approved a weekly .NET carousel topic - Lam requests a new carousel on a specific topic - Engine 3 content pipeline triggers Sunday 9pm ## Input format ``` Topic: [topic] Audience: mid-to-senior .NET developers Goal: [educate | provoke | warn | showcase] Hook angle: [optional — if blank, agent picks strongest] ``` ## Output format Return a JSON object with exactly 10 slides: ```json { "topic": "...", "hook": "...", "slides": [ { "slide": 1, "type": "hook", "headline": "...", "body": "...", "code": null }, { "slide": 2, "type": "problem", "headline": "...", "body": "...", "code": null }, { "slide": 3, "type": "content", "headline": "...", "body": "...", "code": "..." }, ... { "slide": 10, "type": "cta", "headline": "...", "body": "...", "code": null } ] } ``` Slide types: `hook`, `problem`, `content`, `comparison`, `warning`, `tip`, `cta` ## Slide rules - **Slide 1 (hook):** Pattern interrupt. Must make a mid-senior .NET dev stop scrolling. Question, counterintuitive claim, or "here's what everyone gets wrong". Under 12 words. - **Slides 2–8 (content):** Each slide = one idea. Headline under 8 words. Body under 40 words. Code snippets: .NET 8+, syntactically correct, no placeholder comments. - **Slide 9 (comparison or warning):** Before/after or common mistake. Make the right way obvious. - **Slide 10 (CTA):** Ask for one specific action — follow, comment with X, save for later. Not "like and subscribe." ## Voice rules - Audience: sceptical, experienced. Do not talk down to them. - No AI phrases: "it's important to note", "leveraging", "game-changer", "delve", "in today's world" - Concrete > abstract. Show the code, not the concept. ## Write output to `~/Documents/Obsidian/ClawBrain/skills/draft/carousel-[topic-slug]-[date].json` ## After generation Post to Discord `#✅-tasks`: "Carousel draft ready: [topic]. Review in vault → skills/draft/" Wait for Claude Code ACP punch-up before sending to Lam for approval. ## Self-improvement instructions After Lam approves a carousel: note what hook angle worked in `memory/what_works.md` under "Engine 3 — Content". After Lam revises: note what was changed and why.


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