Learn: a lesson a day
Five-minute lessons that build on each other. Spot the made-up number, fix the request that caused it, and learn what works. Anything you miss comes back until it sticks.
Short lessons that feel like a game, a simulator where you direct an AI agent and catch its mistakes, and a coach for the AI work you really do.
Try one · catch the AI's mistake
How it works
Five-minute lessons that build on each other. Spot the made-up number, fix the request that caused it, and learn what works. Anything you miss comes back until it sticks.
Real jobs done by an AI agent — with the mistakes agents really make planted in them. Brief it, decide what it's allowed to do, and catch what's wrong before it reaches anyone.
Paste a conversation you had with ChatGPT, Claude or Copilot. See what you checked, what you didn't and what you shouldn't have shared — and the lesson that fixes each gap.
A 20-minute test that adapts to your level. One score from 10 to 160, broken down into four skills, that you can share. Retake it every two weeks and watch it climb.
Streaks that count practice, not visits
XP only for right answers and real work
Weekly leagues, and leagues for your team
Review aimed at your weakest skills
What you'll learn
Four sections, 16 units, about five minutes a lesson. Each section builds on the one before.
Section 1
Section 2
Section 3
Section 4
If you use AI at work
Now
Every week you type the same request into ChatGPT, worded a little differently each time.
With Tokolingo
You write it well once, then reuse it every week with your files and standards built in.
Now
The answer sounds right, so you send it — without really knowing what it got wrong.
With Tokolingo
A quick check flags anything your own files don't back up, before it goes out.
Now
Someone asks how you made it, and the honest answer is: I kept tweaking until it looked right.
With Tokolingo
You have clear written steps you can share with your team, improve, and rerun in ten minutes.
Your first real task · about 30 minutes
Your actual status update, research summary or report, with every claim checked against your own files. You know what’s safe to send before you send it.
Five short answers that make it work: what to attach, what to ask, what good looks like, what to check, and what never to paste. Pick a day and it’s ready for you again next week.
Your score before and after, and every run timed against doing it by hand — so you see the hours saved and the mistakes caught before they went out.
Start with the task that eats most of your week
Real work, step by step
No studying up front. You try the real task, and whatever goes wrong decides the lesson you get next.
Do the job with no help at all.
Five minutes shows exactly where you struggle — no guessing — and that decides the one lesson you get next.
We highlight what the material doesn't back up.
A score tells you how you did. A highlight on your own words tells you what to change — and each one links to the lesson that fixes it.
The same job again, with hints, a coach and a worked answer.
This is where the real document gets made, and where you see whether the fix worked. Revise and resubmit as often as you like.
Save your steps and pick when you'll need them again.
This is what you still have next Monday. Everything before it proves the steps work; this makes them come back when you need them.
Feedback on your own words
A score tells you how you did. Highlights on your own sentences show what to change — and which claims you shouldn’t send.
The team resolved most blockers this week1 and the migration is nearly done2.
Sign-ups are up to 1,240 this month, from 9803.
Good AI work is more than a prompt
AI gets better at understanding prompts every year. The other four parts don’t get easier, and they’re where work actually goes wrong.
What gets attached every time — and what deliberately doesn't?
Without it you paste whatever is nearest, and the AI fills the gaps with guesses.
The prompt you send, every time.
A vague request gets a confident answer in the wrong shape, and you fix it by hand.
What must be true of the output before you'd accept it?
Decide this before you look, or you'll end up accepting whatever came back.
What do you verify before any of this leaves the building?
Skip it and the invented number goes out with your name on it.
Who is accountable, and what never goes in?
Nobody owns it, so nobody catches it — and confidential text leaks by habit.
Beyond the daily path
When something goes wrong on a real task, you get the longer lesson that fixes it — about eight minutes, then straight back to work.
8 screens · 14 min
Three contradictory user interviews and forty minutes before a roadmap review. Produce a memo where every claim traces back to a quote.
6 screens · 12 min
An AI-drafted investor update with invented numbers in it. Find them, prove they are wrong, and rewrite it before it reaches the board.
5 screens · 10 min
Scattered team updates into a status email your VP will actually read, ending with the prompt you reuse every Monday after.
Looking at this for a team? Team groups are free: a shared league, and a dashboard of who practised and what their real work saved. See how teams work.
FAQ
Take a quick placement to find your level, then start the path and watch your score climb.
Start learning