Choose by what you want out the other side, not by which video looks most impressive. Every video below is free, on YouTube, and I have listed the real run time so the hour actually fits.
Watch: Claude Cowork: 8 Use Cases Every Marketer Should Know by Grace Leung, 20 minutes 51 seconds. Eight worked examples of Claude doing real work inside real files, no code, no terminal. It is framed for marketers but the shape of it transfers to any desk job.
Copy: pick the single use case closest to something you did last week and rebuild it exactly as shown, using her example first.
Transplant: run the same use case on your own file. Her channel: youtube.com/@graceleungyl.
Watch: How I'd Make Money with Claude if my life depended on it by Nate Herk, 9 minutes 19 seconds. Short and unusually concrete about what is actually sellable. Because it is only nine minutes, follow it with the first ten minutes of How to Build a One Person AI Business, 24 minutes 52 seconds in full, and come back for the rest another night.
Copy: build the smallest version of one offer he describes, end to end, badly. Badly is fine. Finished is the point.
Transplant: rebuild it for a business you actually know, ideally one you have worked in. His channel: youtube.com/@nateherk.
Watch: Claude Skills: Build Your First AI Marketing Team in 16 Minutes by Grace Leung, 16 minutes 42 seconds. Skills are the single highest-leverage Claude feature for non-developers, because they turn a prompt you keep re-explaining into a command you type once. If you want the bigger version afterwards, Claude Code: Build Your Full AI Marketing Team runs 17 minutes 35 seconds.
Copy: build the exact skill she builds, install it, run it once on her example.
Transplant: rewrite that skill's instructions for a task you repeat weekly, then run it on this week's version.
Watch: Every Claude Code Skill I Use to Drive My Entire Development Process by Cole Medin, 23 minutes exactly. This one assumes you are comfortable in a terminal and is deliberately last, because it makes far more sense after you have shipped something small.
Copy: take one skill from his setup and reproduce it in your own project.
Transplant: replace one manual step of your real workflow with it. His channel: youtube.com/@ColeMedin.
I said in the reel that Anthropic's own channel is underrated, and I want to be accurate about what is actually on it. Anthropic's YouTube channel is mostly short announcement and research videos, often one to two minutes, like Introducing Cowork or Let Claude handle work in your browser. They are excellent for knowing what shipped. They are not hour-long walkthroughs, so do not plan your evening around them.
The actual Anthropic-made teaching lives somewhere else, and it is free:
The copy block fails when you sit there thinking "right, so what do I ask it". Use these two prompts to bridge from the video into your own work. Open claude.ai in a second window before you press play.
First, while the video is still fresh, get the workflow out of your head and onto the page:
I just watched a tutorial and I want to rebuild what they did rather than only understand it. Here is what happened in the video, in my own messy words: [describe what they built, what they typed, and what came out, even if you are fuzzy on the details].
Turn that into a numbered workflow I can follow right now, step by step, with the exact thing I should type at each step written out in full rather than described. Where I have clearly missed or misremembered a step, fill the gap and mark it as your assumption so I can check it against the video. Where a step depends on a tool or setting I might not have switched on, tell me the setting and where to find it before I get stuck halfway.
Keep it to the smallest version that still produces a finished result. I would rather build a small thing tonight than half of an impressive one.Then, in the last block, move it onto your own material:
Now run that same workflow on my actual work instead of the tutorial's example. Here is my situation: [your role, the task you repeat most often, and the tool or file it usually lives in]. Here is a real example of the input I would give it: [paste something real, an email, a plan, a spreadsheet row, a brief].
Adapt the workflow to my inputs and tell me clearly where my version has to differ from the tutorial's version, and why. If any step does not transfer, say so plainly rather than inventing a workaround that will fall over the second time I run it.
Finish by telling me which single step of this I should turn into a reusable saved prompt or a skill, and write that saved version out for me in full so I can keep it.