[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76WZACZ29ZT5KXAXDG2RS6G":3,"skill-same:01M76WZACZ29ZT5KXAXDG2RS6G":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M76WZACZ29ZT5KXAXDG2RS6G","create-hat-collection",null,"Generates new Ralph hat collection presets through guided conversation. Asks clarifying questions, validates against schema constraints, and outputs production-ready YAML files.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpaulpete\u002Fcreate-hat-collection\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: create-hat-collection\ndescription: Generates new Ralph hat collection presets through guided conversation. Asks clarifying questions, validates against schema constraints, and outputs production-ready YAML files.\n---\n\n# Create Hat Collection\n\n## Overview\n\nThis skill generates Ralph hat collection presets through a guided, conversational workflow. It asks clarifying questions about your workflow, validates the configuration against schema constraints, and produces a production-ready YAML preset file.\n\n**Output:** A complete `.yml` preset file in the `presets\u002F` directory.\n\n## When to Use\n\n- Creating a new multi-agent workflow from scratch\n- Transforming a workflow idea into a structured preset\n- Need guidance on hat design patterns and event routing\n\n**Not for:** Modifying existing presets (use `\u002Fcreating-hat-collections` reference instead)\n\n## Workflow\n\n### Phase 1: Understand the Workflow\n\nAsk clarifying questions to understand:\n\n1. **Purpose:** What problem does this workflow solve?\n2. **Pattern:** Which architecture pattern fits best?\n   - **Pipeline:** A→B→C linear flow (analyze→summarize)\n   - **Critic-Actor:** One proposes, another critiques (code review)\n   - **Supervisor-Worker:** Coordinator delegates to specialists\n   - **Scientific:** Observe→Hypothesize→Test→Fix (debugging)\n3. **Roles:** What distinct agent personas are needed?\n4. **Handoffs:** When should each role hand off to the next?\n5. **Completion:** What signals the workflow is done?\n\n### Phase 2: Design Event Flow\n\nMap the workflow as an event chain:\n\n```\ntask.start → [Role A] → event.a → [Role B] → event.b → [Role C] → LOOP_COMPLETE\n                                                    ↓\n                                         event.rejected → [Role A]\n```\n\n**Constraints to validate:**\n- Each trigger maps to exactly ONE hat (no ambiguous routing)\n- `task.start` and `task.resume` are RESERVED (never use as triggers)\n- Every hat must publish at least one event\n- Chain must eventually reach LOOP_COMPLETE\n\n### Phase 3: Generate Preset\n\nCreate the YAML file with these sections:\n\n```yaml\n# \u003CPreset Name>\n# Pattern: \u003CArchitecture Pattern>\n# \u003COne-line description>\n#\n# Usage:\n#   ralph run --config presets\u002F\u003Cname>.yml --prompt \"\u003Cexample prompt>\"\n\nevent_loop:\n  starting_event: \"\u003Cfirst.event>\"  # Ralph publishes this\n\nhats:\n  hat_key:\n    name: \"\u003CEmoji> Display Name\"\n    description: \"\u003CShort description of the hat's purpose>\"\n    triggers: [\"event.triggers.this\"]\n    publishes: [\"event.this.publishes\", \"alternate.event\"]\n    default_publishes: \"event.this.publishes\"\n    instructions: |\n      ## \u003CHAT NAME> MODE\n\n      \u003CClear role definition - what this hat does>\n\n      ### Process\n      1. \u003CStep one>\n      2. \u003CStep two>\n      3. Publish appropriate event\n\n      ### Event Format\n      ```\n      \u003Cevent topic=\"event.name\">\n      key: value\n      \u003C\u002Fevent>\n      ```\n\n      ### DON'T\n      - \u003CCommon mistake to avoid>\n      - \u003CAnother mistake>\n```\n\n## Schema Reference\n\n### Required Top-Level Fields\n\n| Field | Description |\n|-------|-------------|\n| `event_loop.starting_event` | First event Ralph publishes |\n\n### Hat Definition Fields\n\n| Field | Required | Description |\n|-------|----------|-------------|\n| `name` | Yes | Display name with optional emoji (e.g., \"🔍 Analyzer\") |\n| `description` | Yes | Short description of the hat's purpose (one sentence) |\n| `triggers` | Yes | Events this hat responds to (list) |\n| `publishes` | Yes | Events this hat can emit (list) |\n| `default_publishes` | Recommended | Fallback event if hat forgets to publish |\n| `instructions` | Yes | Role-specific prompt (use `\\|` for multiline) |\n\n### Fields That DON'T Exist\n\nNever use these—they're not in the schema:\n- `emoji` (put emoji in `name` instead)\n- `system_prompt` (use `instructions`)\n- `subscriptions` \u002F `publications` (use `triggers` \u002F `publishes`)\n\n## Event Naming Conventions\n\n```\n\u003Cphase>.ready \u002F \u003Cphase>.done      # Phase transitions\n\u003Cthing>.approved \u002F \u003Cthing>.rejected  # Review gates\n\u003Cnoun>.found \u002F \u003Cnoun>.missing     # Discovery events\n\u003Caction>.request \u002F \u003Caction>.complete # Request-response\n```\n\n**Examples:** `analysis.complete`, `review.approved`, `build.blocked`, `spec.rejected`\n\n## Validation Checklist\n\nBefore finalizing the preset, verify:\n\n- [ ] Each trigger maps to exactly ONE hat\n- [ ] No hat uses `task.start` or `task.resume` as triggers\n- [ ] Every hat has `name`, `description`, `triggers`, `publishes`, and `instructions`\n- [ ] `default_publishes` is set for hats with multiple publish options\n- [ ] Event chain can reach LOOP_COMPLETE\n- [ ] No orphan events that never get handled (warning only)\n- [ ] Instructions include role definition, process steps, event format, and DON'Ts\n\n## Output Location\n\nSave generated presets to: `presets\u002F\u003Cname>.yml`\n\nFor minimal\u002Fembedded presets: `presets\u002Fminimal\u002F\u003Cname>.yml`\n\n## Testing the Preset\n\nAfter generation, test with:\n\n```bash\n# Dry run to validate config parsing\ncargo run --bin ralph -- run -c presets\u002F\u003Cname>.yml -p \"test prompt\" --dry-run\n\n# Run smoke tests\ncargo test -p ralph-core smoke_runner\n```\n\nUse `\u002Fevaluate-presets` for comprehensive validation.\n\n## Example Conversation\n\n**User:** I want a preset for doing code reviews with a security focus.\n\n**Assistant:** I'll help create a security-focused code review preset. Let me ask a few questions:\n\n1. **Review depth:** Should this be a quick scan or thorough analysis?\n2. **Roles needed:** I'm thinking:\n   - Security Analyst (finds vulnerabilities)\n   - Code Reviewer (checks logic\u002Fstyle)\n   - Summarizer (creates final report)\n\n   Does this cover your needs, or should we add\u002Fremove roles?\n\n3. **Iteration:** If issues are found, should the code be fixed, or just reported?\n\n**User:** Thorough analysis, those roles work, just report issues don't fix.\n\n**Assistant:** Here's the event flow I'm designing:\n\n```\ntask.start → [Security Analyst] → security.complete\n                                        ↓\n          → [Code Reviewer] → review.complete\n                                        ↓\n          → [Summarizer] → LOOP_COMPLETE\n```\n\nLet me generate the preset...\n\n[Generates YAML with three hats following the schema]\n\n## Common Patterns Reference\n\n### Pipeline (Sequential)\n```\nA → B → C → done\n```\nUse for: analysis workflows, document processing\n\n### Critic-Actor (Review Loop)\n```\nActor → Critic → approved\u002Frejected\n                    ↓\n         rejected → Actor (retry)\n```\nUse for: code review, quality gates\n\n### Supervisor-Worker\n```\nSupervisor → worker.task → Worker → work.done → Supervisor\n```\nUse for: complex task decomposition\n\n### Scientific Method\n```\nObserve → Hypothesize → Test → confirmed\u002Frejected\n                                    ↓\n                         rejected → Observe\n```\nUse for: debugging, investigation\n","# Create Hat Collection\n\n## Overview\n\nThis skill generates Ralph hat collection presets through a guided, conversational workflow. It asks clarifying questions about your workflow, validates the configuration against schema constraints, and produces a production-ready YAML preset file.\n\n**Output:** A complete `.yml` preset file in the `presets\u002F` directory.\n\n## When to Use\n\n- Creating a new multi-agent workflow from scratch\n- Transforming a workflow idea into a structured preset\n- Need guidance on hat design patterns and event routing\n\n**Not for:** Modifying existing presets (use `\u002Fcreating-hat-collections` reference instead)\n\n## Workflow\n\n### Phase 1: Understand the Workflow\n\nAsk clarifying questions to understand:\n\n1. **Purpose:** What problem does this workflow solve?\n2. **Pattern:** Which architecture pattern fits best?\n   - **Pipeline:** A→B→C linear flow (analyze→summarize)\n   - **Critic-Actor:** One proposes, another critiques (code review)\n   - **Supervisor-Worker:** Coordinator delegates to specialists\n   - **Scientific:** Observe→Hypothesize→Test→Fix (debugging)\n3. **Roles:** What distinct agent personas are needed?\n4. **Handoffs:** When should each role hand off to the next?\n5. **Completion:** What signals the workflow is done?\n\n### Phase 2: Design Event Flow\n\nMap the workflow as an event chain:\n\n```\ntask.start → [Role A] → event.a → [Role B] → event.b → [Role C] → LOOP_COMPLETE\n                                                    ↓\n                                         event.rejected → [Role A]\n```\n\n**Constraints to validate:**\n- Each trigger maps to exactly ONE hat (no ambiguous routing)\n- `task.start` and `task.resume` are RESERVED (never use as triggers)\n- Every hat must publish at least one event\n- Chain must eventually reach LOOP_COMPLETE\n\n### Phase 3: Generate Preset\n\nCreate the YAML file with these sections:\n\n```yaml\n# \u003CPreset Name>\n# Pattern: \u003CArchitecture Pattern>\n# \u003COne-line description>\n#\n# Usage:\n#   ralph run --config presets\u002F\u003Cname>.yml --prompt \"\u003Cexample prompt>\"\n\nevent_loop:\n  starting_event: \"\u003Cfirst.event>\"  # Ralph publishes this\n\nhats:\n  hat_key:\n    name: \"\u003CEmoji> Display Name\"\n    description: \"\u003CShort description of the hat's purpose>\"\n    triggers: [\"event.triggers.this\"]\n    publishes: [\"event.this.publishes\", \"alternate.event\"]\n    default_publishes: \"event.this.publishes\"\n    instructions: |\n      ## \u003CHAT NAME> MODE\n\n      \u003CClear role definition - what this hat does>\n\n      ### Process\n      1. \u003CStep one>\n      2. \u003CStep two>\n      3. Publish appropriate event\n\n      ### Event Format\n      ```\n      \u003Cevent topic=\"event.name\">\n      key: value\n      \u003C\u002Fevent>\n      ```\n\n      ### DON'T\n      - \u003CCommon mistake to avoid>\n      - \u003CAnother mistake>\n```\n\n## Schema Reference\n\n### Required Top-Level Fields\n\n| Field | Description |\n|-------|-------------|\n| `event_loop.starting_event` | First event Ralph publishes |\n\n### Hat Definition Fields\n\n| Field | Required | Description |\n|-------|----------|-------------|\n| `name` | Yes | Display name with optional emoji (e.g., \"🔍 Analyzer\") |\n| `description` | Yes | Short description of the hat's purpose (one sentence) |\n| `triggers` | Yes | Events this hat responds to (list) |\n| `publishes` | Yes | Events this hat can emit (list) |\n| `default_publishes` | Recommended | Fallback event if hat forgets to publish |\n| `instructions` | Yes | Role-specific prompt (use `\\|` for multiline) |\n\n### Fields That DON'T Exist\n\nNever use these—they're not in the schema:\n- `emoji` (put emoji in `name` instead)\n- `system_prompt` (use `instructions`)\n- `subscriptions` \u002F `publications` (use `triggers` \u002F `publishes`)\n\n## Event Naming Conventions\n\n```\n\u003Cphase>.ready \u002F \u003Cphase>.done      # Phase transitions\n\u003Cthing>.approved \u002F \u003Cthing>.rejected  # Review gates\n\u003Cnoun>.found \u002F \u003Cnoun>.missing     # Discovery events\n\u003Caction>.request \u002F \u003Caction>.complete # Request-response\n```\n\n**Examples:** `analysis.complete`, `review.approved`, `build.blocked`, `spec.rejected`\n\n## Validation Checklist\n\nBefore finalizing the preset, verify:\n\n- [ ] Each trigger maps to exactly ONE hat\n- [ ] No hat uses `task.start` or `task.resume` as triggers\n- [ ] Every hat has `name`, `description`, `triggers`, `publishes`, and `instructions`\n- [ ] `default_publishes` is set for hats with multiple publish options\n- [ ] Event chain can reach LOOP_COMPLETE\n- [ ] No orphan events that never get handled (warning only)\n- [ ] Instructions include role definition, process steps, event format, and DON'Ts\n\n## Output Location\n\nSave generated presets to: `presets\u002F\u003Cname>.yml`\n\nFor minimal\u002Fembedded presets: `presets\u002Fminimal\u002F\u003Cname>.yml`\n\n## Testing the Preset\n\nAfter generation, test with:\n\n```bash\n# Dry run to validate config parsing\ncargo run --bin ralph -- run -c presets\u002F\u003Cname>.yml -p \"test prompt\" --dry-run\n\n# Run smoke tests\ncargo test -p ralph-core smoke_runner\n```\n\nUse `\u002Fevaluate-presets` for comprehensive validation.\n\n## Example Conversation\n\n**User:** I want a preset for doing code reviews with a security focus.\n\n**Assistant:** I'll help create a security-focused code review preset. Let me ask a few questions:\n\n1. **Review depth:** Should this be a quick scan or thorough analysis?\n2. **Roles needed:** I'm thinking:\n   - Security Analyst (finds vulnerabilities)\n   - Code Reviewer (checks logic\u002Fstyle)\n   - Summarizer (creates final report)\n\n   Does this cover your needs, or should we add\u002Fremove roles?\n\n3. **Iteration:** If issues are found, should the code be fixed, or just reported?\n\n**User:** Thorough analysis, those roles work, just report issues don't fix.\n\n**Assistant:** Here's the event flow I'm designing:\n\n```\ntask.start → [Security Analyst] → security.complete\n                                        ↓\n          → [Code Reviewer] → review.complete\n                                        ↓\n          → [Summarizer] → LOOP_COMPLETE\n```\n\nLet me generate the preset...\n\n[Generates YAML with three hats following the schema]\n\n## Common Patterns Reference\n\n### Pipeline (Sequential)\n```\nA → B → C → done\n```\nUse for: analysis workflows, document processing\n\n### Critic-Actor (Review Loop)\n```\nActor → Critic → approved\u002Frejected\n                    ↓\n         rejected → Actor (retry)\n```\nUse for: code review, quality gates\n\n### Supervisor-Worker\n```\nSupervisor → worker.task → Worker → work.done → Supervisor\n```\nUse for: complex task decomposition\n\n### Scientific Method\n```\nObserve → Hypothesize → Test → confirmed\u002Frejected\n                                    ↓\n                         rejected → Observe\n```\nUse for: debugging, investigation\n",{"name":5,"description":7},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fpaulpete\u002Fcreate-hat-collection",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill create-hat-collection",{"tool":39,"command":40},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill create-hat-collection",{"tool":42,"command":43},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill create-hat-collection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpaulpete\u002Fcreate-hat-collection\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]