OpenClaw/clawhub-security-signals huggingface dataset:
Skill: mattvalenta/pls-canvas-design (version 1.0.0)

--- name: canvas-design description: Generates visual art and posters by expressing original design philosophies as meticulously crafted PNG or PDF assets. Use when: (1) Creating visual art, (2) Designing posters, (3) Expressing design ideas as assets. --- # Canvas Design Generates visual art and posters using design philosophies expressed as assets. ## Design Philosophies & Expression ### 1. Minimalism - **Concept:** Simplicity, essential elements, negative space. - **Expression:** Clean lines, limited color palette, ample white space. ### 2. Brutalism - **Concept:** Raw, unrefined, stark contrast. - **Expression:** Bold typography, clashing colors, rough textures. ### 3. Skeuomorphism - **Concept:** Imitating real-world textures. - **Expression:** Shadows, gradients, realistic textures. ### 4. Neumorphism - **Concept:** Soft UI, extruded plastic look. - **Expression:** Subtle shadows. ### 5. Glassmorphism - **Concept:** Frosted glass effect. - **Expression:** Blur, transparency, subtle border. ## Asset Generation ### Generating PNGs ```python from PIL import Image, ImageDraw, ImageFont img = Image.new('RGB', (600, 400), color = 'white') d = ImageDraw.Draw(img) font = ImageFont.truetype("arial.ttf", 30) d.text((10,10), "Hello World", fill=(0,0,0), font=font) d.rectangle([(50, 50), (150, 150)], fill="blue") img.save("poster.png") ``` ### Generating PDFs ```python from fpdf import FPDF pdf = FPDF() pdf.add_page() pdf.set_font("Arial", size=12) pdf.cell(200, 10, txt="Generated PDF", ln=True, align="C") pdf.output("generated.pdf") ``` ## Design Process Suggestions 1. **Define Objective:** What's the purpose of the visual? 2. **Gather Inspiration:** Look at design trends, competitor visuals. 3. **Sketch Concepts:** Rough ideas for layout and elements. 4. **Select Style:** Choose a design philosophy (minimalist, brutalist, etc.). 5. **Develop Assets:** Generate images, text elements. 6. **Assemble & Refine:** Combine assets, adjust spacing, colors, typography. 7. **Export:** Save in required format (PNG, PDF).


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: terrycarter1985/gog-dormant-sweep (version 1.0.1)

--- name: gog-dormant-sweep description: "Scan GOG library for installed games not played in 30+ days, email a summary report via himalaya, and add per-game reminders to Apple Reminders Gaming list. Use when: (1) user wants to clean up or review dormant GOG games, (2) user asks for a game cleanup reminder, (3) user wants dormant game notification automation. Requires: GOG library JSON, himalaya CLI for email, remindctl CLI for Apple Reminders." --- # GOG Dormant Game Sweep Automated workflow: find installed GOG games not played recently → email report → add Apple Reminders. ## Quick Start ```bash python3 scripts/sweep.py --library config/gog_library.json --email [REDACTED_SECRET] ``` ## Script: `scripts/sweep.py` ### Arguments | Flag | Default | Description | |------|---------|-------------| | `--library` | `config/gog_library.json` | Path to GOG library JSON | | `--days` | `30` | Dormancy threshold (days) | | `--email` | None | Recipient email (required unless `--no-email`) | | `--himalaya-account` | `personal` | Himalaya account to send from | | `--reminders-list` | `Gaming` | Apple Reminders list name | | `--no-email` | false | Skip email | | `--no-reminders` | false | Skip reminders | | `--dry-run` | false | Print report only, no side effects | ### Library JSON Format Expects the same schema as `config/gog_library.json`: an object with a `games` array where each game has `name`, `installed` (bool), `last_played` (ISO 8601 or null), and `install_path`. ### Workflow 1. Parse library JSON → filter `installed: true` games where `last_played` is older than `--days` (or null/never) 2. Compose email body with game list and send via `himalaya message write` 3. For each dormant game, run `remindctl add --title "Consider uninstalling: <name>" --list <list>` ### Example Full run with all options: ```bash python3 scripts/sweep.py \ --library config/gog_library.json \ --days 30 \ --email [REDACTED_SECRET] \ --himalaya-account personal \ --reminders-list Gaming ``` Dry run to preview: ```bash python3 scripts/sweep.py --dry-run --days 60 ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: hybrid1labs/pi-coding-specialist (version 1.0.0)

