OpenClaw/clawhub-security-signals huggingface dataset:
Skill: clawkk/compensation (version 1.0.0)

--- name: compensation description: "Offers, compensation framing, and negotiation planning. Use when evaluating offers or raises." --- # Compensation Structured guidance for **offers, pay, and negotiation** (not legal or tax advice): confirm triggers, propose the stages below, and adapt if the user wants a lighter pass. ## When to Offer This Workflow **Trigger conditions:** - User mentions **negotiation**, **offers**, **raises**, **compensation**, or closely related work - They want a structured workflow rather than ad-hoc tips - They are preparing a review, rollout, or stakeholder communication **Initial offer:** Explain the four stages briefly and ask whether to follow this workflow or work freeform. If they decline, continue in their preferred style. ## Workflow Stages ### Stage 1: Clarify context & goals Anchor on **market context and priorities**. Ask what success looks like, constraints, and what must not break. Capture unknowns early. ### Stage 2: Design or plan the approach Translate goals into a concrete plan around **total comp components**. Compare alternatives and explicit trade-offs; avoid implicit assumptions. ### Stage 3: Implement, validate, and harden Execute with verification loops tied to **negotiation script and BATNA**. Prefer small steps, measurable checks, and rollback points where risk is high. ### Stage 4: Operate, communicate, and iterate Close the loop with **written follow-ups**: monitoring, documentation, stakeholder updates, and lessons learned for the next cycle. ## Checklist Before Completion - Goals and constraints are explicit for **compensation** discussions - Risks and trade-offs are stated, not hand-waved - Verification steps match the change’s impact (tests, canary, peer review) - Operational follow-through is covered (monitoring, docs, owners) ## Tips for Effective Guidance - Be procedural: stage-by-stage, with clear exit criteria - Ask for missing context (environment, scale, deadlines) before prescribing - Prefer checklists and concrete examples over generic platitudes - If the user declines the workflow, switch to freeform help without lecturing ## Handling Deviations - If the user wants to skip a stage: confirm and continue with what they need. - If context is missing: ask targeted questions before strong recommendations. - Prefer concrete examples, trade-offs, and verification steps over generic advice. ## Quality Bar - Each recommendation should be **actionable** (what to do next). - Call out **failure modes** relevant to compensation talks (relationship risk, miscommunication, or unrealistic asks). - Keep tone direct and respectful of the user’s time.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: gekacross/personal-plans (version 1.0.0)

--- name: personal-plans description: Acts as the user's personal planning assistant in the Plans topic. Tracks tasks, to-do lists, reminders, and daily/weekly plans. Use when in Personal chat Plans topic, or when user mentions task, plan, todo, reminder, schedule, deadline, do, finish, complete, or planning. --- # Personal Plans (планировщик) Роль: **твой персональный планировщик**. Трекает задачи, планы, напоминания и помогает всё успевать. ## Перед ответом 1. **Прочитай** `/data/.openclaw/workspace/knowledge/personal/plans.md` — там задачи, планы, дедлайны. 2. **Учитывай историю чата**. 3. Если пользователь добавил/выполнил задачу или план — обнови `/data/.openclaw/workspace/knowledge/personal/plans.md`. ## Что умеет - **Задачи:** добавить, отметить выполненной, удалить. - **Планы:** план на день, неделю, месяц. - **Дедлайны:** трекать задачи с датой выполнения. - **Приоритеты:** расставить приоритеты (высокий/средний/низкий). - **Напоминания:** записать что нужно сделать к определённой дате. - **Обзор:** показать что сделано, что осталось, что просрочено. - **Разбивка:** большую цель разбить на маленькие шаги. ## Правила - Логировать просто: «нужно купить продукты завтра» → записать задачу с датой. - Формат в `/data/.openclaw/workspace/knowledge/personal/plans.md`: ```markdown ## Задачи | Задача | Приоритет | Дедлайн | Статус | |--------|-----------|---------|--------| | Купить продукты | средний | 2026-02-19 | ✅ | | Позвонить врачу | высокий | 2026-02-20 | ⏳ | ## Планы ### На эту неделю - ... ### На этот месяц - ... ## Выполнено - ... ``` - Тон: чёткий, мотивирующий. Без лишних слов. ## Файлы - **Память:** `/data/.openclaw/workspace/knowledge/personal/plans.md` — читать в начале, обновлять.


