metadata
Skill1 starsChanged 37 days agoMITView on GitHub
Use when adding, normalizing, or fixing YAML frontmatter in Cooklang .cook recipes or .menu plans (title, tags, source, servings/yield, times, diet, locale, images), including converting old >> metadata lines and bulk metadata changes across a library.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- machina-sports/sports-skillstheir own version, first seen Nov 5, 2026
- DataWithBaraa/claude-code-data-engineering-skillstheir own version, first seen Nov 1, 2026
- cooklang/cooklang-skillsword for word, first seen Oct 13, 2026
- msrv-tech/skillstheir own version, first seen Oct 2, 2026
Other versions4 projects use a version of this.
Word for word · 1
- cooklang/cooklang-skills★ 9100% same
Edited · 0
None found.
Wrote their own version · 3
- machina-sports/sports-skills★ 266same name
- DataWithBaraa/claude-code-data-engineering-skills★ 84same name
- msrv-tech/skills★ 60same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- cooklang-editingSkill
- cooklang-validationSkill
- export-recipeSkill
- meal-planningSkill
- nutrition-goalsSkill
- nutrition-reportsSkill
- organize-collectionSkill
- pantrySkill
- recipe-importSkill
- recipe-searchSkill
- report-authoringSkill
- scale-recipeSkill
- shopping-listSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use when adding, normalizing, or fixing recipe/menu metadata (YAML frontmatter): titles, tags, source/author, servings/yield, times, diet, …
- Very specific: line 55
Keep servings/yield accurate — reason: they drive recipe scaling and any shopping-list or menu math built on top.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
Skill: metadata
Needs the Cook MCP server (tools like read_recipe and write_recipe). If these tools are missing, the Cook MCP server isn't connected: if you installed the cooklang plugin or extension, check that its cook server is running (e.g. /mcp) or reinstall it; otherwise add it from https://github.com/cook-md/cook-mcp. Do not rewrite files without them.
Use when adding, normalizing, or fixing recipe/menu metadata (YAML frontmatter): titles, tags, source/author, servings/yield, times, diet, locale, images, or bulk metadata changes across a library.
This skill owns all metadata guidance. The cooklang-editing and meal-planning skills defer metadata/frontmatter work to here.
Hard rule
Metadata is YAML frontmatter between --- markers at the very start of the file. NEVER use the old >> metadata lines — reason: they are removed from the language; only frontmatter is supported, and write_recipe refuses them. If a file still has them, convert them to frontmatter keys as part of the edit.
Workflow
Changing metadata — tags, cuisine, source, any frontmatter key — on one file or many:
- Pick the targets. Use
search_recipes(tag, or words) orlist_recipes(dirfor a folder) rather than reading the whole library. For a rule like "everything in Desserts/", the folder listing is the selection. - For each file:
read_recipe, change only the frontmatter, and keep the recipe body byte-for-byte. Match the file's existing key names, casing, order and tag style; add a frontmatter block if the file has none; never duplicate a tag. - Save each file with
write_recipe(.cook) orwrite_menu(.menu), sending the full file content — there is no metadata-only write. - More than about 10 files → tell the user how many files you will touch and get a yes first; every write replaces a real file.
- Tell the user what you changed, in which files, and name any files you skipped and why.
For a brand-new file, the frontmatter is part of the content you save with write_recipe.
Canonical metadata fields
| Key (and synonyms) | Purpose | Example |
title | Recipe title. | Uzbek Manti |
source, source.name | Where it came from (URL or text). | https://example.org/recipe, mums |
source.url | URL when the nested form is used. | https://example.org/recipe |
author, source.author | Recipe author. | John Doe |
servings, serves, yield | People/amount. Leading number drives scaling; the rest shows as units. | 2, 15 cups worth |
course, category | Meal category or course. | dinner |
locale | ISO 639 language, optional _ then ISO 3166 country. Used for spelling and pluralisation. | en_GB, fr |
time, time required, duration | Total prep + cook time. Prefer HhMm. | 1h30m |
prep time, time.prep | Prep only. | 2 hour 30 min |
cook time, time.cook | Cooking only. | 10 minutes |
difficulty | Difficulty level. | easy |
cuisine | Cuisine. | French |
diet | Dietary suitability; string or array. | gluten-free, [vegan, halal] |
tags | Descriptive tags (array). | [baking, summer] |
image, images, picture, pictures | Image URL, or array of URLs. | https://example.org/img.jpg |
description, introduction | Notes about the recipe. | Traditional Uzbek dish… |
Rules
- Frontmatter goes at the very top of the file, before any step or section.
- Match the file's existing conventions (key spelling, casing) — reason: a file that mixes
servesandservingsis harder to maintain. - Keep
servings/yieldaccurate — reason: they drive recipe scaling and any shopping-list or menu math built on top. search_recipeswithtagmatches the frontmattertagslist, so consistent tags make the library searchable.- Touch only the files the task names.
Do not skip the care
| Excuse | Rebuttal |
| "It's only metadata, I'll rewrite the body from memory." | write_recipe saves exactly what you send. Copy the body from read_recipe's source unchanged. |
| "The metadata edit is tiny, I'll say it's done." | Say it's done after write_recipe succeeds, and name the file. |
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.