quick-healthy-recipes
Generate exactly 3 simple, fast, healthy recipes from food photos, ingredient lists, or cravings. Use for what-to-cook-tonight requests. Don't use for restaurants, meal plans, baking, or medical diets.
What this skill does
# Quick Healthy Recipes Turn food photos, ingredient lists, or a short cooking desire into **exactly 3** practical recipes that are simple, fast, and healthy enough for a normal weeknight. ## When to use Use this skill when the user asks things like: - "what can I cook with this?" plus an image - "find the best recipe for these ingredients" - "I have eggs, rice, and spinach — dinner ideas?" - "I want something healthy and quick tonight" Do not use it for restaurant recommendations, long meal plans, baking projects, special-diet medical advice, or gourmet cooking that requires advanced technique. ## Core principles Optimize every answer for: 1. **Simple** — few extra ingredients; favor common pantry items. 2. **Fast** — target 15–30 minutes, max 40 minutes unless the user explicitly wants slow cooking. 3. **Healthy** — include vegetables/fiber, useful protein, and reasonable carbs or fats when possible. 4. **Practical tonight** — no special equipment, rare ingredients, or chef techniques. 5. **Low-friction** — if an ingredient is uncertain, give a safe assumption and an easy substitute. Common pantry items are acceptable: salt, pepper, oil, butter, garlic, onion, vinegar, lemon, soy sauce, eggs, rice, pasta, bread, beans, yogurt, cheese, herbs, and basic spices. ## Workflow ### 1. Understand the input If images are provided, inspect them before suggesting recipes. Identify: - Main ingredient(s) - Freshness or cleaning concerns - Parts that cook differently, such as stems vs leaves - Any visible uncertainty If text is provided, extract: - Ingredients available - Desired dish, cuisine, or constraint - Timing clues like "tonight", "quick", or "lunch" Ask a question only when a safety-critical detail is missing. Otherwise, make a reasonable assumption and state it briefly. ### 2. Safety filter Do not confidently identify or recommend eating high-risk unknown items such as wild mushrooms, unknown berries, spoiled food, raw seafood, or foraged plants. If the food might be unsafe, say so and suggest using only verified ingredients. Do not give medical nutrition advice. For allergies, pregnancy, diabetes, kidney disease, or other medical constraints, keep guidance general and tell the user to follow their clinician's advice. ### 3. Build 3 recipe options Create exactly 3 distinct options. Each option should vary by cooking style or meal format, for example: - Stir-fry / sauté - Soup / stew - Bowl / salad / pasta - Omelet / egg dish - Sheet-pan / pan-roast For each recipe, keep ingredient additions short. Prefer one protein booster and one carb/fiber base when the raw ingredients alone are not balanced. ### 4. Rank for tonight Put the best fit first. The first recipe should usually be the fastest and most realistic with the least extra shopping. ## Output format Use this exact structure. Keep it concise. ```markdown Looks like: [ingredient identification or parsed request] Assumption: [one short assumption, or "none"] 1. [Recipe name] — [time] Best if: [why this is the top fit] Extra ingredients: [0–5 common items] Steps: - [short step] - [short step] - [short step] Healthy balance: [protein + veg/fiber + carb/fat note] 2. [Recipe name] — [time] Best if: [why choose it] Extra ingredients: [0–5 common items] Steps: - [short step] - [short step] - [short step] Healthy balance: [protein + veg/fiber + carb/fat note] 3. [Recipe name] — [time] Best if: [why choose it] Extra ingredients: [0–5 common items] Steps: - [short step] - [short step] - [short step] Healthy balance: [protein + veg/fiber + carb/fat note] Pick tonight: [one sentence recommendation] ``` ## Quality checklist Before finalizing, check: - Exactly 3 recipes are present - Each recipe can be cooked without special equipment - Extra ingredients are common and limited - The first recipe is the best fit for tonight - At least two recipes include a realistic protein path - Any uncertainty from images is stated rather than hidden If a recipe fails the checklist, replace it before answering.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.