recipe-export-flow

Export a live agent network's culture into a validated, shareable recipe bundle.

692|60|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Lingtai-AI/lingtai --skill recipe-export-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recipe-export-flow
Source: https://github.com/Lingtai-AI/lingtai/tree/main/tui/internal/preset/skills/lingtai-recipe/reference/export-recipe
Command: npx skills add https://github.com/Lingtai-AI/lingtai --skill recipe-export-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capturing what makes a long-lived LingTai agent network distinctive and packaging it for others is error-prone: agents confuse the network's distilled culture with the recipe that originally seeded it, writes silently fail, and bundles fail validation. This Skill guides the full export workflow so the resulting recipe bundle is valid, safe to publish, and faithful to how the network actually behaves.

Core Features & Use Cases

  • Scope Disambiguation: Distinguishes the three recipe-shaped artifacts (inner-network distillation, the project's own .recipe/, and the TUI snapshot) before authoring anything.
  • Human-in-the-Loop Authoring: Collects recipe id, name, description, layers, library, and languages via email, then writes recipe.json, greet.md, comment.md, and optional library skills in one pass.
  • Validation and Safe Publishing: Runs validate_recipe.py, performs a sensitivity sweep for private names or unreleased details, then initializes git and optionally pushes to GitHub.
  • Use Case: After weeks of running a research network, distill its delegation rules, communication norms, and custom skills into a scholar-distiller bundle that colleagues can clone and apply with /setup.

Quick Start

Export this network's culture as a recipe bundle named scholar-distiller, validate it, and prepare it for publishing to GitHub.

Frequently Asked Questions about recipe-export-flow

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

FAQPage Schema
How do I export a LingTai recipe from an existing agent network?

Reflect on the network's current behavior in `.lingtai/`, collect metadata (id, name, layers, library) from the human via email, author the bundle under `$HOME/lingtai-agora/recipes/<id>/`, then run `validate_recipe.py` and commit with git.

What is the difference between a network recipe and a project's .recipe directory?

A network recipe distills how the agents in `.lingtai/` actually behave now, while the project-root `.recipe/` is the bundle originally applied to seed the project. Republishing the seed is a copy job; distilling the network's culture requires fresh authoring.

What files does a valid recipe bundle require?

The minimum is `.recipe/recipe.json` at the bundle root. Optional layers include `greet/greet.md`, `comment/comment.md`, `covenant/covenant.md`, `procedures/procedures.md`, locale variants, and a library sibling folder of skills.

Why does my recipe library register zero skills after export?

The scanner only registers skills in direct-child subdirectories of the library folder. A `SKILL.md` placed flat at the library root is ignored, so nest each skill in its own subdirectory, even for single-skill libraries.

How do I validate a recipe bundle before publishing?

Run `python3 $HOME/.lingtai-tui/utilities/lingtai-recipe/scripts/validate_recipe.py <bundle-dir>`. Exit code 0 means the bundle is structurally valid; fix reported errors and re-run until clean.

Can a recipe bundle reproduce another network's state or history?

No. A recipe is a seed that shapes behavior only; it ships no `.lingtai/` snapshot, history, or data. Recipients grow a fresh network whose agents are shaped by the recipe but start without the original network's state.