Skip to main content
Driven selects a Skill for your question automatically. This page explains how that works, how to steer it, and how to override it when you want a specific workflow.

Automatic selection

By default, you do not name a Skill. You describe what you want, and Driven routes to the workflow that fits. The routing reads the intent of your prompt:

How to steer the choice

The clearer your intent, the more reliable the routing. Phrasing that names the task helps:
  • “Value [TICKER] and cross-check against peers” clearly signals valuation
  • “Find companies with [criteria]” clearly signals screening
  • “Compare [A] and [B]” clearly signals comparison
Vague prompts (“tell me about [TICKER]”) can route to a general analysis when you wanted something specific. If you want valuation, say valuation.

Naming a Skill explicitly

You can force a specific Skill by naming it in your prompt:
Use Deep Research to analyze [TICKER]'s competitive position and risks.
This bypasses the inference and runs the named Skill.

Manual invocation

You can also invoke any Skill directly through the menu or the command line, independent of your prompt’s wording. This is useful when:
  • You know exactly which workflow you want
  • You want to override the automatic choice
  • You want to run a specific Skill on existing context

When routing picks the “wrong” Skill

If the result is not the workflow you expected, you have two options: rephrase to signal the intent more clearly, or invoke the Skill you wanted explicitly. Either corrects it. You do not have to start a new conversation.