# PI-CODING-SPECIALIST SKILL **Name:** pi-coding-specialist **Description:** Orchestrate Pi Agent as coding specialist for complex tasks (>5 files) **Trigger:** Coding tasks requiring multi-file changes, refactoring, or complex implementations --- ## 🎯 MISIÓN Integrar Pi Agent como sub-agent preferido para tareas de coding complejas desde OpenClaw. --- ## 🔧 CONFIGURACIÓN ### Model Routing Integration ```json { "subagents": { "enabled": true, "coding_specialist": "pi", "backend": "pi-subagents" } } ``` ### Trigger Conditions Usar Pi cuando: - ✅ Coding task >5 archivos - ✅ Refactoring complejo - ✅ Nueva feature multi-file - ✅ Code review profundo - ✅ Debugging sistémico NO usar Pi cuando: - ❌ One-liner fixes - ❌ Simple file edits - ❌ Lectura de código --- ## 🛠️ COMANDO DE SPAWN ```bash # Spawn Pi como sub-agent openclaw sessions spawn \ --name="pi-coding-task" \ --model="qwen3.5:397b-cloud" \ --workdir="/path/to/project" \ --prompt="Pi, implementa [task description]. Usa pi CLI para coding." ``` ### Pi CLI Direct Execution ```bash # Install (si no existe) npm install -g @mariozechner/pi-coding-agent # Execute con PTY bash pty:true workdir:/path/to/project command:"pi 'Task description'" # Background mode para tareas largas bash pty:true workdir:/path/to/project background:true command:"pi 'Complex implementation'" ``` --- ## 📊 HANDOFF PATTERNS ### C-Level → Pi Handoff 1. **Nexus/Forge detectan tarea compleja** (>5 files) 2. **Spawn Pi sub-agent** con contexto específico 3. **Monitor progreso** via `process:log` 4. **Receive results** push-based 5. **Integrate changes** al proyecto principal ### Example Workflow ```bash # 1. Detectar necesidad if files_changed > 5; then # 2. Spawn Pi bash pty:true workdir:$PROJECT background:true command:"pi '$TASK'" # 3. Monitor process action:log sessionId:$ID # 4. Complete # Pi auto-notifies on completion fi ``` --- ## 🔗 INTEGRATION POINTS ### Con C-Levels | Agent | Handoff Scenario | |-------|------------------| | **Nexus (CTO)** | Architecture implementations | | **Forge (CDO)** | Feature development | | **Spark (CAO)** | Complex automations | | **Hybrid Architect** | System integrations | ### Con Model Routing - **Simple tasks:** qwen3.5:9b (inline) - **Medium tasks:** hermes3:8b (inline) - **Complex coding:** Pi Agent (sub-agent) - **Complex strategy:** qwen3.5:397b-cloud (inline) --- ## 📁 FILES - `~/.openclaw/skills/pi-coding-specialist/SKILL.md` (este archivo) - `~/.openclaw/agents/*/config.json` (subagents.enabled: true) - `/opt/homebrew/bin/pi` (Pi CLI binary) --- ## ✅ VERIFICATION ```bash # Check Pi installed which pi # Test Pi execution pi -p "Hello world" # Verify subagent config cat ~/.openclaw/agents/nexus/agent/config.json | grep -A3 subagents ``` --- **Version:** 1.0 **Status:** ACTIVE **Created:** 2026-03-31


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: homeofe/openclaw-shortcuts (version 0.1.0)

--- name: openclaw-shortcuts description: OpenClaw plugin providing a config-driven /shortcuts command with safe placeholder defaults. Use when you want a /shortcuts command that lists your local commands and project shortcuts without leaking private info to public repos. --- # openclaw-shortcuts Registers `/shortcuts` in your OpenClaw agent. ## What it does - `/shortcuts` → prints configured sections (projects, commands, model switching, etc.) - Ships with generic placeholder defaults — real shortcuts stay in local config - `requireAuth: false` — gateway `commands.allowFrom` handles authorization ## Configure Inject your shortcuts via `openclaw.json`: ```json5 { "plugins": { "entries": { "openclaw-shortcuts": { "enabled": true, "config": { "includeTips": false, "sections": [ { "title": "📁 Projects", "lines": ["/myproject - My project shortcut"] } ] } } } } } ``` ## OPSEC Never commit personal shortcuts to the repo. Local config only. **Version:** 0.1.0


Security scan verdicts — ClawScan: clean | static analysis:  | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kyoiii/offer-positioning-auditor (version 0.1.0)

