recipe-testing

Draft simple test-stage recipes in metric units and await approval before adding them to the testing list.

10|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/benjaminshafii/digital-empire --skill recipe-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recipe-testing
Source: https://github.com/benjaminshafii/digital-empire/tree/main/.opencode/skill/recipe-testing
Command: npx skills add https://github.com/benjaminshafii/digital-empire --skill recipe-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the creation of ultra-simple test-stage recipes and defers canonical publishing until user approval, reducing upfront effort while preserving quality control.

Core Features & Use Cases

  • Collect minimal inputs (dish name, 3-8 ingredients, serving size, rough prep time, cook time, and optional flavor notes) to draft a simple recipe.
  • Generate a concise, 3-6 step workflow using metric units and avoiding complex techniques.
  • Enforce an explicit approval flow: summarize the recipe and wait for "approved" before adding to the testing list.
  • Tag approved recipes with "testing" and a non-canonical note when added to the app.

Quick Start

Provide the dish name, main ingredients (3-8 items), serving size, rough prep time and cook time, and any must-have flavor notes (optional). The system will draft a brutally simple recipe (3-6 steps) using metric units and present a clear confirmation prompt: reply "approved" to add to the testing list. If not approved, revise inputs and repeat. On approval, the recipe is added to the testing list with the "testing" tag and a note indicating it is a non-canonical test entry.

Frequently Asked Questions about recipe-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a simple test-stage recipe with an approval workflow?

To create a test-stage recipe, provide a dish name, 3-8 ingredients, serving size, prep time, cook time, and optional notes. The system drafts a 3-6 step recipe using metric units and waits for your explicit approval before adding it to the testing list.

What minimal inputs do I need to draft a step-by-step recipe for testing?

Drafting a step-by-step recipe requires a dish name, 3 to 8 ingredients, serving size, rough prep time, and cook time. Optional flavor notes can also be included to generate a concise recipe workflow ready for review.

How does the recipe approval process work before adding a draft to the testing list?

The recipe approval process works by presenting a summarized draft and waiting for you to reply 'approved'. Upon receiving approval, the recipe is added to the testing list with a 'testing' tag and a non-canonical note indicating it is a test entry.

Can I use imperial units when generating a test-stage recipe workflow?

No, you cannot use imperial units. The recipe generation strictly enforces metric units to ensure consistency across the 3-6 step workflow, avoiding complex techniques while drafting the simple recipe for your testing list.

What happens to a drafted recipe if I do not approve it during the confirmation flow?

If a drafted recipe is not approved during the confirmation flow, it is not added to the testing list. You must revise your initial inputs and repeat the generation process to receive a new draft for approval.

Are there limitations on the number of ingredients or steps for a test-stage recipe?

Yes, limitations include restricting ingredients to 3-8 items and confining the workflow to 3-6 steps. This ensures the generated recipe remains ultra-simple and avoids complex techniques before entering the testing list.