什么是 食谱？

食谱技能旨在将您的 AI 助手转变为先进的烹饪助手。通过利用 Openclaw Skills，用户可以汇总来自不同来源（包括网页 URL、语音描述和手写笔记照片）的食谱，并将其转换为标准化的、人类可读的 Markdown 格式。该系统通过管理本地工作区 ~/recipes/ 而不是依赖专有的、臃肿的食谱管理应用程序，优先考虑数据所有权和简洁性。

除了简单的存储，此技能还专注于烹饪的实用性。它提供遵循化学比例的智能食材缩放，通过集中索引组织厨房工作流程，并随您的需求而进化。从提取博客文章中“无废话”的精华到保存祖母的手写计量，此技能确保您的烹饪知识井然有序、可搜索且具有可操作性。

下载入口:https://github.com/openclaw/skills/tree/main/skills/ivangdavila/recipe

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

食谱 应用场景

• 通过将原始照片与结构化 Markdown 版本链接，数字化手写家传食谱。
• 从广告密集的烹饪网站提取纯净的食谱数据，消除干扰。
• 为一周的用餐规划自动生成合并的购物清单。
• 根据特定食材（如“鹰嘴豆”或“鸡肉”）搜索用餐灵感。
• 为大型晚宴缩放食谱，同时处理酵母和泡打粉等非线性增长的食材。

1. 该技能在用户主目录中初始化一个结构化文件系统，包含主菜、配菜、甜点和基础款的指定文件夹。
2. 当提供食谱来源时，助手会将数据解析为带有 YAML 前置属性（用于准备时间、份数等元数据）的 Markdown 文件。
3. 助手维护一个主 index.md 文件，作为所有 Openclaw Skills 食谱条目的数据库，以便按标签或菜系进行快速过滤。
4. 对于用餐规划，助手会选择多个食谱并将它们的食材汇总到一份购物清单中。
5. 该技能使用逻辑对食材进行去重，并按商店区域（蔬菜、乳制品、储藏室）进行分组，以便高效购物。

食谱 配置指南

要在您的 Openclaw Skills 环境中开始使用此技能，请确保您的助手拥有文件系统权限，并运行以下命令初始化工作区：

mkdir -p ~/recipes/{mains,sides,desserts,basics,meal-plans}
touch ~/recipes/index.md

目录准备就绪后，只需向助手分享食谱的 URL 或照片即可开始录入过程。

食谱 数据架构与分类体系

该技能使用具有特定元数据要求的扁平文件 Markdown 结构组织信息：

name: Recipes
description: Build a personal recipe collection with ingredients, scaling, and meal planning.
metadata: {"clawdbot":{"emoji":"??","os":["linux","darwin","win32"]}}

Core Behavior

• 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

When User Shares a Recipe

• 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

Recipe File Structure

• 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

Key Fields

• 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

Ingredient Format

• 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

Scaling

• 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"

Progressive Enhancement

• 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

Folder Structure

~/recipes/
├── mains/
├── sides/
├── desserts/
├── basics/          # sauces, stocks, staples
├── index.md         # master list with tags
└── meal-plans/      # weekly plans

Searching and Filtering

• 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

Meal Planning

• 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

Shopping List Generation

• 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)

What To Capture From URLs

• Recipe title and description
• Ingredients list (structured)
• Instructions (numbered steps)
• Times and servings
• Skip the life story — just the recipe

Notes and Variations

• "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

What NOT To Suggest

• 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

Family Recipe Preservation

• 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"