recipe-scraping
Guidelines and standards for scraping recipes from external sources using automated tools.
安装与使用
请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。
查看来源 ↗使用指南技能说明
Recipe Scraping Guidelines
This document outlines the standards and procedures for scraping recipes from external sources using automated tools.
Table of Contents
Tool Usage
- Primary Tool: Use firecrawl-local MCP server for scraping recipe content from URLs.
-
Parameters: Use
formats: ["markdown"]andonlyMainContent: truefor clean extraction. - Multiple Pages: If a source links to individual recipes, crawl each recipe URL separately to get full details.
Organization
-
Directory Structure: Store scraped recipes in
phase0_flow/recipes/<site>/where<site>is the domain name with hyphens (e.g.,newsletter-ethanchlebowski-com). -
File Naming: Use kebab-case filenames based on the recipe title (e.g.,
steak-and-corn-tostada.md). - Grouping: Keep recipes from the same source together in their dedicated subdirectory.
Metadata Requirements
-
Source URL: Include the original source URL at the top of each recipe file in the format
Source: https://example.com/recipe-url. - Scraping Date: Optional: Include scraping date in ISO 8601 format if needed for tracking.
Content Formatting
- Attribution: Always include source attribution to respect original content creators.
-
Structure: Use standard markdown with
# Title,### Ingredients,### Instructions. - Ingredients: List ingredients in bullet points, grouped by component if applicable.
- Instructions: Number the steps sequentially.
- Preservation: Maintain original recipe details including quantities, cooking times, and tips.
使用示例
查看来源仓库中的使用示例与配置说明。
查看来源 ↗来源历史
- 收录时间
- 2026-01-20
- 索引更新时间
- 2026-01-26
- Branch
- main
收录与同步日期属于本站记录。源码修改历史请查看来源仓库。
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!