Docs / Recipes/ Creating Recipes

Creating Recipes

Write procedural recipes in CRHQ — define multi-step workflows with clear instructions and skill references.

Creating a recipe means writing a clear, step-by-step procedure that an agent can follow. Good recipes are specific, sequential, and reference the right skills.

Creating a New Recipe

  1. Go to Settings → Recipes
  2. Click Create Recipe
  3. Fill in the details:
FieldDescription
NameDescriptive name (e.g., "Weekly Sales Report", "Website Audit")
DescriptionSummary for search and discovery
ContentThe full procedural instructions (markdown)
ActiveToggle on/off — inactive recipes aren't available to agents
  1. Click Save

Writing Recipe Content

Recipe content follows a step-by-step structure:

# Weekly Sales Report

Generate a comprehensive weekly sales report and distribute it.

## Prerequisites
- Access to sales database (database-query skill)
- Slack integration (slack skill)
- Artifact display capability

## Steps

### 1. Gather Data
Use the database-query skill to pull:
- Total revenue for the past 7 days
- Revenue by product category
- Top 10 customers by spend
- Comparison to previous week

### 2. Analyze Trends
- Calculate week-over-week growth percentage
- Identify top-performing and declining categories
- Note any anomalies or significant changes

### 3. Create Report
Generate an HTML artifact with:
- Summary dashboard with key metrics
- Revenue trend chart
- Category breakdown table
- Notable highlights section

### 4. Distribute
- Post the report summary to #sales in Slack
- Include the artifact share link
- Tag @sales-team

## Error Handling
- If database is unreachable, report the error and retry once
- If Slack is down, save the report and note delivery failure

Version History

Recipes are versioned automatically — every save creates a new version. You can view history and restore previous versions just like with skills.

Tips

  • Be explicit about order — Number your steps clearly
  • Reference skills — Name the specific skills the agent should use
  • Include error handling — Define what to do when steps fail
  • Set quality gates — Add verification steps ("confirm the data looks correct before proceeding")
  • Keep it focused — One recipe per workflow; don't combine unrelated procedures