What problem does it solve?
When users ask how to configure or operate a feature, plain text answers are often insufficient, yet blindly launching interactive guides for every keyword creates noise. This Skill resolves that tension by deciding when a step-by-step interactive guide is appropriate and by driving the full guide lifecycle based on system-injected states.
Core Features & Use Cases
- State-Driven Responses: Reacts to injected states (Guide Matched, Pending, Selection, Active, Completed) instead of re-matching guides from raw chat text.
- Guide Lifecycle Control: Uses MCP tools to fetch available guides, send interactive selection cards, persist guide state, launch the frontend overlay, and control an active guide (exit or skip).
- Judgment Before Action: Distinguishes between users who need a quick explanation and users who need hands-on step-by-step guidance, avoiding fake or duplicate guide offers.
- Use Case: A user asks "how do I configure this feature?" The assistant checks available guides, offers an interactive card with start/preview/skip options, launches the overlay on confirmation, and handles exit requests mid-guide.
Quick Start
When the user asks how to operate a feature, check available guides with the guide MCP tools and offer an interactive guide card instead of a long text tutorial.