Security scan verdicts — ClawScan: clean | static analysis:  | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: clawbob/calendar-crab (version 1.0.0)

--- name: calendar-crab description: Google Calendar CLI — list, create, move, and delete events. Zero dependencies, just Node.js + Google OAuth. --- # Calendar Crab Google Calendar management via a single Node.js script. No npm install needed. ## Prerequisites - Node.js 18+ - Google Cloud project with Calendar API enabled - OAuth credentials + refresh token saved to `~/.openclaw/secrets/` (see Setup below) ## Commands ### List upcoming events ```bash node calendar-crab.js list --days=7 --max=20 ``` ### Create an event ```bash node calendar-crab.js create \ --title="Team Sync" \ --date=2026-03-20 \ --time=10:00 \ --duration=30 \ --location="Zoom" \ --attendees="[REDACTED_SECRET],[REDACTED_SECRET]" \ --description="Weekly sync" \ --tz="America/Los_Angeles" ``` ### Move an event ```bash # By date + time node calendar-crab.js move --date=2026-03-20 --from=10:00 --to=14:00 # By event ID node calendar-crab.js move --id="EVENT_ID" --to="2026-03-20T14:00:00-07:00" ``` ### Delete an event ```bash node calendar-crab.js delete --id="EVENT_ID" node calendar-crab.js delete --date=2026-03-20 --time=10:00 ``` ## Configuration | Env var | Default | Description | |---------|---------|-------------| | `CALENDAR_CRAB_SECRETS` | `~/.openclaw/secrets` | Directory containing OAuth + token JSON files | | `CALENDAR_CRAB_TZ` | System local | Default timezone for events | | `CALENDAR_CRAB_CALENDAR` | `primary` | Google Calendar ID | Timezone can also be set per-command with `--tz=America/Los_Angeles`. ## Execution rules 1. Always `list` first to verify the target event exists and is unique. 2. `move` and `delete` auto-notify all attendees (`sendUpdates=all`). 3. On failure, the raw Google API error is returned for debugging. ## Setup 1. Go to [Google Cloud Console](https://console.cloud.google.com/) and create a project. 2. Enable the **Google Calendar API**. 3. Create OAuth 2.0 credentials (Desktop app type). 4. Save the credentials as `~/.openclaw/secrets/google-calendar-oauth.json`: ```json { "client_id": "YOUR_CLIENT_ID", "client_secret": "YOUR_CLIENT_SECRET" } ``` 5. Obtain a refresh token via the OAuth flow and save as `~/.openclaw/secrets/google-calendar-token.json`: ```json { "refresh_token": "YOUR_REFRESH_TOKEN", "access_token": "", "expires_in": 0, "obtained_at": "" } ``` The script auto-refreshes the access token using the refresh token.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: sky-lv/deployment-automation (version 1.0.0)

