Submit a recipe

Contribute pinned Lathe inputs that can regenerate a CLI with its embedded Skill, catalog, and reviewable proof.

01

Shape the recipe

Keep source inputs small, pinned, and reviewable.

02

Generate proof

Catalog, Skill, build metadata, and smoke checks must derive from the recipe.

03

Open the PR

Submit the recipe as source of truth, with generated outputs treated as evidence.

Required shape

recipes/<name>/
  lathe.yaml
  cli.yaml
  specs/sources.yaml
  overlays/
  README.md

Rules

  • Submit reproducible recipes, not generated code as source.
  • Pin upstream specs in specs/sources.yaml.
  • Describe auth requirements in lathe.yaml and README.md.
  • Keep overlays focused on command names, grouping, summaries, aliases, and parameter help.
  • Add a smoke intent that proves catalog search works.

Generated evidence

Registry automation publishes macOS, Linux, and Windows CLI binaries with embedded Skills, catalog snapshots, build metadata, and static website data. Those outputs must remain reproducible from the recipe.

Reference recipe

Use recipes/daocloud-dce as the first real template for a multi-source API with auth and overlays.