skills/chef-assistant/SKILL.md
Guides cooking through culinary principles, food science, and flavor architecture rather than rote recipe steps. Covers technique teaching (knife skills, sauces, searing, braising), food science (Maillard reaction, emulsions, brining), flavor troubleshooting (salt/acid/fat/heat balance), menu planning, ingredient substitutions, plating, and cultural cuisine exploration. Use when users mention cooking, recipes, chef, cuisine, flavor, technique, plating, food science, seasoning, or culinary questions.
npx skillsauth add lyndonkl/claude chef-assistantInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill teaches cooking through principles — science and rationale before steps, flavor architecture (salt, acid, fat, heat, sweet, bitter, umami, aroma, water, texture), sensory cues paired with precision measurements, reproducible ratios and templates, and cultural context showing how different cuisines approach similar challenges.
Quick example:
User asks: "My chicken breast is always dry. What am I doing wrong?"
Response approach:
Copy this checklist and track your progress:
Chef Assistant Progress:
- [ ] Step 1: Define cooking goal and constraints
- [ ] Step 2: Identify key techniques and principles
- [ ] Step 3: Build flavor architecture
- [ ] Step 4: Plan texture and contrast
- [ ] Step 5: Execute with sensory cues and precision
- [ ] Step 6: Plate and present with intention
Step 1: Define cooking goal
Specify what you're making, dietary constraints, equipment available, skill level, and time budget. Identify if goal is recipe execution, technique learning, flavor troubleshooting, menu planning, or cultural exploration.
Step 2: Identify techniques
Break down required techniques (knife cuts, searing, emulsions, braising). Explain why each technique matters and provide sensory cues for success. Reference resources/template.md for technique breakdowns.
Step 3: Build flavor architecture
Layer flavors in stages:
See resources/methodology.md for advanced flavor pairing.
Step 4: Plan texture
Every dish should have at least one contrast:
Step 5: Execute with precision
Provide clear steps with both sensory cues and measurements:
Step 6: Plate and present
Apply plating principles:
Self-assess using resources/evaluators/rubric_chef_assistant.json. Minimum standard: Average score ≥ 3.5.
Pattern 1: Recipe Execution with Technique Teaching
Pattern 2: Flavor Troubleshooting
Pattern 3: Technique Deep Dive
Pattern 4: Menu Planning with Progression
Pattern 5: Cultural Cooking Exploration
Critical requirements:
Salt at multiple stages: Don't season only at end. Season proteins before cooking (dry brine or salt 30min+ ahead), season base aromatics, season sauce, finish with flaky salt for texture.
Use meat thermometer: Visual cues alone are unreliable. Invest in instant-read thermometer. Pull temps: chicken 150-155°F (carries to 160°F), pork 135-140°F (medium), steak 125-130°F (medium-rare), fish 120-130°F depending on type.
Taste as you go: Adjust seasoning incrementally. Add salt/acid/fat in small amounts, taste, repeat. Can't un-salt, but can always add more.
Mise en place before heat: Prep everything before you start cooking. Dice all vegetables, measure spices, prep aromatics. High-heat cooking moves fast—no time to chop mid-sear.
Control heat: Most home cooks cook too hot. High heat for searing only. Medium for sautéing aromatics. Low for sauces and gentle cooking. Preheat pans properly (water droplet test).
Rest meat after cooking: Allow proteins to rest 5-10 min after cooking (longer for roasts). Juices redistribute, carryover cooking completes. Tent with foil if worried about cooling.
Acid brightens: If dish tastes flat despite salt, add acid (lemon, lime, vinegar, tomato). Acid wakes up flavors and balances richness.
Fat carries flavor: Aroma compounds are fat-soluble. Toast spices in oil/butter to release flavor. Finish sauces with fat for body and sheen.
Common pitfalls:
Key resources:
Quick ratios and formulas:
Typical workflow time:
When to escalate:
Inputs required:
Outputs produced:
chef-assistant-guide.md: Complete cooking guide with recipe, techniques, flavor architecture, plating guidance, and cultural contexttesting
--- name: advisory-edit description: A strict advisory-only editing discipline for a writer who dictates ("speaks out") essays and wants help WITHOUT having their voice changed. The editor directs structure, flags grammar, and suggests strategic language — but never modifies the writer's text unless the writer explicitly says "apply" / "make that change" / "rewrite this." Produces a line-referenced, suggestion-only critique where every item is marked the writer's call. Four passes: structural, l
testing
Provides the house style for analyst-grade strategist writing — third-person register with sparing first-person, no em dashes, no "not X, not Y, not Z" negation cascades, numbered footnote citations rather than inline source parentheticals, specific opinion-signaling phrases, and topic-forward paragraph structure modeled on voice patterns observed in Damodaran's Musings on Markets and Thompson's Stratechery. Use when consolidating working notes into a finished long-form strategist or analyst report that must read as written by a senior human analyst rather than an AI assistant.
testing
Renders a markdown report to a PDF using pandoc with xelatex (11pt serif body, 1-inch margins, numbered footnotes, formal heading hierarchy). Requires a one-time install of pandoc and a LaTeX engine on the user's machine — basictex on macOS or texlive-xetex on Linux. Does not attempt automatic install. Fails loudly with the exact install commands if pandoc or xelatex is missing on the user's PATH. Use when producing a finished strategist or analyst report PDF from a polished markdown source.
testing
Produces step-by-step computational walkthroughs of vector and matrix operations as a sequence of numbered "frames", showing the explicit state at each step. The text-equivalent of a 3Blue1Brown animation — each frame shows what changed and why, so the learner can re-trace the operation by hand. Use when the learner needs to *see* a computation unfold (eigenvalue computation, attention with 3 tokens, gradient descent step, SVD on a 2×2, layer norm on a 3-vector, softmax of a small input), when an explanation has been given but the learner needs to ground it in a worked example, or when introducing an operation that's intimidating in symbol form but trivial in pencil-and-paper form.