Douguo Recipe Collection

Problem

When asking an agent for recipes, common issues are unclickable results, missing fields being filled in arbitrarily, and limited mobile rendering. Users usually want to compare a few dishes quickly, then open one recipe for the full method. This skill constrains recipe lookup into a predictable Markdown output flow, reducing fabrication and format drift.

How It Works

The skill uses the Douguo food MCP and usually runs in two steps:

• Search: When the user mentions a dish or ingredient, it calls douguo_recipe_search, returns five first-page results, and renders a table with serial number, recipe name, author, favorites, time, difficulty, and main ingredients. Recipe names use recipe_url hyperlinks, and missing fields are shown as —.
• Detail: After the user selects a recipe, it calls douguo_recipe_detail and outputs a linked title, author, difficulty, time, description, an ingredient quantity table, and ordered steps. Ingredients must include both name and quantity, and steps must appear in order without merging or skipping.

Boundaries

• It does not auto-paginate, support exact filters, or display images, including step images.
• If MCP does not return ratings, cooking time, or difficulty, those fields must remain marked as missing instead of being inferred.
• On service errors, the response should advise retrying later or visiting the Douguo site, rather than fabricating recipe content.