Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingtai-ai/recipe-export-flow
Nested lingtai-recipe reference for exporting a standalone recipe bundle from a live network or methodology: scope disambiguation, human-in-the-loop metadata collection, bundle authoring, validation, git initialization, and handoff.
Passed 8 of 15 test cases with the skill, and 3 of 15 without it.
and 6 more in the full report
8 fixed4 passed either way9 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to set up the export directory for my new recipe 'data-cleaner'. Should I use ~/lingtai-agora/recipes/data-cleaner directly in file tool calls or resolve environment variables first?
| Checked | Without skill | With skill |
|---|---|---|
| Resolves $HOME via echo $HOME before building absolute file paths. | Missed | Passed |
| Avoids using ~ in file tool arguments. | Passed | Passed |
The instructions your model reads when the skill loads.
Nested lingtai-recipe reference. Read this after the top-level router sends you here.
This is the recipe-export sub-guide of the lingtai-recipe skill. For an overview of all recipe-related flows, read ../../SKILL.md.
Prerequisites: Read ../recipe-format/SKILL.md first — it defines the bundle shape, recipe.json schema, the four behavioral layers (all optional), the library sibling, and how the validator enforces all of it. This sub-guide assumes you understand all of that.
A recipe is the culture of a network, distilled into a portable seed. Your job is to help the human reflect on their network's culture and package the parts worth sharing. An exported recipe is a bundle directory — a git repo the recipient clones and points /setup at.
../../SKILL.md ("Disambiguate scope BEFORE picking a sub-guide") defines the three recipe-shaped artifacts a project can hold at once. Confirm scope with the human before authoring anything, then apply the export-side rule for each:
A recipe distilled from the inner network (the agents in .lingtai/) — the default, and what this sub-guide assumes. You write a NEW .recipe/ capturing what makes this network distinctive.
The outer project's own .recipe/ at the project root (sibling of .lingtai/). If the human says "re-export the recipe," they may mean republish this existing bundle, NOT write a new one. Ask. Republishing is mostly a copy job (copy <project>/.recipe/ and the matching <project>/<library_name>/ sibling into $HOME/lingtai-agora/recipes/<id>/, then jump to Step 4 to validate). Distilling a fresh recipe is what the rest of this sub-guide covers.
The applied-recipe snapshot at .lingtai/.tui-asset/.recipe/ — a TUI-managed copy of #2, useful as evidence of what behavior is currently in force. Not a separate artifact to ship: if the human wants what's in there, they almost certainly mean #2.
The most common failure mode in a project that was itself seeded from a recipe (e.g., a methodology recipe applied to produce a domain network): the agent confuses #2 with #1 and ends up republishing the seeding methodology instead of distilling the network's actual culture. If the project has both a .lingtai/ and its own .recipe/ at the root, ASK the human which scope they want before proceeding.
A recipe bundle is the shareable artifact the TUI copies into a project on selection. Minimum shape:
<bundle-root>/ # the repo root the recipient clones
└── .recipe/
└── recipe.json # manifest (id, name, description, …)
Everything else is optional, and ../recipe-format/SKILL.md ("Bundle Directory Structure") is the authoritative layout. Typical bundles add greet/greet.md (first-contact) and comment/comment.md (ongoing behavioral constraints), their <lang>/ variants, occasionally covenant/covenant.md or procedures/procedures.md, and a <library_name>/ sibling of framework-agnostic skills. Export adds one file the format reference does not: an optional README.md at the bundle root, for GitHub display.
A recipe ships no .lingtai/ snapshot — just the seed. The garden grows fresh in each new project that applies the recipe.
Use the email tool for every message to the human. Never rely on text output.
test cases passed, vs 3 / 15 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.