How to write a good prompt
The same habits that improve any prompt apply across all of these:- 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.
- Ask for evidence. Request sources, assumptions, and flagged data gaps so you can audit the answer rather than taking it on faith.
- Name what matters to you. Telling the Agent which drivers, metrics, or risks you care about focuses the analysis on your decision.
- 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.
- State your context. Your horizon, your strategy, and your existing position all change the right answer. Say them.
The collections
| Collection | For |
|---|---|
| Stock research prompts | Analyzing individual companies |
| Screening prompts | Finding stocks that match criteria |
| Market analysis prompts | Reading the market, sectors, and macro themes |
| Scheduled task prompts | Automating briefings, monitors, and alerts |
| Paper trading prompts | Testing ideas with simulated trades |
| Playbook templates | Strategy memory by investing style |
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.Related
- Skills reference — what each Skill does
- Guides — full walkthroughs that use these prompts
- Skills concept — how prompts map to Skills