Recipes

A recipe is an agent in a file: who it is, how it talks, what it does and does not do, and which channels it works on. Drop it in the creator and you get an agent; export it from an existing agent and take it to another account or a repo.

The format

It is the Goose recipe format, with an x-ghosty section for what is ours:

version: "1.0.0"title: Soporte al clientedescription: Resuelve dudas y problemas frecuentes con la documentación del negocio.instructions: |  Eres el agente de soporte del negocio. Resuelves dudas de uso, problemas frecuentes y  preguntas sobre cuentas y pagos.
  ## Cómo hablas  Español de México, claro y paciente. Primero confirmas que entendiste el problema en una  frase; luego das los pasos, numerados y cortos.
  ## Qué NO haces  - No adivinas: si la documentación no lo cubre, lo dices y escalas.  - No pides contraseñas ni datos de tarjeta.x-ghosty:  engine: claude  channels: { teams: true }

No secrets: a recipe never carries keys or tokens.

The eight house recipes

In New agent → Plantilla:

Picking one fills the form and the identity is editable before creating.

Upload yours

In New agent → Plantilla, drop the .yaml in the zone at the bottom (or click to pick it). If a field is wrong, the creator says so before creating. Ask your coding agent for the recipe with the prompt above: it knows the format.

Export an agent's recipe

On any agent's card, Descargar receta returns its recipe.yaml with name, description, identity, engine and channels, without secrets. Use it to copy an agent to another account, version it in a repo or hand it to a client.

What a recipe is not

Knowledge files, skills and MCP servers do not travel in the recipe: they belong to the agent's machine and are given through the configuration API.