When should you use it?
- You rebuild the same style of deck often
- Meeting notes pile up unformatted
- Your Claude subscription includes the extension
Not for: Pixel-perfect design work; Confidential files on sites the extension should not see
What do you need, and what do you get?
You need
- A presentation template
- Your raw notes or research topic
- The Claude browser extension
You get
- A populated deck ready for polish
- A clean Word file plus a PDF copy
- Readable research summaries and draft emails
How does it work, step by step?
- Install and pin the extensionAdd it from the Chrome store, sign in and grant access only to the sites you plan to use.
- Open the templateLoad your deck and describe what each section needs to cover.
- Let it fill, then polishIt handles headings and body copy; you do the final visual pass.
- Paste the messy notesAsk for a structured Word document with clear headings, then an exported PDF.
- Draft from contextWith an email or page open, ask for a reply or summary based on what is on screen.
The prompt
Our own prompt, inspired by Nick Woodford and written to work in Claude. Values in lime are placeholders.
Here is my presentation template open in this tab. Fill it for a talk on [topic] for [audience]: one idea per slide, short headings, no more than [N] bullets each. Keep the template's layout and fonts. Use only the facts in [source notes]. When done, list any slide where you had to guess so I can check it.
Inspired by Nick Woodford: How to Use Claude's Chrome Extension to Automate the Work You Keep Putting Off. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Browser agents are slow; plan to do something else while it works.
- Check the facts in any research page before sending it on.
Our take
Modest, believable uses are why Nick Woodford's write-up is worth listing. Filling a familiar slide template, tidying meeting notes into a Word file and PDF, compiling research into a readable page and drafting email from the current tab are not glamorous, but together they eat hours every week. His honesty about speed helps: treat the side panel like an assistant you brief and leave alone, not a tool to stare at while it works. Limit site permissions to the handful of domains you actually need, so it cannot wander into banking, HR or payroll tabs. Keep templates and style guides in a folder it can open, which produces more consistent decks than describing the look each time. Review every email draft before sending, and spot-check figures it pulls into slides against the source. Close sensitive tabs before enabling the extension on a page. Prefer exporting finished files to your own drive rather than leaving them only in the chat.
Where the time goes back: Formatting work is low-skill but time-consuming; delegating it leaves you only the final review.
FAQ
Is it on the free plan?
How much time does it save?
Source and credit
Inspired by Nick Woodford. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- How to Use Claude's Chrome Extension to Automate the Work You Keep Putting Off
- Creator
- Nick Woodford
- Published on
- marketsmarterwithai.substack.com (Substack)
- Original date
- Mar 24, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.