What problem does it solve? Two Quarto-related skills exist with overlapping triggers, and context-based firing silently picks one, so requests can land on the wrong skill without anyone noticing. This router classifies each Quarto request, dispatches it to the correct skill, and forces an explicit report of which skill was not used and why. ## Core Features & Use Cases - Request Classification: Maps request shapes (new deliverable creation, existing project reconfiguration, syntax questions, format migration, render failure triage) to either origin-quarto or quarto-authoring. - Execution Ordering: Enforces template-first workflow where origin-quarto sets up organizational templates before content is written, with quarto-authoring references consulted mid-task as needed. - Accountability Reporting: Requires a one-line declaration explaining why the unused skill was skipped, making routing mistakes traceable. - Use Case: A user asks to build RevealJS slides from the company template. The router dispatches to origin-quarto for template copying and rendering, consults quarto-authoring only if a syntax question arises, and reports that quarto-authoring was not the primary skill used. ## Quick Start Route my Quarto request to the right skill: I want to create a new slide deck from our organizational template and render it to PowerPoint.
