Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Build a personal recipe collection with ingredients, scaling, and meal planning.
Build a personal recipe collection with ingredients, scaling, and meal planning.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
User shares a recipe โ capture in standard format, save to collection User asks "what can I make with X" โ search by ingredient User plans meals โ help organize week and generate shopping list Create ~/recipes/ as workspace
URL โ fetch and extract into standard format Photo of recipe โ extract text, structure it Voice/text description โ format into recipe structure Handwritten family recipe โ preserve original, add structured version
One Markdown file per recipe: chicken-tikka-masala.md Frontmatter: prep_time, cook_time, servings, tags, source Sections: ingredients, instructions, notes Keep readable โ someone should cook from this file
Title and brief description Prep time, cook time, total time Servings (base for scaling) Ingredients with quantities and units Step-by-step instructions Tags: cuisine, meal-type, dietary, difficulty Source: URL, book, or "family recipe" Notes: substitutions, tips, variations tried
Quantity, unit, ingredient, prep: "2 cups chicken, diced" Consistent units โ pick metric or imperial, stick with it Group by section if complex: "For the sauce:", "For the marinade:" Note optional ingredients clearly
Store base servings in frontmatter Calculate scaled quantities on request Flag ingredients that don't scale linearly (salt, yeast, baking powder) Round to practical measurements โ no "0.37 cups"
Week 1: dump recipes as they come, minimal formatting Week 2: standardize format, add tags Week 3: build index by cuisine/meal type Month 2: meal planning and shopping lists Month 3: ingredient inventory integration
~/recipes/ โโโ mains/ โโโ sides/ โโโ desserts/ โโโ basics/ # sauces, stocks, staples โโโ index.md # master list with tags โโโ meal-plans/ # weekly plans
By ingredient: "recipes with chickpeas" By tag: "quick weeknight", "vegetarian", "mexican" By time: "under 30 minutes" Favorites: tag or star system for go-to recipes
Weekly plan: 7 dinners, optional lunches/breakfasts Balance variety โ not three pasta dishes in a row Consider ingredient overlap โ buy once, use twice Generate combined shopping list from plan
Aggregate ingredients across selected recipes Combine same ingredients: 2 cups + 1 cup = 3 cups Group by store section: produce, dairy, pantry Exclude pantry staples user always has (configurable)
Recipe title and description Ingredients list (structured) Instructions (numbered steps) Times and servings Skip the life story โ just the recipe
"Made this 2024-03-15, added more garlic, family loved it" Track modifications that worked Rate recipes after making them Flag recipes never actually made vs tested
Complex recipe management app โ files work fine Nutrition calculation โ too complex, use dedicated tool if needed Automated meal planning โ user knows their preferences Social features โ this is personal collection
Scan or photograph original handwritten recipes Link image in the markdown file Keep original measurements even if odd ("coffee cup of flour") Note the source: "Grandma's recipe, circa 1960"
Writing, remixing, publishing, visual generation, and marketing content production.
Largest current source with strong distribution and engagement signals.