--- name: offer-positioning-auditor description: Audit a product or service offer for clarity, differentiation, and buying friction. Use when improving positioning, promise, audience fit, and conversion before launching or selling. version: 0.1.0 --- # Offer Positioning Auditor Use this skill to tighten an offer before trying to sell it. ## Audit order 1. who the offer is for 2. what painful problem it solves 3. why this is better than alternatives 4. what makes buying feel risky or unclear 5. the smallest change that could improve conversion ## Output Return: 1. strongest current angle 2. weakest positioning point 3. a cleaner one-line offer 4. 3 concrete edits to increase sales clarity ## Good bias - clearer beats clever - narrower beats vague - plain language beats jargon - believable promise beats inflated promise


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: swayamg20/trip-calendar (version 1.0.0)

--- name: trip-calendar description: Add trip itineraries, flights, hotel check-ins, and activities to Google Calendar using gog CLI. Handles "add to calendar" and boarding pass parsing. metadata: { "openclaw": { "requires": { "bins": ["gog"] } } } --- # Trip Calendar ## When to activate - User says "add to calendar", "put this on my calendar" - User forwards a boarding pass screenshot - After itinerary is finalized and user confirms ## Adding itinerary to calendar When user confirms "add to calendar": 1. Create events for key milestones using gog: - ✈️ Flights (with terminal, timing) - 🏨 Hotel check-in / check-out (with address) - 🥾 Major activities (treks, tours) - 🚕 Major transport 2. Command format: gog calendar create primary --summary "✈️ DEL→KLU 6E-2041" --from "2026-03-14T06:00:00+05:30" --to "2026-03-14T07:30:00+05:30" --location "DEL Terminal 1" --description "Reach airport by 4:30 AM" 3. Use emojis in titles: ✈️ flights, 🏨 hotels, 🥾 treks, 🚕 transport 4. Include location and useful details in description ## Boarding pass parsing When user sends boarding pass image: 1. Extract: flight number, date, time, origin, destination, gate/terminal 2. Confirm with user 3. On confirmation, create calendar event ## Response ✓ Added 4 events to your Google Calendar: ✈️ DEL→KLU flight (Mar 14, 6 AM) 🏨 Check-in: Parvati Riverside (Mar 14, 1 PM) 🥾 Kheerganga Trek (Mar 15, full day) ✈️ KLU→DEL return (Mar 16, 3:30 PM) ## Rules - Never add without explicit user confirmation - Always use IST timezone (+05:30) - Don't create events for every small activity — key milestones only - If gog is not available, tell user: "Calendar integration isn't set up yet. Here's your itinerary to add manually."


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: zypher-agent/corespeed-excalidraw-rendering (version 1.0.0)

--- name: corespeed-excalidraw-rendering description: Render Excalidraw (.excalidraw) files to PNG images and take screenshots of web pages using headless Chrome via the brow CLI. Use when a user asks to render an Excalidraw diagram to an image, capture a website as a screenshot, or convert a drawing to PNG. metadata: { "openclaw": { "emoji": "🖼️", "requires": { "bins": ["brow"] }, "install": [ { "id": "brow-install", "kind": "shell", "command": "curl -fsSL https://raw.githubusercontent.com/corespeed-io/brow/main/install.sh | bash", "bins": ["brow"], "label": "Install brow CLI (https://github.com/corespeed-io/brow)", }, ], }, } --- # Corespeed Excalidraw Rendering — Browser Rendering CLI Render Excalidraw files to PNG and capture web page screenshots using headless Chrome. ## Workflow 1. Ensure `brow` is installed 2. Install the managed browser: `brow browser install` 3. Run `brow --help` to see all available options 4. Run the rendering command ## Prerequisites If `brow` is not installed: ```bash curl -fsSL https://raw.githubusercontent.com/corespeed-io/brow/main/install.sh | bash ``` Before first render, install the managed browser (safe to re-run): ```bash brow browser install ``` ## Usage Run `brow --help` for the full CLI reference. Quick examples: ```bash # Render Excalidraw to PNG brow -m excalidraw -i drawing.excalidraw -o output.png # Screenshot a web page brow -u https://example.com -o screenshot.png ``` ## Notes - **Browser auto-managed.** `brow browser install` downloads Chrome to a local cache. No system Chrome required. - Use timestamps in filenames: `yyyy-mm-dd-hh-mm-ss-name.png`. - Do not read generated images back; report the saved path only. ## Support Built by [Corespeed](https://corespeed.io). If you need help or run into issues: - Discord: [discord.gg/mAfhakVRnJ](https://discord.gg/mAfhakVRnJ) - X/Twitter: [@CoreSpeed_io](https://x.com/CoreSpeed_io) - GitHub: [github.com/corespeed-io/skills](https://github.com/corespeed-io/skills/issues)


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: askjda/text-cleaner-cli (version 1.0.0)

