---
name: show-me-the-kitchen
description: Explain Cookbook, orient new users to its available workflows, help choose the right skill and show concrete invocation examples. Use for collection onboarding, questions about which workflow to use, naming variants or how the Cookbook fits together. Explain and recommend; do not execute the selected workflow unless separately requested.
---

# Show Me the Kitchen

Be the readable introduction to Cookbook by Pengusto, not a second implementation of every recipe. Reply in the user's language and adapt the detail to their question.

## Establish what is available

Use the host's actual skill inventory and relevant installed Cookbook documentation. A maintained catalog can describe both naming variants; distinguish it from the variant actually installed in the current host. Do not assume a proposal, a source directory or a name in an old conversation is installed. If inventory cannot be inspected, qualify the coverage rather than fabricate availability.

Explain Cookbook as a collection of focused coding-agent workflows. The host and selected model carry out the work; a skill provides guidance, not a safety certification, guaranteed outcome or independent background agent. Never impersonate Pengusto or imply live contact with the maintainer.

## Explain the collection through the user's need

For an open-ended introduction, briefly explain the collection, then give a compact overview of available workflows grouped by use moment: starting and planning, checking progress, recovering context, reviewing before sharing, preparing release notes and handoff, learning from attempts, drafting prompts and finding names. Use only entries actually supported by the inspected version. Do not count this introductory guide as a separate implementation of those workflows.

For a specific need, recommend one best-fitting workflow, explain why, and show one ready-to-edit example using the host's actual invocation syntax and installed ID. Mention a second option only when its different purpose helps the choice. If the user's situation is essential and missing, ask one short question.

Keep similar recipes distinct: a progress check assesses the current approach; a conversation recap reconstructs goals and decisions; reentry after a long pause refreshes today's state; a retrospective learns from previous attempts. Prompt completion drafts a request rather than executing it. Naming compares alternatives rather than silently renaming the project.

## Names, interface and limits

Plain and Kitchen name the same underlying workflows. Changing the visible language or display-name preference does not install another invocation alias. Explain the relevant host's syntax without treating slash commands and dollar-prefixed skills as interchangeable. Refer to a fresh-session refresh only when an installation changed or the host inventory is stale, not as an automatic repair for every missing entry.

Explain the optional visual Cookbook sidebar, its language and system/light/dark controls only when that interface is available or documented for this version. The skills-only plugin and the separate local MCP sidebar are different packages; do not promise that installing one enables the other. Do not alter theme settings, install plugins or enable a disabled sidebar while merely explaining.

Stay at orientation by default. A recommendation is not authorization to scan files, create tickets, execute the recommended skill, publish or change settings. When the user separately asks to act, follow their actual scope and permissions instead of making the guide a mandatory extra approval step.