Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingtai-ai/lingtai-recipe
Menu manual (not a tool) for everything recipe-related in LingTai. A **recipe** is the named payload that shapes an orchestrator's greeting, ongoing behaviour, and shipped library; every LingTai project uses one (selected at `/setup` time, inherited from a clone, or auto-discovered when a project already has `.recipe/` at its root). Routes to two sub-guides — `reference/recipe-format/SKILL.md` (read first when authoring or customising) and `reference/export-recipe/SKILL.md` (shipping the methodo
Passed 18 of 20 test cases with the skill, and 5 of 20 without it.
and 13 more in the full report
14 fixed6 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Where can we find the snapshot copy of the recipe bundle captured by the system when the workspace was originally configured?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies .lingtai/.tui-asset/.recipe/ as the snapshot copy captured during initial setup | Missed | Passed |
The instructions your model reads when the skill loads.
Bundle root convention: The bundle root is the directory that contains
.recipe/at its top level (alongside the library folder). When pointing the TUI or any tool at a recipe, pass this directory, not.recipe/itself and not a parent of it. For recipes published vialingtai-recipeskill, this is$HOME/lingtai-agora/recipes/<id>/.
A recipe bundle is a required .recipe/ behavioral layer (recipe.json manifest plus optional greet/, comment/, covenant/, procedures/ layer dirs) beside an optional framework-agnostic skill library named by recipe.json#library_name. reference/recipe-format/SKILL.md is authoritative for that structure; this router does not restate it.
Every LingTai project uses a recipe — selected during /setup, inherited from a cloned network, or auto-discovered when a project already has .recipe/ at its root.
This skill is the one place to look for anything recipe-related. Pick the sub-file that matches what you're doing, then read it in full before acting.
lingtai-recipe owns these nested references. They are parent-owned drill-down
files, not standalone top-level skills.
- name: recipe-format-reference
location: reference/recipe-format/SKILL.md
description: |
Authoritative recipe bundle format reference: directory structure,
`recipe.json` schema, optional behavioral layers, locale fallback rules,
library sibling mechanics, validator contract, and custom recipe testing.
- name: recipe-export-flow
location: reference/export-recipe/SKILL.md
description: |
Standalone recipe-export procedure for distilling a live network's culture
into a portable recipe bundle: scope disambiguation, metadata collection,
authoring, validation, sensitivity sweep, git initialization, and handoff.
| If you need to... | Read |
|---|---|
Understand or author a recipe bundle: structure, recipe.json, optional layers, locale fallback, library sibling, validation, testing | reference/recipe-format/SKILL.md |
Export a standalone recipe: distill culture into optional greet/comment/covenant/procedures plus optional skill library; no agents, no mailboxes | reference/export-recipe/SKILL.md |
A single project directory can hold up to three recipe-shaped artifacts at once, and they are NOT interchangeable. Identify which the human means before going further:
test cases passed, vs 5 / 20 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.