Free Resource
The full list is right here. No signup needed to read it.
This is the working list, no fluff. Each workflow takes under a minute to try, and each one comes with a prompt you can copy and adapt to your own work today.
Talk or paste everything in your head, half sentences and all, then ask Claude to shape it into something usable: a doc, a plan, an email.
The messier the input, the more this one earns its keep. You are not writing for Claude, you are thinking out loud at it.
Try this prompt
Here is everything on my mind about the team offsite, completely unsorted. Turn it into a one-page plan with sections for goals, agenda, logistics, and open questions.
Paste two or three emails you have written and liked, then ask for a new one that matches your tone.
Claude picks up your phrasing, sentence length, and level of formality from the samples, so you edit a draft that already sounds like you instead of starting from a blank page.
Try this prompt
Here are three emails I wrote recently. Study my tone, then draft a reply to the message below that declines the meeting but offers two alternative times. Keep it in my voice.
Paste a transcript or your messy notes and ask for the structure underneath: who owns what, by when, and what was actually decided.
This works even when the notes are fragments, because the decisions are usually in there, just buried.
Try this prompt
Here is the raw transcript from today's planning call. Pull out every decision made, every action item with an owner and a deadline, and anything that was raised but left unresolved.
Upload a PDF, contract, or report and ask for the handful of things that actually matter, plus anything unusual.
You are not skipping the reading, you are deciding which parts deserve a close read. That is a different and better use of your time.
Try this prompt
Here is a 40-page vendor contract. Give me the five things that matter most, anything unusual compared to a standard agreement of this type, and the questions I should ask before signing.
Paste anything confusing, such as jargon, an error message, or a clause in a policy, and ask for the plain-English version plus what to do next.
The second half of that ask is the important part. An explanation with a next step is worth far more than an explanation alone.
Try this prompt
Explain this error message in plain English, tell me what most likely caused it, and give me the first thing I should try.
Describe what you want a column to do in plain words and get the formula back, with an explanation of each part.
The explanation matters: next time you can modify the formula yourself instead of asking again.
Try this prompt
In Google Sheets, I want column D to show the number of days between the date in column B and today, but display the word overdue when that number is negative. Give me the formula and explain each part.
Before a decision, give Claude your plan and ask it to argue against it.
Claude is agreeable by default, so you have to assign the skeptic role explicitly. Done right, this surfaces the objection you would otherwise hear three weeks too late.
Try this prompt
Here is my plan to consolidate our two newsletters into one. Argue against it as a skeptical colleague would. What am I missing, and what would have to be true for this to fail?
Ask for a comparison or an overview and require sources you can check.
Then actually check the ones your decision depends on. The workflow is not "trust the answer", it is "get a well-organized starting point and verify what matters".
Try this prompt
Compare the three main approaches to running a customer advisory board. Cite sources I can check for each claim, and flag anything you are not certain about.
Paste one finished piece, such as a post, a doc, or a video transcript, and ask for the other formats you need.
The thinking is done; this is translation work, and Claude is very good at translation work. Review each output before it goes anywhere.
Try this prompt
Here is a blog post I just finished. Turn it into a LinkedIn post, a short email to my list, and three short social posts. Keep my wording wherever you can.
The meta-workflow behind all of the above: every ask gets context (what is going on), a role (who Claude should act as), and a format (what the output should look like).
Compare a bare ask like "Write a project update" with the version below. Same request, and the second one comes back usable on the first try.
The upgraded version
You are a project manager writing for executives who have two minutes. Context: we are three weeks into the website redesign, on schedule, but the photography quotes came in above what we planned. Write a five-sentence update that leads with status and ends with the one decision I need from them.
The foundational lessons are free. Short, hands-on, and built around real scenarios like the ten above, so what you practice is what you actually use.
Claude Academy is an independent learning platform and is not affiliated with, endorsed by, or sponsored by Anthropic. Claude is a trademark of Anthropic, PBC.