Get the FREE Ultimate OpenClaw Setup Guide →

cook-menu

npx machina-cli add skill PJuniszewski/cook/cook-menu --openclaw
Files (1)
SKILL.md
2.4 KB

cook-menu Skill

Interactive menu for managing cook artifacts using native Claude Code UI.

Execution Flow

When /cook-menu is invoked, follow this flow:

Step 1: Scan Artifacts

Run this command to get artifact list with metadata:

for f in cook/*.cook.md; do
  if [ -f "$f" ]; then
    name=$(basename "$f" .cook.md)
    status=$(grep -m1 "^## Status" -A1 "$f" | tail -1 | tr -d '[:space:]')
    mode=$(grep -m1 "^## Cooking Mode" -A1 "$f" | tail -1 | tr -d '[:space:]')
    echo "$name|$status|$mode"
  fi
done

Step 2: Select Artifact

Use AskUserQuestion tool to present artifacts:

Question: "Which artifact do you want to manage?"
Header: "Artifact"
Options: [list of artifacts with status as description]

If user selects "Exit" or cancels, end the skill.

Step 3: Select Action

Use AskUserQuestion tool to present actions:

Question: "What do you want to do with <artifact-name>?"
Header: "Action"
Options:
  - "Validate" - "Run validation checks on this artifact"
  - "Compare" - "Diff with another artifact"
  - "Status" - "View artifact metadata summary"
  - "Back" - "Return to artifact selection"

Step 4: Execute Action

Based on selection:

Validate:

./scripts/cook-validate "cook/<artifact>.cook.md" --verbose

Compare:

  1. Use AskUserQuestion to select second artifact
  2. Run: ./scripts/cook-diff "cook/<artifact1>.cook.md" "cook/<artifact2>.cook.md"

Status:

./scripts/cook-validate "cook/<artifact>.cook.md" --quiet

Then display: filename, status, mode, owner, date, section count.

Back: Return to Step 2.

Step 5: Loop

After action completes, return to Step 3 (action selection) for same artifact. User can select "Back" to return to artifact selection.

Example Flow

/cook-menu
  │
  ▼
[AskUserQuestion: Select artifact]
  - dry-run-validation.2026-01-10 (well-done)
  - artifact-versioning.2026-01-10 (ready-for-merge)
  │
  ▼ user selects "dry-run-validation"
  │
[AskUserQuestion: Select action]
  - Validate
  - Compare
  - Status
  - Back
  │
  ▼ user selects "Validate"
  │
[Runs cook-validate, shows results]
  │
  ▼
[AskUserQuestion: Select action] (loop)

Requirements

  • Artifacts in cook/*.cook.md
  • scripts/cook-validate for validation
  • scripts/cook-diff for comparisons

Source

git clone https://github.com/PJuniszewski/cook/blob/main/skills/cook-menu/SKILL.mdView on GitHub

Overview

cook-menu provides an interactive UI to manage cook artifacts using native Claude Code UI. It scans the cook/*.cook.md files to list artifacts with their status and mode, lets you pick an artifact and an action, and executes validation, diff, or status checks accordingly.

How This Skill Works

On invocation, it scans artifacts from cook/*.cook.md to build a list with name, status, and mode. It then uses AskUserQuestion to select an artifact and an action (Validate, Compare, Status, Back). Actions run corresponding scripts (cook-validate or cook-diff) and display results or metadata, looping back to the action selection for the same artifact until you go Back or Exit.

When to Use It

  • Validate an artifact to run comprehensive checks with verbose output
  • Compare two artifacts to surface differences using cook-diff
  • View a concise status/metadata summary of an artifact
  • Review multiple artifacts in a session without reloading
  • Navigate from artifact selection back to action selection for iterative work

Quick Start

  1. Step 1: Run /cook-menu to start the interactive menu
  2. Step 2: Use the first prompt to select an artifact from the list
  3. Step 3: Choose an action (Validate, Compare, Status, Back) and follow prompts

Best Practices

  • Ensure all cook/*.cook.md artifacts are up to date before scanning
  • Use Verbose for initial validation to capture detailed results
  • Use Quiet for quick status checks to reduce noise
  • Verify that scripts/cook-validate and scripts/cook-diff are executable
  • Document results after each action for traceability

Example Use Cases

  • dry-run-validation.2026-01-10 (well-done) -> Validate artifact with verbose checks
  • artifact-versioning.2026-01-10 (ready-for-merge) -> Status view to confirm metadata
  • quick-audit.2026-02-01 (needs-review) -> Compare with another artifact to assess changes
  • featureX.2026-02-15 (in-progress) -> Validate, then review diffs for progress tracking
  • release-candidate.2026-02-28 (awaiting-approval) -> Status to finalize readiness

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers