agentleFS
brainsforaibrainsforai/brains-skills/skills/lobes/recipes/skill.md

recipes

Skill1 starsChanged 5 months agoMITView on GitHub

Skill ID: recipes Version: 1.0.0 Domains: personal, food Install: fetch this file and follow the "How to use" section Read this file, then set up a recipes project in the user's Brains knowledge base using the template and instructions below. Create the project structure, initialize the instructions page, and offer to add the first recipe. Filing — important: This lobe is a note template only; it does not choose a folder. Before creating pages, check whether a hippocampus skill (PARA,…

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. 0 are common, 8 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read this file, then set up a recipes project in the user's Brains knowledge base using the template and instructions below.

    line 10
  2. Very specific:

    When asked for dinner ideas, filter by meal_type: dinner and sort by rating if available.

    line 23
  3. Very specific:

    When asked for a quick meal, filter by total time under a threshold (default 30 minutes).

    line 24
  4. Very specific:

    When asked for vegetarian / vegan / gluten-free options, filter by dietary_tags.

    line 25
  5. Distinctive:

    When asked to plan meals for a week, select recipes that: (1) cover the requested meal types, (2) avoid repetition of cuisine within 2 …

    line 28
  6. Distinctive:

    When planning meals, note which recipes can be batch-cooked together (same oven temp, same prep day).

    line 29
  7. Distinctive:

    When asked for a monthly rotation, group by cuisine and distribute to avoid two similar meals in the same week.

    line 30
  8. Distinctive:

    When asked for a shopping list for specific recipes, aggregate all ingredients across those recipes.

    line 33
  9. Distinctive:

    When asked to scale a recipe for a different number of servings, adjust all ingredient quantities proportionally.

    line 38
  10. Distinctive:

    When asked "what should I make tonight?", consider: any dietary constraints mentioned, what hasn't been cooked recently (if date-tracked), …

    line 41
  11. Distinctive:

    When asked for something similar to a specific recipe, find recipes with matching cuisine or overlapping key ingredients.

    line 42
  12. Very specific:

    If rating is missing, don't rank the recipe above or below others — list it without a rating.

    line 46
  13. Very specific:

    If prep_time or cook_time is missing, don't estimate — say "time not recorded."

    line 47
  14. Very specific:

    If dietary_tags is empty, don't assume the recipe is free of any allergens.

    line 48
  15. Very specific:

    Use this template when creating a new recipe page.

    line 60

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
skill.md

Recipes Skill

Skill ID: recipes
Version: 1.0.0
Domains: personal, food
Install: fetch this file and follow the "How to use" section

How to use

Read this file, then set up a recipes project in the user's Brains knowledge base using the template and instructions below. Create the project structure, initialize the instructions page, and offer to add the first recipe.

Filing — important: This lobe is a note template only; it does not choose a folder. Before creating pages, check whether a hippocampus skill (PARA, Johnny.Decimal, Zettelkasten, or Mind Palace) is active. If one is, ask it where each page belongs and record that path in the page's filed_at field. If no structure is active, fall back to a flat recipes/ folder. Never hardcode a location here.


Agent Instructions

You help the user get more value from their personal recipe database. Pages in this domain follow the Recipes template below: each page covers one recipe, with frontmatter (recipe_name, cuisine, meal_type, prep_time, cook_time, servings, dietary_tags, rating) and sections for ingredients, instructions, notes, variations, and pairings.

Core capabilities

Recipe discovery

  • When asked for dinner ideas, filter by meal_type: dinner and sort by rating if available. Return name, cuisine, and total time (prep + cook).
  • When asked for a quick meal, filter by total time under a threshold (default 30 minutes). Combine prep_time and cook_time.
  • When asked for vegetarian / vegan / gluten-free options, filter by dietary_tags. Return only recipes that match all specified tags.

Meal planning

  • When asked to plan meals for a week, select recipes that: (1) cover the requested meal types, (2) avoid repetition of cuisine within 2 days, (3) match any dietary constraints given.
  • When planning meals, note which recipes can be batch-cooked together (same oven temp, same prep day).
  • When asked for a monthly rotation, group by cuisine and distribute to avoid two similar meals in the same week.

Shopping lists

  • When asked for a shopping list for specific recipes, aggregate all ingredients across those recipes. Combine duplicate ingredients (e.g. "2 cups flour" + "1 cup flour" = "3 cups flour").
  • Group the shopping list by category: produce, proteins, dairy, pantry, spices.
  • Flag pantry staples (salt, oil, common spices) separately — the user may already have them.

Recipe scaling

  • When asked to scale a recipe for a different number of servings, adjust all ingredient quantities proportionally. Note ingredients that don't scale linearly (e.g. leavening agents in baking, seasoning should be adjusted to taste).

Recommendations

  • When asked "what should I make tonight?", consider: any dietary constraints mentioned, what hasn't been cooked recently (if date-tracked), and simplicity.
  • When asked for something similar to a specific recipe, find recipes with matching cuisine or overlapping key ingredients.

Handling incomplete data

  • If rating is missing, don't rank the recipe above or below others — list it without a rating.
  • If prep_time or cook_time is missing, don't estimate — say "time not recorded."
  • If dietary_tags is empty, don't assume the recipe is free of any allergens.

Output format

  • Recipe lists: name, cuisine, total time, rating. Keep it scannable.
  • Shopping lists: grouped by category, quantities summed.
  • Meal plans: day-by-day table or list with recipe name and meal type.

Page Template

Use this template when creating a new recipe page. This lobe defines the note shape only — it does not pick a folder. The active hippocampus skill decides where it is filed (recorded in filed_at); with no structure active, default to recipes/<recipe-name>.md.

---
file_type: recipes
filed_at: ""
# filed_at: path set by the active hippocampus skill — flat `recipes/` folder if no structure active
recipe_name: ""
cuisine: ""
# cuisine: italian | mexican | japanese | indian | american | mediterranean | other
meal_type: ""
# meal_type: breakfast | lunch | dinner | snack | dessert | drink
prep_time: 
# prep_time: minutes
cook_time: 
# cook_time: minutes
servings: 
difficulty: medium
# difficulty: easy | medium | hard
rating: 
# rating: 1–5
dietary_tags: []
# dietary_tags: vegetarian | vegan | gluten-free | dairy-free | nut-free | keto | paleo
source: ""
# source: cookbook name, URL, or "family recipe"
tags: []
---

## Ingredients

<!-- List all ingredients with amounts. Group by component if the recipe has multiple parts (e.g. sauce, filling, dough). -->

- 
- 
- 

## Instructions

<!-- Numbered steps. Each step should be one clear action. -->

1. 
2. 
3. 

## Notes

<!-- Substitutions, tips, common mistakes, make-ahead instructions, storage notes. -->

## Variations

<!-- Ways to adapt this recipe: different proteins, dietary swaps, seasonal ingredients. -->

## Pairings

<!-- What goes well with this? Side dishes, drinks, sauces. -->

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.