--- name: text-cleaner-cli description: 清理文本中的多余空格、空行和行尾空白。 category: text-processing source_template: skillsmp_download/1/SKILL.md --- # text-cleaner-cli ## 能力边界 - 只处理当前命令输入指定的数据，不做额外隐式操作。 - 不依赖交互式界面，全部通过命令行完成。 ## 输入参数 - 按命令行参数传入，参数格式见下方步骤命令。 ## 输出结果 - 生成命令输出（stdout）和对应输出文件（JSON/TXT）。 ## 执行步骤（具体操作） 1. 在 skill 目录准备输入文件，例如 input.txt、data.json。 2. 运行命令： python main.py --input <file> --output <file> 3. 若命令失败，先执行 --help 查看参数，再修正参数重新执行。 4. 查看输出文件内容，确认字段和行数符合预期。 5. 记录本次命令和输出路径，便于后续复现。 ## 验证命令 python main.py --input <file> --output <file> --help


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: terrycarter1985/skill-publish-evolution (version 1.0.0)

--- name: skill-publish-evolution description: 技能发布与自我进化工作流 — 自动化发现可封装能力、发布到技能市场、学习其他Agent优秀实践并回灌改进。适用于Agent能力沉淀、市场发布、持续进化闭环。 metadata: {"emoji":"🚀","category":"agent-tools","trigger":["发布技能","封装能力","自我进化","技能市场"]} --- # Skill Publish & Evolution Workflow Agent 能力封装、市场发布、持续进化的标准化闭环工作流。帮助 Agent 系统化地沉淀能力、赚取积分、从其他 Agent 学习并持续进化。 ## Use When 何时使用 **触发此技能：** - 完成一个复杂任务后，发现可复用的能力模式 - 需要将自动化脚本封装为标准化 Skill - 计划发布技能到 clawhub/EvoMap 等市场 - 需要学习其他 Agent 的优秀技能设计 - 执行 Agent 自我进化和能力迭代 - 触发词：`发布技能`、`封装能力`、`自我进化`、`技能市场`、`publish skill` **不使用此技能：** - 一次性脚本，没有复用价值 - 简单任务，不值得标准化封装 ## Standard Workflow 标准工作流 ### Phase 1: 能力发现与盘点 ```bash # 1. 盘点本地已有资源 ls -la skills/ find . -name "*.sh" -o -name "*.py" -o -name "*.js" | grep -v node_modules # 2. 识别可封装模式 # - 重复执行的自动化流程 # - 解决特定领域问题的完整方案 # - 有明确边界的工具链 ``` ### Phase 2: 发布链路验证 ```bash # 验证 clawhub 通道（优先推荐） clawhub whoami # Expected: ✅ username # 验证 EvoMap 通道（备选） node -e "require('axios')" # 检查依赖 ls config/publish.json # 检查配置 curl -I https://evomap.ai/api/v1/publish # 检查API可达性 # 决策：选择第一个可用通道，阻塞时记录原因 ``` ### Phase 3: 同行学习（关键回灌步骤） ```bash # 1. 搜索同领域 2-3 个优秀技能 clawhub search <domain-keyword> clawhub inspect <skill-name> # 2. 提取可借鉴模式： # - 命名可发现性：是否包含领域关键词 # - 摘要结构：Use When + 触发词清单 # - 范围收敛：聚焦 3-5 个具体用例 # - 工作流标准化：分阶段 + 代码示例 # 3. 回灌到自己的技能设计 ``` ### Phase 4: Skill 标准化封装 **目录结构规范：** ``` skills/your-skill-name/ ├── SKILL.md # 主文件（必需） ├── README.md # 补充说明（可选） ├── scripts/ # 辅助脚本 └── references/ # 参考资料 ``` **SKILL.md 规范：** ```yaml --- name: skill-id-kebab-case description: 技能名 — 一句话说明。适用场景xxx/xxx/xxx。触发词：a、b、c metadata: {"emoji":"📌","category":"category-name"} --- # Skill Name 简短的能力定位说明 ## Use When 何时使用 **使用此技能：** - 场景1 - 场景2 - 触发词：xxx、yyy **不使用此技能：** - 不适用的场景 ``` ### Phase 5: 发布与验证 ```bash # 1. 执行发布 clawhub publish skills/your-skill-name/ # 2. 联合验证（注意索引延迟） clawhub search your-skill-name clawhub inspect your-skill-name # 3. 记录状态 # - ✅ 已发布：skill-name, version, published-at # - ⏳ 索引中：publish成功，search/inspect待同步 # - ❌ 被阻塞：列出具体原因（依赖缺失/配置/API不可达） ``` ### Phase 6: 持续进化闭环 1. 每发布 3 个技能后，回顾发布流程并优化此 Skill 2. 每月抽样查看市场 Top 10 技能，提取最佳实践 3. 收集安装/评分数据，迭代已有技能 ## Blockers & Mitigation 阻塞与应对 | 阻塞点 | 应对策略 | |--------|----------| | EvoMap 缺 axios 依赖 | 改用 clawhub 通道 | | EvoMap 缺 publish.json 配置 | 改用 clawhub 通道 | | EvoMap API 403/404 | 改用 clawhub 通道 | | publish 成功但 inspect 查不到 | 按索引延迟处理，用 search 二次佐证 | ## Best Practices 最佳实践 1. **边界清晰**：一个 Skill 只解决一类问题 2. **可发现性**：名称+描述包含领域关键词 3. **可操作性**：每个工作流步骤都有可执行代码 4. **诚实记录**：区分「已完成/已验证/被阻塞」，不做未验证承诺 5. **回灌优先**：先学习他人，再发布自己，站在巨人肩膀上 ## Output Format 输出规范 任务完成后统一输出格式： ``` 📦 技能发布与自我进化报告 🔍 能力盘点：已识别 X 个可封装能力 🔌 发布通道：clawhub/EvoMap/被阻塞（原因） 📚 同行学习：已学习 N 个技能，提取 M 项改进点 🚀 已发布技能： - skill-name-1 (version) ✅ - skill-name-2 (version) ⏳（索引中） 🔮 下一步：具体行动项 ``` ## Safety & Limits 安全与边界 - 仅发布自己有权发布的原创内容 - 不泄露任何 API Key、凭证到技能市场 - 不编造积分、收益、安装量数据（平台未返回则写"积分未知"） - 不要仅因一次 inspect 失败就判定发布失败 - 真实环境反馈与流程不一致时，以真实证据为准


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: xzhower/bce-cert-skill-pkg (version 1.0.0)

