Pick the result
Name one thing you want to finish: a listing presentation, a repeatable follow-up draft, or a workflow that stops failing.
Use AI to turn a YouTube playlist or a Skool classroom into a short plan for the work you actually need to do.
A course is a repair shop, not a hobby. Bring one problem. Leave with one working result.
A great tutorial can still be the wrong tutorial for you. The useful question is: what helps me finish my next real task?
Name one thing you want to finish: a listing presentation, a repeatable follow-up draft, or a workflow that stops failing.
Paste a playlist, lesson list, notes or captions you can access. For a Skool course, use material you have permission to use.
Have AI rank watch first, skim and skip against your goal, available time and tools you already use.
Try one small step. Record what worked, what failed and the next question. Let that question choose your next lesson.
Choose your constraints. Copy the prompt into the AI assistant you already use, then add your source material.
This page creates the prompt locally in your browser. You don't need to sign in here. If your AI cannot open a link or read captions, paste the text instead.
Joshua's July 2026 course notes prioritized memory, reliable routines and review over repeating setup. The useful lesson: borrow the idea that fills a gap in your stack.
Start with the lessons on recurring work and observing failures if your current problem is a workflow that needs checking.
Build target: one check that reports a failure clearly before you add more automation.
Understand what information belongs in short, medium and long-term memory. Compare each role with the tools you already have.
Build target: a simple map of what your assistant needs to remember and where it belongs.
Choose this when your assistant produces work that needs a stronger review step. Define what a good result must pass.
Build target: a review checklist and a separate critique before you use the result.
Pull the review and debugging lessons when your checks are weak. Read your notes first, then watch the part that answers the open question.
Build target: reproduce one failure and verify the fix.
The July 5 lesson notes kept one useful idea: back up the assistant's knowledge. They skipped a second agent stack that duplicated existing tools.
Build target: a recoverable backup of your own non-sensitive configuration. Your needs may differ.
Choose this when a real presentation is the next deliverable. Save unrelated design tools for a task that actually needs them.
Build target: one clear presentation you can use.
Skip foundations you already use confidently. Park a new database, knowledge app or agent package if an existing tool already does that job.
Revival trigger: a specific repeated problem your current setup cannot handle.
A visual setup, design critique or live troubleshooting demo can be worth watching. Ask AI to identify the relevant segment only when timestamps are available.
Read a caption-based brief for the steps, tradeoffs and one next action. Open the video if something important is unclear.
Repeated beginner setup and duplicate tools go to the bottom. A new title or a dramatic claim doesn't create a new priority.
This distinction also informed Joshua's September 27, 2026 video learning guide: some videos needed visual attention; others were briefed from captions or skipped. A title-only ranking is provisional, not transcript analysis.
These public takeaways come from the September 27, 2026 caption-based briefs. All three received “Read the brief” in that learning guide. Read the idea below first; open the video when you need more detail.
Useful idea: separate yes/no, pick-one and scoring tasks from open-ended writing. Start with a small, labeled sample and check the decisions before expanding.
Try it: give your AI ten fictional support requests and three categories. Review each classification and note where the categories are unclear.
Useful idea: one coordinator can decide who owns a request. Specialists need a clear role and only the tools needed for that role.
Try it: write a coordinator instruction: “When I describe a task, name the owner, deliverable and next step.” Test it before creating additional assistants.
Useful idea: use real data, consistent typography and one coherent visual style. Keep the successful style as a reference for the next graphic.
Try it: give your AI a reference image you can use, your type and color choices, and one verified fact. Ask for one graphic, then review readability on your phone.
Start with public videos from these creators. Apply the same filter before adding another course or community.
Creator identities checked against their public YouTube pages on October 5, 2026. These links are starting points, not a guarantee about every video or a paid-community recommendation.