Route users to the right skill through guided interview

Runs a short structured interview to figure out what a user is trying to do, then recommends one primary skill and up to two secondary skills from the installed skill library, with a one to two sentence reason for each and the exact @skill-name invocation to copy-paste. The interview asks up to four funnel questions in order, skipping any made irrelevant by an earlier answer: the broad task area (building or coding, debugging, security or pentesting, AI/LLM/automation, marketing/SEO/growth, DevOps/infrastructure, design/UI/UX, or planning/strategy); how specific the task already is (clear spec, rough idea, or starting from scratch); the tech stack or domain involved, only if relevant; and whether the user wants to work fully autonomously or stay in the loop. After recommending, it offers to compose a complete, ready-to-paste prompt using the recommended skill and everything learned in the interview.

Use it when the user says "I don't know where to start" or "which skill should I use," has a vague goal without a clear method, asks "what should I use for..." or "I'm not sure how to approach this," or is new to the skill library and needs guidance. It never recommends more than one primary and two secondary skills at once, picks the most upstream skill first when a goal spans multiple categories (for example a brainstorming skill before a full-stack build skill), and defaults to a brainstorming skill for open-ended goals or an app-builder skill for anything involving building something when the user is totally lost. It only recommends skills - it does not execute them, the user still has to invoke the recommended skill themselves - and it only knows about skills actually installed in the library, so a recommendation for an uninstalled skill may not work; its routing reference also does not cover every skill in the library, and highly ambiguous goals may need follow-up clarification since routing is natural-language matching, not guaranteed classification.

Input is the user's answers to the funnel questions. Output is a structured recommendation naming a primary skill with its reasoning and exact invocation syntax, up to two secondary "also consider" skills, and optionally a full ready-to-use prompt. The routing reference maps broad categories to representative skills - for example, building a full product routes to an app-builder skill (via a brainstorming-then-plan-writing sequence if the user wants to plan first, or a fully autonomous mode if they want hands-off execution); debugging something broken routes to a systematic-debugging skill, or a test-fixing skill specifically for failing tests; integrating a third-party service routes to service-specific skills such as a Stripe-integration skill for payments or a Clerk-auth skill for authentication; and security or pentesting work routes to an ethical-hacking-methodology skill plus a pentest-checklist, with web-app-specific skills like SQL-injection or XSS testing layered in as needed.

Operates entirely within the same skill library it routes into - it reads the installed skill list and returns @skill-name invocations the user pastes to actually run them; it has no external APIs or services of its own.

Anyone new to a large skill library, or with a vague goal and no clear method, who wants a short guided interview to land on the right skill (or short sequence of skills) and a ready-to-paste prompt, instead of browsing dozens of skill names to guess which one fits.