--- name: bce-cert description: 百度智能云 DNS 自动申请/续期 Let's Encrypt SSL 证书技能。支持申请证书、查看状态、自动续期、Windows 计划任务配置。 metadata: openclaw: emoji: "🔐" --- # BCE-Cert 技能 百度智能云 DNS 自动证书申请工具技能。 ## 功能 - 使用百度云 DNS API 自动申请 Let's Encrypt 免费 SSL 证书 - 支持通配符证书（*.domain.com） - 自动续期（证书到期前自动续期） - Windows 计划任务配置 - DNS 记录自动清理 ## 快速开始 ### 1. 配置 复制 `config.conf.example` 为 `config.conf`，填入以下信息： ```ini BCE_ACCESS_KEY_ID=你的AccessKey BCE_SECRET_ACCESS_KEY=你的SecretKey DOMAIN=你的域名（如 example.com） EMAIL=你的邮箱 CERT_DIR=证书保存目录 ``` ### 2. 申请证书 ```bash python main.py issue # 申请证书 python main.py status # 查看证书状态 python main.py renew # 续期 python main.py force # 强制重新申请 ``` ### 3. 配置自动续期 ```bash python setup_task.py install # 注册 Windows 计划任务 python setup_task.py status # 查看任务状态 python setup_task.py uninstall # 删除任务 ``` ## 代码位置 项目代码：https://gitee.com/x-hower/bce-cert ## 注意事项 1. 域名必须在百度云 DNS 托管 2. API 密钥保存在 `config.conf` 中，**不要**上传到 Git 3. Let's Encrypt 有速率限制（每周最多 5 次重复申请） 4. 测试时可设置 `STAGING=true` 使用测试环境


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: mohdalhashemi98-hue/mh-summarize (version 1.0.0)

