hatch3r-recipe

Create and execute validated YAML workflow recipes for hatch3r agents.

26|4|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/hatch3r/hatch3r --skill hatch3r-recipe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hatch3r-recipe
Source: https://github.com/hatch3r/hatch3r/tree/main/skills/hatch3r-recipe
Command: npx skills add https://github.com/hatch3r/hatch3r --skill hatch3r-recipe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Recipes standardize repeatable hatch3r workflows so teams can run complex multi-step agent plans safely and consistently instead of re-deriving the same sequence each time.

Core Features & Use Cases

  • Recipe creation & schema-driven design: Define a YAML recipe with variables, step DAGs, checkpoints, and completion messaging for predictable orchestration.
  • Dependency-aware execution planning: Model depends_on and parallel_with relationships to build an execution graph and run safe parallel substeps when appropriate.
  • Dry-run validation & recovery workflow: Validate prerequisites, detect cycles, catch missing references, and support resume after failures to reduce trial-and-error.
  • Project or global recipe scope: Target recipes to .hatch3r/recipes/ (project) or ~/.hatch3r/recipes/ (user-level) depending on reuse needs.

Quick Start

Create a recipe YAML in .hatch3r/recipes/ and run it in dry-run mode to confirm the DAG, variables, and referenced commands/skills before executing for real.

Frequently Asked Questions about hatch3r-recipe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create repeatable YAML workflow recipes for agent orchestration?

You create repeatable agent workflows by defining a YAML recipe with variables, step DAGs, and checkpoints. This standardizes multi-step agent plans so teams can execute complex sequences safely and consistently without re-deriving the process each time.

What's the best way to validate a dependency graph before running a workflow?

The best way to validate a dependency graph is using dry-run mode. Dry-run execution validates prerequisites, detects cycles, catches missing references, and confirms the DAG and variables before you execute the workflow for real.

Can I resume workflow execution after a step failure?

Yes, you can resume workflow execution after failures. The recipe orchestration supports a recovery workflow with checkpoint guardrails, allowing you to resume safely from the last valid state instead of restarting the entire sequence.

How do dependency-aware execution graphs handle parallel steps?

Dependency-aware execution graphs model depends_on and parallel_with relationships to build an execution sequence. This allows the orchestrator to run safe parallel substeps when appropriate based on the constructed dependency graph.

Should I store workflow recipes at the project level or user level?

You should store workflow recipes at the project level in .hatch3r/recipes/ for project-specific automation, or at the user level in ~/.hatch3r/recipes/ for global reuse across multiple projects depending on your needs.