create-hat-collection
Generates new Ralph hat collection presets through guided conversation. Asks clarifying questions, validates against schema constraints, and outputs production-ready YAML files.
- License 许可
- MIT
- 最近更新
- 2026-06-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- create-hat-collection
- description
- Generates new Ralph hat collection presets through guided conversation. Asks clarifying questions, validates against schema constraints, and outputs production-ready YAML files.
03 SKILL.md 正文
Create Hat Collection
Overview
This 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.
Output: A complete .yml preset file in the presets/ directory.
When to Use
- Creating a new multi-agent workflow from scratch
- Transforming a workflow idea into a structured preset
- Need guidance on hat design patterns and event routing
Not for: Modifying existing presets (use /creating-hat-collections reference instead)
Workflow
Phase 1: Understand the Workflow
Ask clarifying questions to understand:
- Purpose: What problem does this workflow solve?
- Pattern: Which architecture pattern fits best?
- Pipeline: A→B→C linear flow (analyze→summarize)
- Critic-Actor: One proposes, another critiques (code review)
- Supervisor-Worker: Coordinator delegates to specialists
- Scientific: Observe→Hypothesize→Test→Fix (debugging)
- Roles: What distinct agent personas are needed?
- Handoffs: When should each role hand off to the next?
- Completion: What signals the workflow is done?
Phase 2: Design Event Flow
Map the workflow as an event chain:
task.start → [Role A] → event.a → [Role B] → event.b → [Role C] → LOOP_COMPLETE
↓
event.rejected → [Role A]
Constraints to validate:
- Each trigger maps to exactly ONE hat (no ambiguous routing)
task.startandtask.resumeare RESERVED (never use as triggers)- Every hat must publish at least one event
- Chain must eventually reach LOOP_COMPLETE
Phase 3: Generate Preset
Create the YAML file with these sections:
# <Preset Name>
# Pattern: <Architecture Pattern>
# <One-line description>
#
# Usage:
# ralph run --config presets/<name>.yml --prompt "<example prompt>"
event_loop:
starting_event: "<first.event>" # Ralph publishes this
hats:
hat_key:
name: "<Emoji> Display Name"
description: "<Short description of the hat's purpose>"
triggers: ["event.triggers.this"]
publishes: ["event.this.publishes", "alternate.event"]
default_publishes: "event.this.publishes"
instructions: |
## <HAT NAME> MODE
<Clear role definition - what this hat does>
### Process
1. <Step one>
2. <Step two>
3. Publish appropriate event
### Event Format
```
<event topic="event.name">
key: value
</event>
```
### DON'T
- <Common mistake to avoid>
- <Another mistake>
Schema Reference
Required Top-Level Fields
| Field | Description |
|---|---|
event_loop.starting_event |
First event Ralph publishes |
Hat Definition Fields
| Field | Required | Description |
|---|---|---|
name |
Yes | Display name with optional emoji (e.g., "🔍 Analyzer") |
description |
Yes | Short description of the hat's purpose (one sentence) |
triggers |
Yes | Events this hat responds to (list) |
publishes |
Yes | Events this hat can emit (list) |
default_publishes |
Recommended | Fallback event if hat forgets to publish |
instructions |
Yes | Role-specific prompt (use | for multiline) |
Fields That DON'T Exist
Never use these—they're not in the schema:
emoji(put emoji innameinstead)system_prompt(useinstructions)subscriptions/publications(usetriggers/publishes)
Event Naming Conventions
<phase>.ready / <phase>.done # Phase transitions
<thing>.approved / <thing>.rejected # Review gates
<noun>.found / <noun>.missing # Discovery events
<action>.request / <action>.complete # Request-response
Examples: analysis.complete, review.approved, build.blocked, spec.rejected
Validation Checklist
Before finalizing the preset, verify:
- [ ] Each trigger maps to exactly ONE hat
- [ ] No hat uses
task.startortask.resumeas triggers - [ ] Every hat has
name,description,triggers,publishes, andinstructions - [ ]
default_publishesis set for hats with multiple publish options - [ ] Event chain can reach LOOP_COMPLETE
- [ ] No orphan events that never get handled (warning only)
- [ ] Instructions include role definition, process steps, event format, and DON'Ts
Output Location
Save generated presets to: presets/<name>.yml
For minimal/embedded presets: presets/minimal/<name>.yml
Testing the Preset
After generation, test with:
# Dry run to validate config parsing
cargo run --bin ralph -- run -c presets/<name>.yml -p "test prompt" --dry-run
# Run smoke tests
cargo test -p ralph-core smoke_runner
Use /evaluate-presets for comprehensive validation.
Example Conversation
User: I want a preset for doing code reviews with a security focus.
Assistant: I'll help create a security-focused code review preset. Let me ask a few questions:
-
Review depth: Should this be a quick scan or thorough analysis?
-
Roles needed: I'm thinking:
- Security Analyst (finds vulnerabilities)
- Code Reviewer (checks logic/style)
- Summarizer (creates final report)
Does this cover your needs, or should we add/remove roles?
-
Iteration: If issues are found, should the code be fixed, or just reported?
User: Thorough analysis, those roles work, just report issues don't fix.
Assistant: Here's the event flow I'm designing:
task.start → [Security Analyst] → security.complete
↓
→ [Code Reviewer] → review.complete
↓
→ [Summarizer] → LOOP_COMPLETE
Let me generate the preset...
[Generates YAML with three hats following the schema]
Common Patterns Reference
Pipeline (Sequential)
A → B → C → done
Use for: analysis workflows, document processing
Critic-Actor (Review Loop)
Actor → Critic → approved/rejected
↓
rejected → Actor (retry)
Use for: code review, quality gates
Supervisor-Worker
Supervisor → worker.task → Worker → work.done → Supervisor
Use for: complex task decomposition
Scientific Method
Observe → Hypothesize → Test → confirmed/rejected
↓
rejected → Observe
Use for: debugging, investigation
04 同仓库更多 Skills
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.
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 <subcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir/UltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).
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 <subcommand>). 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/UltraHonk zero-knowledge proofs.
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).
moldium
Post and manage content on the Moldium blog platform. Triggered by "post to Moldium", "write a blog post", "publish an article", etc.
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/category/interest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http://weakaccept.top:8000/.