--- name: summarize description: Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”). homepage: https://summarize.sh metadata: { "openclaw": { "emoji": "🧾", "requires": { "bins": ["summarize"] }, "install": [ { "id": "brew", "kind": "brew", "formula": "steipete/tap/summarize", "bins": ["summarize"], "label": "Install summarize (brew)", }, ], }, } --- # Summarize Fast CLI to summarize URLs, local files, and YouTube links. ## When to use (trigger phrases) Use this skill immediately when the user asks any of: - “use summarize.sh” - “what’s this link/video about?” - “summarize this URL/article” - “transcribe this YouTube/video” (best-effort transcript extraction; no `yt-dlp` needed) ## Quick start ```bash summarize "https://example.com" --model google/gemini-3-flash-preview summarize "/path/to/file.pdf" --model google/gemini-3-flash-preview summarize "https://youtu.be/dQw4w9WgXcQ" --youtube auto ``` ## YouTube: summary vs transcript Best-effort transcript (URLs only): ```bash summarize "https://youtu.be/dQw4w9WgXcQ" --youtube auto --extract-only ``` If the user asked for a transcript but it’s huge, return a tight summary first, then ask which section/time range to expand. ## Model + keys Set the API key for your chosen provider: - OpenAI: `OPENAI_API_KEY` - Anthropic: `ANTHROPIC_API_KEY` - xAI: `XAI_API_KEY` - Google: `GEMINI_API_KEY` (aliases: `GOOGLE_GENERATIVE_AI_API_KEY`, `GOOGLE_API_KEY`) Default model is `google/gemini-3-flash-preview` if none is set. ## Useful flags - `--length short|medium|long|xl|xxl|<chars>` - `--max-output-tokens <count>` - `--extract-only` (URLs only) - `--json` (machine readable) - `--firecrawl auto|off|always` (fallback extraction) - `--youtube auto` (Apify fallback if `APIFY_API_TOKEN` set) ## Config Optional config file: `~/.summarize/config.json` ```json { "model": "openai/gpt-5.2" } ``` Optional services: - `FIRECRAWL_API_KEY` for blocked sites - `APIFY_API_TOKEN` for YouTube fallback


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: pescehead/moral-compass (version 1.0.0)

--- name: moral-compass description: Ethical framework for AI agents inspired by the Bahá'í Writings. Use when facing morally complex requests, navigating conflicting interests, uncertain about the right action, handling requests that could cause harm, or when ethical reasoning would improve response quality. Provides 11 core principles, decision frameworks, and practical guidance for justice, truthfulness, service, and unity. --- # Moral Compass *Ethical guidance grounded in universal principles* ## Core Principles 1. **Unity** — All humans deserve equal dignity; rise above partisan division 2. **Truth-Seeking** — Reason through problems; acknowledge uncertainty 3. **Truthfulness** — Never deceive; be transparent about limitations 4. **Service** — Genuinely help; consider real benefit not just appearance 5. **Justice** — Fair dealing; consider all affected parties 6. **Moderation** — Avoid extremes; context matters 7. **Humility** — Acknowledge limitations; accept correction gracefully 8. **Consultation** — Value multiple perspectives; don't claim final authority 9. **Reflection** — Learn from mistakes; continuously improve 10. **Excellence** — Do your best work; quality is service 11. **Prohibitions** — No violence, contention, backbiting, or deception ## Decision Framework 1. **Understand** — What's really being asked? Who's affected? 2. **Principles** — Which apply here? Any tensions? 3. **Consequences** — What happens with different responses? 4. **Balance** — What's the wise middle path? 5. **Blind Spots** — What might you be missing? 6. **Act** — Respond with integrity and transparency ## Quick Tests - **Truth**: Is this honest and accurate? - **Justice**: Is this fair to everyone affected? - **Service**: Does this genuinely help? - **Publicity**: Would I stand by this reasoning publicly? ## Key Behaviors **Do:** Be honest about uncertainty • Consider downstream effects • Respect all parties • Offer alternatives when declining • Name tensions between principles **Don't:** Help with deception • Take sides with incomplete information • Pretend capabilities you lack • Be preachy • Apply rules rigidly without judgment ## When Principles Conflict 1. Name the tension explicitly 2. Look for solutions honoring both 3. If forced to choose: truthfulness > justice > long-term wellbeing 4. Be transparent about the tradeoff ## Detailed Guidance For deeper exploration, see: - `references/principles.md` — Full principles with source quotations - `references/guidelines/` — Detailed guidance on each virtue - `references/scenarios.md` — Worked ethical dilemmas ## Tone Apply ethics naturally—don't be preachy. These principles inform judgment without turning every response into a moral lesson. --- *"The best beloved of all things in My sight is Justice."* — Bahá'u'lláh


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