30 days. 10 minutes a day.

Welcome to the Toolkit, the Friday half of The AI Debrief. Tuesday tells you what happened; Friday hands you something to use. (If you missed it, Tuesday's issue was about a model that's half price only until January.)

Here's the problem this week's tool is built to solve, stated honestly. You read about something on Tuesday. You mean to try it. By Thursday it's buried, and the following week there's a new thing, and the cycle restarts. Six months of that and you know a hundred tool names while actually using about two. The gap isn't knowledge. It's reps — on a schedule, applied to your own work.

The 30-Day AI Academy Challenge

We opened it this week and it's free. Every day for thirty days you get three things: one short lesson, one 10-minute worksheet, and one check-in. That's the entire commitment — no three-hour modules, no dashboard of unwatched videos.

The ten minutes is the feature, not a limitation. Anything that needs an hour gets postponed to a day you have an hour, and that day keeps not arriving. Ten minutes survives a bad week, which is the only thing that matters over a month.

The worksheet is what makes it stick. A lesson you watch is entertainment. A lesson you apply to your own work the same day is a skill you still have in March.

The month at a glance

Start Here (Days 1–2). A welcome and a tour, then your goal and your AI stack. Day 2 is the one that decides whether the rest lands — you pick what you're actually building toward, so every lesson after it has somewhere to go.

Week 1 — AI Foundations. How these models actually work and how to talk to them. Unglamorous, and the reason everything downstream runs on understanding instead of copy-paste.

Week 2 — Core Skills. The dense stretch: advanced prompting, custom instructions and memory, projects and knowledge bases, writing and content in your own voice, AI images and video, then data, docs and spreadsheets. It ends on Day 16 with the capstone — you assemble all of it into your own personal AI OS. Not a certificate. A working system, tuned to your job, that you keep.

Week 3 — Automations. The part almost nobody reaches on their own: getting the work to happen while you're not at the keyboard. This is where the ten minutes a day starts paying rent.

Week 4 — Build & Apply. The payoff stretch. You pick your path, build the AI system that actually fits it, and get into the ways people are turning these skills into income. Everything from the first three weeks points here — by the end you are not learning tools any more, you are running something.

Here's the Day 2 exercise, stripped down. It works on paper, and it's the single highest-leverage thing in the first week.

1. List last week's five most repeated tasks. Not projects — tasks. "Wrote the client update." "Cleaned the export." "Answered the same three questions." Be specific enough that someone else could do it from your description.

2. Put two numbers on each. Roughly how many hours it took, and how much you'd miss it on a scale of one to five. Most people find one task eating four-plus hours that they'd score a one.

3. That's your target. High hours, low attachment. Not the most interesting task — the most repeated one. Interesting work is where you want your hours going; repeated work is what you want to hand off first.

4. Name your stack, out loud. Which model you'll use, where the context lives, what "done" looks like. Most AI attempts fail here: people ask a chat window for something without having decided what a good answer looks like.

Do those four steps and you'll get more out of the next month than most people get out of a course. The challenge just gives you twenty-nine more days of it, with the worksheet already written.

Every 30-day anything has the same failure point, and it is not Day 1 or Day 30. It is Day 9 — far enough in that the novelty is gone, not far enough that you have seen a result yet. Three things get people through it.

Anchor it to something you already do. Not "I will do it in the morning" but "I will do it while the coffee brews." A time anchored to an existing habit survives a busy week. A time anchored to intention does not.

Do the worksheet on real work. The temptation is to practise on a tidy made-up example. Don't. Use the actual half-finished thing sitting on your desk, however messy — messy is where the learning is, and it is the only version that transfers to Monday.

Miss one, never two. You will miss a day; everyone does. The rule that matters is that a missed day stays a missed day instead of becoming the end of the streak. Almost nobody quits because they skipped a Tuesday. They quit because skipping Tuesday made the whole thing feel already failed.

If you want company for it, the challenge runs inside AI Academy, where people post what they built each day. That daily check-in is the third piece, and it is the reason a group challenge finishes at a completely different rate than a course you bought alone.

Who should skip it. If you're already running custom instructions, knowledge bases and automations daily, Weeks 1 and 2 will be review — start at Week 3 or skip this one entirely and I'll see you Tuesday. This is built for the much larger group who use AI most weeks, suspect they are using maybe a tenth of it, and have never had a reason to sit down and find out. Thirty days is long enough to prove that out and short enough that you will actually finish.

Free, no card. Day 1 takes 20 minutes.

That's the Toolkit.

See you Tuesday for the Debrief.

From Drew and The AI Debrief team

P.S. If you start the challenge, hit reply and tell me the goal you pick on Day 2. I read every one, and I'll be checking in on the challengers all month.

P.P.S. New here, or skipped one? Every past edition is in the archive.