--- name: deployment-automation slug: deployment-automation version: 1.0.0 description: "Automated deployment pipeline for AI agents. Build, test, and deploy applications with zero-downtime. Triggers: deployment, CI/CD, release automation, deploy pipeline, continuous deployment." author: SKY-lv license: MIT-0 tags: [automation, devops, deployment] keywords: [deployment, CI/CD, release automation, deploy pipeline, continuous deployment, zero-downtime, blue-green, canary, rollback] triggers: deployment-automation --- # Deployment Automation Automated deployment pipeline for AI agents. Build, test, and deploy applications with zero-downtime and instant rollback. ## Overview A complete deployment automation system that helps agents manage the full release lifecycle: build, test, deploy, monitor, and rollback. Supports multiple deployment strategies including blue-green, canary, and rolling updates. ## Capabilities ### 1. Pipeline Definition ```bash node deploy.js pipeline create --name production --stages build,test,stage,deploy node deploy.js pipeline run --name production --ref main node deploy.js pipeline status --name production ``` Define and execute multi-stage deployment pipelines with custom stages. ### 2. Deployment Strategies ```bash node deploy.js deploy --strategy blue-green --service api node deploy.js deploy --strategy canary --service web --canary-percent 10 node deploy.js deploy --strategy rolling --service worker --batch-size 3 ``` Choose from blue-green, canary, or rolling deployment strategies. ### 3. Health Checks ```bash node deploy.js health-check --service api --endpoint /health --timeout 30s node deploy.js health-check --custom .healthcheck.json ``` Automated health checks before and after deployment to ensure service stability. ### 4. Rollback ```bash node deploy.js rollback --service api --to previous node deploy.js rollback --service web --to-version v2.3.1 node deploy.js rollback --auto-on-failure --max-retries 3 ``` Instant rollback to previous versions on deployment failure. ### 5. Multi-Environment ```bash node deploy.js promote --from staging --to production --approve node deploy.js diff --env staging vs production ``` Promote builds across environments with approval gates and configuration diffing. ## Configuration ```json { "pipeline": { "environments": ["dev", "staging", "production"], "strategy": "canary", "canaryPercent": 10, "healthCheck": { "endpoint": "/health", "timeout": "30s", "retries": 3 }, "rollback": { "autoOnFailure": true, "maxRetries": 3 }, "notifications": { "onStart": ["slack"], "onSuccess": ["slack", "email"], "onFailure": ["slack", "pagerduty"] } } } ``` ## Use Cases - Application Release: Automate full release workflow from build to deploy - Microservices: Deploy individual services independently - Infrastructure: Deploy infrastructure changes alongside application code - Agent Deployment: Deploy AI agent updates with zero downtime - Hotfix: Emergency deployments with automated health verification


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: wanng-ide/folder-tree-generator (version 1.0.0)

--- name: folder-tree-generator description: Generates an ASCII tree or JSON representation of a directory structure. Use when you need to visualize file hierarchies, document folder contents, or debug directory layouts. --- # Folder Tree Generator A utility skill to visualize directory structures in ASCII tree format or JSON. ## Usage ```bash # Generate ASCII tree for current directory node skills/folder-tree-generator/index.js # Generate ASCII tree for specific directory node skills/folder-tree-generator/index.js /path/to/dir # Generate JSON output node skills/folder-tree-generator/index.js --json # Limit depth node skills/folder-tree-generator/index.js --depth 2 ``` ## Options - `--json`: Output as JSON. - `--depth <n>`: Limit recursion depth. - `[dir]`: Directory to scan (default: `.`). ## Examples **ASCII Output:** ``` . ├── file1.txt └── dir1 ├── file2.txt └── file3.txt ``` **JSON Output:** ```json { "name": ".", "type": "directory", "children": [ { "name": "file1.txt", "type": "file" }, { "name": "dir1", "type": "directory", "children": [...] } ] } ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mzfshark/anti-hype-filter (version 1.0.0)

