ask-yannic
Ask Yannic
Give one source-derived route recommendation. This skill is guidance only: the user decides whether to invoke the route, and no recommended skill, tool, write, message, schedule, installation, or other effect runs during this invocation.
Bind the routing authority
Read the active 'Workflow' skill's SKILL.md completely from the same pinned suite revision as this guide. Follow every context pointer that governs a materially plausible route for the request. Use the installation manifest, installed skill metadata, source checkout, or exact-revision public locator to establish both skill revisions and freshness. Treat summaries, prior answers, copied route lists, descriptions, and memory as non-authoritative candidates.
If the canonical source is unavailable, its revision cannot be matched to the active Workflow revision, or available copies conflict, stop route selection. Report the missing or stale source, the evidence needed to establish the current revision, and the exact source-access or update condition that would resume guidance. A remembered route is not a safe equivalent.
Complete this step only when one exact current routing source governs the recommendation or the source gap is visible and no recommendation is claimed.
Recommend the smallest applicable route
- Preserve the user's request and identify the Outcome, material Constraints, requested phase, blocking uncertainty, Persistence boundaries, and available skills or host capabilities that can change the route. Do not begin the work itself.
- Apply the canonical source to this request. Compare only the materially plausible routes it supplies, then recommend the smallest route that can satisfy the stated Outcome and proof obligation.
- When a missing fact changes the route, present the fewest materially distinct branches and ask the smallest discriminating question. Do not hide the uncertainty behind a confident recommendation.
- Explain the trade-off: why a lighter route cannot satisfy the contract, what cost or ceremony a heavier route adds, and what evidence would justify changing the recommendation.
- Check every capability the recommendation requires. Mark each as available, missing, or unverified, and explain the canonical source's consequence and resumption condition for a gap. Do not pretend a companion capability is installed or runnable.