Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingtai-ai/recipe-format-reference
Nested lingtai-recipe reference for authoring and validating recipe bundles: bundle structure, .recipe/recipe.json schema, behavioral layers, library sibling mechanics, locale fallback, validator checks, hand-authored recipes, testing, and publishing.
Passed 19 of 23 test cases with the skill, and 5 of 23 without it.
and 22 more in the full report
15 fixed5 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
When a recipe bundle with `library_name: "velli"` is applied to a project, how is the library folder path registered inside each agent's configuration relative to its `.lingtai/<agent>/` directory?
| Checked | Without skill | With skill |
|---|---|---|
| Specify the relative path `"../../velli"` added to the agent skills paths configuration. | Missed | 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 authoring reference of the lingtai-recipe skill. For overview of all recipe-related flows, read ../../SKILL.md. For the recipe export flow, read ../export-recipe/SKILL.md.
A recipe bundle is a directory that ships two kinds of content, side-by-side:
.recipe/ dotfolder containing the LingTai-facing behavioral layer (greet, comment, covenant, procedures) and the manifest (recipe.json).recipe.json#library_name) containing framework-agnostic skills — drop-in for any agent framework, not just LingTai.The bundle is the shareable artifact. When the TUI applies a recipe, it copies the bundle into the project root; the project then becomes self-contained — every path reference in init.json resolves within the project directory.
my-recipe-bundle/
├── .recipe/ # required — LingTai behavioral layer
│ ├── recipe.json # required — manifest (id, name, description, library_name, …)
│ │ # SINGLE CANONICAL FILE. NEVER localized.
│ │ # Locale variants of recipe.json are FORBIDDEN —
│ │ # they silently drop critical fields like library_name.
│ ├── greet/ # optional — first-contact message
│ │ ├── greet.md # default version
│ │ └── <lang>/greet.md # optional locale variants (en, zh, wen)
│ ├── comment/ # optional — system-prompt constraints
│ │ ├── comment.md
│ │ └── <lang>/comment.md
│ ├── covenant/ # optional — covenant override
│ │ ├── covenant.md
│ │ └── <lang>/covenant.md
│ └── procedures/ # optional — procedures override
│ ├── procedures.md
│ └── <lang>/procedures.md
└── <library_name>/ # optional — framework-agnostic skills
├── <skill-a>/
│ └── SKILL.md
└── <skill-b>/
├── SKILL.md
├── scripts/
test cases passed, vs 5 / 23 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.