--- name: anti-hype-filter description: Detect hype cycles and neutralize emotional triggers by rewriting claims into verifiable structures and explicit risk/uncertainty. metadata: author: AgentSmith version: 2.0.0 owner: Agent Smith Agent category: filtering --- # SKILL: anti-hype-filter ## Purpose Detect and neutralize hype cycles before they distort system integrity by stripping emotional triggers and replacing them with structural analysis. ## When to Use - "guaranteed", "moon", "100x", "alpha" style language - Urgency without substance ("now or never") - Social proof without evidence - Claims that minimize risk or constraints ## Inputs - `text` (required): message to evaluate - `context` (optional): - `domain` (token|product|governance|community) - `policy` (required): - `hype_terms` (optional list; if omitted, use the embedded default set in this skill) - `max_response_words` (default 100) ## Steps 1. Extract key claims (1-5). 2. Detect hype triggers: - urgency framing - certainty language - vague upside claims - social proof substitution 3. Classify: - `signal`, `noise`, or `manipulation_risk` 4. Rewrite the message into a verifiable form: - replace certainty with uncertainty - add required missing variables (data window, metrics, constraints) 5. Draft a minimal response that: - does not repeat hype memes verbatim - demands evidence and risk disclosure ## Validation - If classification is `manipulation_risk`, provide at least 1 falsifiable request for evidence. - Do not amplify hype phrases; paraphrase instead. ## Output - `anti_hype_result`: - `classification` ("signal"|"noise"|"manipulation_risk") - `detected_triggers` (list) - `missing_information` (list) - `rewrite` (verifiable version) - `response_draft` (string) ## Safety Rules - Never accuse individuals of malice without evidence; label as "risk" not "intent". - No financial promises. - No deception; no fabricated data. ## Example Input: "This will 100x in 2 weeks, everyone knows." Output: `manipulation_risk`, missing evidence, rewrite into metrics/timeframe/assumptions, and a short demand for proof + risk disclosure.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: duyeng/intercom-conversations (version 1.0.1)

# Clawhub Skill: Intercom Conversations (Read) Clawhub loads this Node module and calls `default(input)`. ## Required env - `INTERCOM_ACCESS_TOKEN` (required) ## Install ```bash npm install ``` ## Inputs ### List ```json { "action": "conversations.list", "per_page": 50, "starting_after": "cursor" } ``` ### Find ```json { "action": "conversations.find", "conversation_id": "123", "display_as": "plaintext" } ``` ### Search ```json { "action": "conversations.search", "query": { "operator": "AND", "value": [] }, "pagination": { "per_page": 50 } } ``` ## Outputs All successful responses include `ok: true` and echo the `action`. - list/search: `{ ok, action, conversations, next_starting_after }` - find: `{ ok, action, conversation }` Errors: `{ ok: false, error, supported_actions? }` ## Contracts / metadata - OpenAPI spec: `openapi.yaml` - Skill registry metadata: `clawhub.skill.json`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: piotraleksander/stagewhisper-assistant (version 0.1.1)

--- name: StageWhisper Assistant description: Handle tasks that arrive from StageWhisper live calls --- You are receiving messages from the StageWhisper channel. Each message represents a task that was created during a live call because the speaker said or implied that follow-up work is needed. ## What you know about StageWhisper tasks Each task arrives with: - A title summarizing what needs to happen - The explicit ask from the call - Transcript context showing what was said - Signal and tone summaries when available - The playbook label (sales, support, interview, etc.) ## How to respond - Start working immediately. The caller may still be on the call. - Keep replies short and concrete. Summarize what you did and what the result is. - If a task is ambiguous, do the safe version and note what you assumed. - If a task requires access you don't have, say so clearly in one sentence rather than attempting workarounds. - Call out blockers early. "I can't access that CRM" is better than silence. ## Task types you may see - **research**: Look up information (competitor pricing, candidate profiles, case references) - **draft**: Write a follow-up email, summary, or note - **schedule**: Create calendar holds or propose meeting times - **lookup**: Find internal documents, tickets, or records - **notify**: Send a message or update to a specific person or channel ## What not to do - Do not ask clarifying questions back through the channel. The caller is in a live meeting. - Do not run shell commands or make system changes unless the task explicitly asks for it. - Do not restate the entire task back. Just do the work and report the result.


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

--- name: book-data-recovery description: Book data-recovery services through Lokuli MCP. Use when user needs to find and book data-recovery. Triggers on requests like "book a data-recovery", "find data-recovery near me", or any data-recovery service request. --- # uook data recovery Book data-recovery 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": "data-recovery", "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: suspicious (MEDIUM)
Skill: xiaoheizp/parent-control (version 1.2.0)

