Skip to main content
This is a library of copyable prompts for getting the most out of Driven, organized by what you are trying to do. Every prompt is a starting point: copy it, swap in your tickers and criteria, and adjust to fit. Where a prompt maps to a specific Skill, it routes there automatically.

​
How to write a good prompt

The same habits that improve any prompt apply across all of these:
  1. Be specific about what you want. “Analyze NVDA’s data center margins and the risks to them” beats “tell me about NVDA.” Specificity in, specificity out.
  2. Ask for evidence. Request sources, assumptions, and flagged data gaps so you can audit the answer rather than taking it on faith.
  3. Name what matters to you. Telling the Agent which drivers, metrics, or risks you care about focuses the analysis on your decision.
  4. Iterate in place. The first answer is a draft. Push back: ask for the bear case, ask it to date claims, ask it to tighten scope.
  5. State your context. Your horizon, your strategy, and your existing position all change the right answer. Say them.

​
The collections

​
A note on letting Driven route

You rarely need to name a Skill. Describe the task and Driven selects the right workflow. The prompts here are written that way, in plain language about the goal. If you want to force a specific Skill, you can name it (“Use Deep Research to…”) or invoke it from the menu.