If this session was compacted, the copy of this skill in context may be cut off. Read ${CLAUDE_SKILL_DIR}/SKILL.md from disk and resume at the step you are on.

When to invoke

Use when the task clearly wants a vibestack workflow but the right one is not obvious, or when the host has no slash-command picker and the pack has to be found by name. In Claude Code, Cursor, Kiro and Copilot CLI, skills are /name. In Codex there is no / picker — reference a skill as $name inside an ordinary message (Use $office-hours to shape this idea).

/vibe — pick the right skill

The router is named vibe, not vibestack: the pack's own checkout is sometimes parked at ~/.claude/skills/vibestack, and a skill installing to that path would collide with it — the installer's own integration test asserts that checkout survives.

Route on intent. Process skills come first: brainstorm or plan before implementing, investigate before fixing, review before shipping.

Anything not listed here is in the full index — read it rather than guessing at a skill name:

_found=""
for _d in "${CLAUDE_SKILL_DIR:-}" "$HOME/.agents/skills/vibe" "$HOME/.claude/skills/vibe" \
          "$HOME/.cursor/skills/vibe" "$HOME/.kiro/skills/vibe" "${COPILOT_HOME:-$HOME/.copilot}/skills/vibe" \
          ".agents/skills/vibe" ".claude/skills/vibe" ".cursor/skills/vibe" ".kiro/skills/vibe" ".github/skills/vibe"; do
  if [ -n "$_d" ] && [ -r "$_d/skills-index.md" ]; then
    cat "$_d/skills-index.md"; _found=1; break
  fi
done
if [ -z "$_found" ]; then
  for _r in "$HOME/.agents/skills" "$HOME/.claude/skills" "$HOME/.cursor/skills" "$HOME/.kiro/skills" \
            "${COPILOT_HOME:-$HOME/.copilot}/skills"; do
    [ -d "$_r" ] && { echo "$_r:"; ls "$_r"; }
  done
fi

The index sits next to this file, so if none of those paths resolve, read skills-index.md from the directory this SKILL.md was loaded from.

Second opinion — route by host. The outside voice has to be a different model from the one already running:

if [ -n "${CODEX_THREAD_ID:-}" ] || [ -n "${CODEX_SANDBOX:-}" ]; then echo "HOST: codex"
elif [ -n "${CLAUDECODE:-}" ]; then echo "HOST: claude"
else echo "HOST: other"; fi

HOST: claude → codex. HOST: codex → claude (codex refuses to run nested under Codex, and would be the same model anyway). HOST: other (Cursor, Kiro, Copilot CLI) → codex, unless the session's own model is GPT, then claude. Copilot CLI sets no documented session variable, so it always reports HOST: other.

Rules when routing:

• Invoke it, don't describe it. Once a skill fits, hand off: invoke it through the Skill tool (Claude Code, Cursor, Kiro, Copilot CLI), or on Codex load that skill's SKILL.md and follow it (users invoke it there as Use $<name>). Do not answer with a list of options, and do not do the skill's work freehand when the skill exists. Except: never invoke a typed-only skill (a row that says "type /name") — tell the user to type it (on Codex, Use $name) and do not do its work yourself.
• Failures. When the user names the cause and a narrow fix, make one read-only check of the file, test or log it rests on; if it holds, fix it and run the focused test, otherwise invoke investigate. When the cause is unknown, make one read-only triage pass, with no reproduction and no wider search, over the supplied evidence and the code it implicates; fix only if that pass alone proves the root cause, otherwise invoke investigate.
• Answer directly instead when the request is a quick factual question (including "which skills are there?" — show the table), a small edit the user scoped themselves, or the user asked for a direct answer rather than a workflow.
• Pick one. Don't stack skills; each carries its own full workflow, and a skill's own instructions take precedence once invoked.
• Only route to a skill that is installed. Don't guess a name: if the table or the index has nothing that fits, or the skill is not present on this host, say so and proceed normally — these are workflows, not dependencies.