Skip to content
cccskills
FreePublished on GitHub

test-kitchen

This skill should be used when implementing features with parallel exploration or competition. Triggers on "build", "create", "implement", "try both approaches", "compare implementations". Routes to omakase-off (entry gate for design exploration) or cookoff (exit gate for parallel implementation).

The English summary is being prepared. Showing the original description.

See how to install

Files included (6)

  • SKILL.md4.7 KB
  • cookoff/SKILL.md13.3 KB
  • judge/SKILL.md5.7 KB
  • omakase-off/references/detailed-workflow.md7.9 KB
  • omakase-off/SKILL.md4.8 KB
  • skill-report.json82.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Test Kitchen

Parallel implementation framework with two gate skills:

SkillGateTrigger
test-kitchen:omakase-offEntryFIRST on any build/create/implement request
test-kitchen:cookoffExitAt design→implementation transition

Flow

"Build X" / "Create Y" / "Implement Z"
    ↓
┌─────────────────────────────────────┐
│  OMAKASE-OFF (entry gate)           │
│  Wraps brainstorming                │
│                                     │
│  Choice:                            │
│  1. Brainstorm together             │
│  2. Omakase (3-5 parallel designs)  │
└─────────────────────────────────────┘
    ↓
[Brainstorming / Design phase]
    ↓
Design complete, "let's implement"
    ↓
┌─────────────────────────────────────┐
│  COOKOFF (exit gate)                │
│  Wraps implementation               │
│                                     │
│  Choice:                            │
│  1. Cookoff (2-5 parallel agents)   │
│  2. Single subagent                 │
│  3. Local implementation            │
└─────────────────────────────────────┘
    ↓
[Implementation]

Key Insight

Skills need aggressive triggers to work. They can't passively detect "uncertainty" or "readiness" - they must claim specific moments in the conversation flow.

  • Omakase-off: Claims the BUILD/CREATE moment (before brainstorming)
  • Cookoff: Claims the IMPLEMENT moment (after design)

When Each Triggers

Omakase-off (Three Triggers)

Trigger 1: BEFORE brainstorming

  • "I want to build...", "Create a...", "Implement...", "Add a feature..."
  • ANY signal to start building something
  • Offers choice: Brainstorm together OR Omakase (parallel designs)

Trigger 2: DURING brainstorming (slot detection)

  • 2+ uncertain responses on architectural decisions
  • "not sure", "don't know", "either works", "you pick", "no preference"
  • Offers to explore detected slots in parallel

Trigger 3: Explicitly requested

  • "try both approaches", "explore both", "omakase"
  • "implement both variants", "let's see which is better"

Cookoff

  • "Let's implement"
  • "Looks good, let's build"
  • "Ready to code"
  • Design doc just committed
  • ANY signal to move from design to code

Omakase Mode (Skip Brainstorming)

If user picks "Omakase" at the entry gate:

  1. Quick context gathering (1-2 questions)
  2. Generate 3-5 best architectural approaches
  3. Implement ALL in parallel
  4. Tests pick the winner
  5. Skip detailed brainstorming entirely

Best for: "I'm flexible, show me options in working code"

Cookoff Mode (Parallel Implementation)

If user picks "Cookoff" at the exit gate:

  1. Each agent reads the same design doc
  2. Each agent creates their OWN implementation plan
  3. All implement in parallel
  4. Compare results, pick winner

Best for: "I want to see different implementation approaches"

Key Distinction

Omakase-offCookoff
GateEntry (before/during brainstorming)Exit (after design)
QuestionHOW to explore?HOW to implement?
Parallel onDifferent DESIGNSSame design, different PLANS
TriggersBuild request, indecision detection, explicit"let's implement" signal
SkipsBrainstorming (optional via short-circuit)Nothing - always after design

Slot Detection (During Brainstorming)

When omakase-off delegates to brainstorming, it passively tracks architectural decisions where user shows uncertainty:

Detection signals:

  • "not sure", "don't know", "either works", "both sound good"
  • "you pick", "whatever you think", "no preference"
  • User defers 2+ decisions in a row

Slot classification:

TypeExamplesWorth exploring?
ArchitecturalStorage engine, framework, auth methodYes - different code paths
TrivialFile location, naming, config formatNo - easy to change

At end of brainstorming:

  • If architectural slots exist → offer parallel exploration
  • If no slots → hand off to cookoff for implementation

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace440Updated Oct 21, 2026

Trigger for: explaining current FAR, DFARS, or agency-supplement text; determining documented acquisition-policy status for an agency and FAR part; comparing codified text, RFO model text, and agency deviations; tracing acquisition rulemaking; finding procurement comment periods; analyzing public comments; refreshing prior policy analysis; or producing an Acquisition Policy Impact Brief. Use published federal sources and supplied policy documents without making legal or procurement-specific applicability determinations. Do not use for clause selection, market research execution, opportunities, pricing, grants, or cooperative agreements.

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace440Updated Oct 21, 2026

Systematic framework for extracting actionable items from documents and organizing them into prioritized, trackable checklists. Use when converting reports, meeting notes, audits, or any document with embedded action items into structured TODO lists.

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace440Updated Oct 21, 2026

Browser automation for AI agents via inference.sh. Navigate web pages, interact with elements using @e refs, take screenshots, record video. Capabilities: web scraping, form filling, clicking, typing, drag-drop, file upload, JavaScript execution. Use for: web automation, data extraction, testing, agent browsing, research. Triggers: browser, web automation, scrape, navigate, click, fill form, screenshot, browse web, playwright, headless browser, web agent, surf internet, record video

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace440Updated Oct 21, 2026

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace440Updated Oct 21, 2026

Run AI apps via inference.sh CLI - image generation, video creation, LLMs, search, 3D, Twitter automation. Models: FLUX, Veo, Gemini, Grok, Claude, Seedance, OmniHuman, Tavily, Exa, OpenRouter, and many more. Use when running AI apps, generating images/videos, calling LLMs, web search, or automating Twitter. Triggers: inference.sh, infsh, ai model, run ai, serverless ai, ai api, flux, veo, claude api, image generation, video generation, openrouter, tavily, exa search, twitter api, grok

The English summary is being prepared. Showing the original description.

aiskillstore/marketplace440Updated Oct 21, 2026

See all skills by aiskillstore

Report a problem with this skill