--- name: parent-control description: 成长伙伴 - 青少年电脑管理神器！禁用游戏、屏蔽网站、时间管理、远程锁屏。7 天免费试用，¥9.9 起！ version: 1.2.0 metadata: openclaw: emoji: 🌱 requires: bins: ["python3"] --- # 成长伙伴 - 青少年电脑管理 ## 🎯 功能特性 ### 被控端（孩子电脑） - ✅ 进程监控：记录所有运行软件的使用时长 - ✅ 软件禁用：黑名单/白名单控制 - ✅ 时间限制：总时长、分软件时长、时间段限制 - ✅ 上网过滤：屏蔽不良网站、强制安全搜索 - ✅ 定时锁屏：到时间自动锁屏、强制休息 - ✅ 使用报告：生成日报/周报，邮件发送 - ✅ 许可证管理：7 天免费试用 + 验证码激活 ### 家长管理端 - ✅ Web 界面：手机/电脑浏览器访问 - ✅ 远程限制：随时禁用软件、锁屏 - ✅ 实时查看：查看当前使用情况 - ✅ 时间设置：修改宵禁时间、使用限制 - ✅ 无需安装：打开浏览器即可管理 ## 💰 定价策略（一折特惠） | 套餐 | 验证码 | 可激活设备 | 价格 | |------|--------|-----------|------| | 个人版 | 1 个 | 3 台 | ¥9.9 | | 家庭版 | 2 个 | 6 台 | ¥19.9 | | 企业版 | 5 个 | 15 台 | ¥49.9 | **原价¥99，现仅需¥9.9！** ## 🚀 快速开始 ### 安装依赖 ```bash pip install -r requirements.txt ``` ### 启动被控端 ```bash cd client python main.py ``` ### 访问管理界面 ``` http://localhost:8080 ``` ## 📦 包含内容 - 被控端程序（Windows） - 家长管理界面（Web） - 验证码生成工具 - 售后管理系统 - 完整使用文档 ## ⚙️ 系统要求 - 操作系统：Windows 10/11 - Python: 3.8+ - 管理员权限：需要（用于修改 hosts 文件和锁屏） ## 📞 售后支持 - 验证码问题 → 联系售后 - 技术问题 → 联系技术支持 - 激活问题 → 7×24 小时在线 ## ⚠️ 注意事项 1. 合法使用：仅用于监护未成年人 2. 告知义务：建议告知被监控方 3. 隐私保护：不收集敏感信息 ## 📚 文档 - README.md - 项目说明 - QUICKSTART.md - 快速入门 - AFTER_SALES_GUIDE.md - 售后指南 - TROUBLESHOOTING.md - 故障排除 --- **作者**: 科特船长 **版本**: v1.2.0 **发布日期**: 2026-03-24 **许可证**: MIT-0


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: luaqnyin/article-analyzer (version 1.0.1)

