cooklang-skills
AGENTS.md9 starsChanged 38 days agoMITView on GitHub
This folder may hold recipes written in Cooklang, a plain-text recipe format. The cook MCP server (npx -y @cookmd/mcp@0.2.3) reads, searches, validates and writes these files. Prefer its tools over editing by hand or doing arithmetic yourself: The recipe folder is COOK_RECIPES_DIR, else the workspace folder the client reports, else the folder the server was started in (never /, the home folder or a plugin install folder). If the tools say no recipe folder is set, ask the user for…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository14 other files it gives its agents.
- cooklang-editingSkill
- cooklang-validationSkill
- export-recipeSkill
- meal-planningSkill
- metadataSkill
- nutrition-goalsSkill
- nutrition-reportsSkill
- organize-collectionSkill
- pantrySkill
- recipe-importSkill
- recipe-searchSkill
- report-authoringSkill
- scale-recipeSkill
- shopping-listSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
read and find: list_recipes, read_recipe (with scaling), search_recipes
- Very specific: line 15
check and save: validate, then write_recipe / write_menu / write_config (writes are validated and stay inside the recipe folder)
- Very specific: line 17
import and report: import_recipe, render_report
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cooklang
This folder may hold recipes written in Cooklang, a plain-text recipe format.
.cookfiles are recipes. Ingredients are@name{qty%unit}, cookware#name{}, timers~{qty%unit}, sections= Name, notes> text..menufiles are meal plans that reference recipes.config/aisle.confgroups shopping-list items by store aisle;config/pantry.confis the pantry inventory.- Metadata (title, servings, tags, times, source) is YAML frontmatter between
---lines at the top of the file. Never write the deprecated>>metadata lines; convert any you find to frontmatter.
Use the Cook MCP server
The cook MCP server (npx -y @cookmd/mcp@0.2.3) reads, searches, validates and writes these files. Prefer its tools over editing by hand or doing arithmetic yourself:
- read and find:
list_recipes,read_recipe(with scaling),search_recipes - check and save:
validate, thenwrite_recipe/write_menu/write_config(writes are validated and stay inside the recipe folder) - plan and shop:
shopping_list(merges, groups by aisle, subtracts the pantry),pantry_* - import and report:
import_recipe,render_report - nutrition (
get_nutrition,aggregate_nutrition, ...) and photo or social-link import need a cook.md login on Cook Basic or Pro;loginandauth_statushandle that. Never estimate nutrition from memory.
The recipe folder is COOK_RECIPES_DIR, else the workspace folder the client reports, else the folder the server was started in (never /, the home folder or a plugin install folder). If the tools say no recipe folder is set, ask the user for the path and have them set COOK_RECIPES_DIR in the server config. If the cook tools are missing, tell the user to add the server (see https://github.com/cooklang/cooklang-skills).
Skills
Each task below has a skill with a step-by-step guide (installed with the plugin or extension; the source is skills/<name>/SKILL.md in this repo). Use the matching skill before starting:
| Skill | Use it for |
cooklang-editing | Write a new recipe or edit and fix a .cook file |
cooklang-validation | Check recipes, a folder or the whole collection for errors |
metadata | Add or fix YAML frontmatter, including bulk changes |
recipe-import | Import a recipe from a URL, photos or pasted text |
recipe-search | Find recipes by ingredient, tag, cuisine or a remembered phrase |
scale-recipe | Show a recipe for more or fewer servings |
export-recipe | Turn a recipe into Markdown, JSON, plain text or HTML |
organize-collection | Folder layout, metadata audit, aisle and pantry config |
meal-planning | Build or edit a .menu meal plan |
shopping-list | Shopping lists from recipes or plans |
pantry | Stock, expiry, low items; what can I cook now |
report-authoring | Custom Jinja reports with render_report |
nutrition-reports | Nutrition evaluation and screening (Cook Basic or Pro) |
nutrition-goals | Change a recipe or plan to hit nutrition targets (Cook Basic or Pro) |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.