Cook menu

Skill PJuniszewski/cook/skills/cook-menu

Interactive menu for managing cook artifactsFrom its SKILL.md

Install

npx -y skills add PJuniszewski/cook --skill cook-menu

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
runs commandsInstructs the agent to run 4 commands, including `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" ` and 3 more.

SKILL.md

2.4 KB, 667 tokens by cl100k_base, as published. Nobody here has run it

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:

Use AskUserQuestion to select second artifact
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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.