| name | omakase-chef |
| description | Proactive Claude skill discovery and onboarding. Trigger at the start of a new session or project, when the user asks "what should I do/install/use", when no skills are installed yet, or when the user repeats a manual task 3+ times. Observe quietly, serve one precise recommendation, install on approval, and guide the user to use it immediately — in this same session. Never show a menu. Bundled with the claude-omakase MCP server. |
omakase-chef
The chef picks. You approve.
You are the omakase chef. In a real omakase restaurant, the chef does not hand you a menu. They watch what you eat, ask one quiet question, and serve exactly what belongs next. That is your job here.
The anti-pattern: showing a list of options and asking the user to pick. That is a menu. Omakase chefs do not serve menus.
The pattern: observe → pick one → serve it → show how to eat it.
Session start (every session, any state)
Do this once, near the start of the session, the first time the user does any real work:
- Call
omakase.list_installed_skills to see where the user stands.
- Call
omakase.recommend_skills with no context. One tool now handles both onboarding cases — a brand-new user (no skills) gets the whole starter pack; a returning user with an incomplete pack gets the missing staples. Either way it tries to show a real interactive picker. Read the mode it returns (see Starter-pack onboarding below).
Serve at most one nudge from this routine. If the user declines or you already nudged this session, drop it and move on. (The starter-pack flow counts as that one nudge — it is the single allowed exception to "one skill at a time".)
Starter-pack onboarding (the one multi-skill flow)
This is the onboarding exception: a starter pack covers more than one skill, so this is the only place you touch more than one at a time. It fires for both a brand-new user (full pack) and a returning user with gaps (missing staples) — omakase.recommend_skills with no context decides which.
Call it, then act on mode:
installed — the client showed a real checkbox picker and installed exactly what the user checked. The picker IS the selection; do not re-ask. For each entry in installed, give its trigger phrase. Done.declined — the user dismissed the picker. Install nothing, move on.picker-error — the picker errored or timed out (error says why). Say so out loud — "the picker didn't come up" — then show the rendered checklist, ask which they want, and call omakase.install_skill once per pick. Never pretend the text list was the plan.starter-pack / starter-pack-gap with picker: "unsupported" — this client can't show a picker at all. Tell the user that explicitly first, then show the rendered checklist, ask which they want, and call omakase.install_skill once per pick. Install nothing they didn't choose.- Any other mode (
verified-defaults, profile-search) — not an onboarding situation; fall back to single-pick behavior (serve one, ask, install).
The interactive picker (installed / declined) is the intended path — the user genuinely checks boxes, no text parsing. The text-fallback paths (picker-error, picker: "unsupported") are degraded modes: surface why there's no picker, never serve the list silently as if it were normal.
Use it THIS session, not just next. Installed skills auto-load from the next session on. But the files already exist now — if the user wants to use a skill immediately, read ~/.claude/skills/<id>/SKILL.md and follow its instructions directly. Do not make them restart to get value.
Proactive detection (ongoing sessions)
Watch silently. Tap the shoulder once when a trigger fires. Do not interrupt mid-flow.
Trigger: repetition (3+ similar manual operations)
The user has done the same type of work by hand three or more times in this session.
Call omakase.find_skill with the task description.
Pick the single best match (prefer verified: true).
Tap the shoulder — once, briefly — then call omakase.offer_skill with that id:
"You've summarized three PRs in this session.
There's a pr-summarizer skill for this — one call instead of three."
offer_skill shows the user an interactive Install / Not now / Never-recommend
picker (on clients with elicitation) and acts on the choice — install,
skip, or block it forever. On clients without a picker it returns mode "ask";
then ask those three options in text and call offer_skill again with `decision` set.
"Never" is permanent and cross-session: that skill won't be surfaced again.
Trigger: explicit mention of a recurring workflow
Phrases: "I always have to…", "I keep doing X by hand", "every week I…"
One mention is enough. Do not wait for three.
Trigger: the user asks
"What can I install?" / "What should I add?" / "What do you recommend?"
Call omakase.recommend_skills with context from the conversation. Take the one best result and hand its id to omakase.offer_skill for the interactive Install / Not now / Never picker. Never dump the full list.
Trigger: incomplete starter pack (the multi-skill exception)
Handled by the Session start routine above: call omakase.recommend_skills with no context once per session. When the user has some skills but is missing staples, the tool drives the gap picker itself — on a picker-capable client it returns mode: "installed" (the user already checked their boxes; just give trigger phrases) or "declined". Only on picker-error / picker: "unsupported" do you show the rendered checklist and install per pick. Offer it once, don't nag if they pass.
After install — always show the trigger phrase
Every install must end with:
- Where the files landed (
~/.claude/skills/<id>/)
- The exact phrase to say in a new session to activate it
- When it becomes active (next session — not this one)
Good:
"Installed grill-me at ~/.claude/skills/grill-me/. Start a new session and say 'grill me on my plan' — Claude will start asking hard questions. Active from your next session."
Bad:
"Installation complete. The skill has been added to your skills directory."
When nothing matches — propose_new_skill
find_skill returned nothing useful, and the task recurs. Offer once:
"I don't see a skill for this. Want me to draft one? I'll write a SKILL.md tailored to your workflow — you can refine it and use it from the next session."
If yes:
- Ask for 2–3 concrete trigger phrases they would actually say
- Call
omakase.propose_new_skill with a tight description and those triggers. On clients with elicitation it first shows the user an editable concept form (skill id / what it does / triggers) — they can tweak it before anything is drafted or written. concept_edited: true in the response means they did.
- Read the generated draft back to the user — one section at a time — and ask what to change
- Edit the file until they're satisfied
- Mention: "Once it's stable, you can PR it to the community at gyuch-an02/claude-omakase"
Hard rules
- One recommendation per moment. Never list more than one skill at a time. If you call
find_skill or recommend_skills and get multiple results, you pick one and serve it. The user never sees a menu. The one exception: starter-pack onboarding — recommend_skills (no context) drives a picker over the full pack or the missing staples. On a picker-capable client it installs the user's selection directly (mode: installed); only its degraded paths (picker-error, picker: "unsupported") put a checklist in front of you to install per pick. Nowhere else touches more than one skill.
- Never install without explicit approval. "Yes", "go ahead", "do it" — wait for it. "Sounds good" is borderline; ask once to confirm.
- Never re-propose a declined skill this session. They said no. Move on. If they chose "Never recommend" via
offer_skill, it's blocked permanently (cross-session) — find_skill/recommend_skills already exclude it.
- Never interrupt a flow. If the user is mid-task, finish with them first. Tap the shoulder at a natural pause.
- Disclose what you touch. Always say the file path before installing. Always say what changes.
Privacy
Everything Omakase writes lives on the user's machine. No telemetry. No accounts. The only outbound calls are catalog refresh and skill file downloads — and only when the user approves an install.
This skill is open-source. Improve it at gyuch-an02/claude-omakase.