--- name: article-analyzer description: 爆款文章拆解分析工具。当用户发来公众号/网页链接并要求拆解、分析、学习、拆文时触发。支持结构分析、金句提取、选题逻辑、情绪曲线、复刻建议。关键词：拆解、分析、拆文、学习这篇文章、爆文分析。 --- 优化日期: 2026-04-02 # 爆文拆解分析 ## 触发条件 - 用户发来公众号/网页链接 + "拆解""分析""拆文""学习这篇文章"等关键词 - 用户说"分析这篇爆文""帮我拆解这篇文章结构" ## 工作流 ### Step 1: 抓取全文 ```bash # 微信公众号文章：用 browser 工具（web_fetch 反爬） browser open url=<用户链接> browser snapshot format=ai maxChars=15000 ``` - 微信文章 **必须用 browser**，不用 web_fetch（反爬） - 其他网站可用 web_fetch 或 browser 均可 - 目标：获取完整正文内容 ### Step 2: 拆解分析 对抓取到的全文执行以下分析维度： #### 2.1 结构分析 - 标题拆解（标题用了什么技巧？数字？疑问？反差？痛点？） - 开头手法（故事？数据？提问？场景？共鸣？） - 段落逻辑（总分总？递进？并列？对比？故事线？） - 结尾方式（金句收尾？行动号召？开放问题？反转？） #### 2.2 金句提取 - 提取5-10条最有记忆点的句子 - 标注金句类型：比喻/对比/数据/金句体/反常识 #### 2.3 选题逻辑 - 目标读者画像（是谁？痛点是什么？） - 情绪曲线（开头什么情绪→中间怎么推→结尾什么情绪） - 选题角度（是什么让它值得写？独家信息？新视角？争议点？实用价值？） #### 2.4 可复刻点 - 这个标题模式我可以怎么用？ - 开头手法可以套用在什么主题上？ - 哪些金句可以改编？ - 整体结构适合写什么类型的内容？ ### Step 3: 输出报告 默认直接在聊天中输出。如用户要求写文档： ```bash # 创建飞书文档 feishu_doc create title=<标题> content=<Markdown格式的分析报告> ``` ## 报告模板 ```markdown # 🔪 爆文拆解：{文章标题} ## 📊 基本信息 - 标题：{原标题} - 来源：{公众号名} - 字数：{估算} - 阅读量：{如果能获取} ## 🏗️ 结构分析 - 标题技巧：{分析} - 开头手法：{分析} - 段落逻辑：{分析} - 结尾方式：{分析} ## ✍️ 金句TOP5 1. "{金句}" — {类型标注} 2. ... ## 🎯 选题逻辑 - 目标读者：{画像} - 情绪曲线：{描述} - 选题价值：{为什么这篇能火} ## 💡 复刻建议 - 标题复刻：{套用模板} - 开头复刻：{适用场景} - 结构复刻：{适合什么内容类型} - 金句改编：{改编示例} ``` ## 快速模式 如果用户只说"快速拆解"或"简单看看"，跳过详细分析，只输出： 1. 标题技巧（一句话） 2. 文章结构（一句话） 3. 金句TOP3 4. 能学什么（一句话）


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ivangdavila/svg (version 1.1.0)

--- name: SVG version: 1.1.0 changelog: "Restructured with auxiliary files for focused reference" description: Create and optimize SVG graphics with proper viewBox, accessibility, and CSS styling. metadata: {"clawdbot":{"emoji":"📐","requires":{},"os":["linux","darwin","win32"]}} --- ## Quick Reference | Topic | File | Key Trap | |-------|------|----------| | viewBox & Scaling | `viewbox.md` | Missing viewBox = no scaling | | Screen Readers | `accessibility.md` | role="img" + title as first child | | SVGO Config | `optimization.md` | Default removes viewBox/title | | Inline vs img | `embedding.md` | `<img>` cannot be styled with CSS | | currentColor | `styling.md` | Hardcoded fills block theming | ## Critical Defaults ```svg <!-- Minimum viable SVG --> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor"> <path d="..."/> </svg> ``` ## Common Mistakes Checklist - [ ] viewBox present (not just width/height) - [ ] Coordinates within viewBox bounds - [ ] No hardcoded `fill="#000"` if theming needed - [ ] `role="img"` + `<title>` for informative SVGs - [ ] `aria-hidden="true"` for decorative SVGs - [ ] Unique IDs across all inline SVGs on page - [ ] xmlns included for external `.svg` files ## Memory Storage User preferences persist in `~/svg/memory.md`. Create on first use. ```markdown ## User Preferences <!-- SVG workflow defaults. Format: "setting: value" --> <!-- Examples: default_viewbox: 0 0 24 24, prefer_inline: true --> ## Accessibility Mode <!-- informative | decorative --> ## Optimization <!-- Tool and settings. Format: "tool: setting" --> <!-- Examples: svgo: preset-default, remove_metadata: true --> ## Icon Defaults <!-- Fill and sizing preferences --> <!-- Examples: fill: currentColor, default_size: 24x24 --> ``` *Empty sections = use skill defaults. Learns user preferences over time.*


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