AI Career Skills Tree
A five-layer roadmap from digital basics to AI agents and automation ops. Click the nodes you already master, and this tree will mark your next step.
How it works
- Click every node you already master. The five layers run in order — foundations first, then tools, prompting, agents, and finally automation ops.
- The next-step card lights up: the tree walks the path in order and highlights the first unfinished node with an amber border.
- Come back and check off new nodes as you learn them. Your progress is saved in this browser automatically — no account, no sign-up.
It walks the five layers in order — Foundation, Core Tools, Prompting, AI Agents, Automation Ops — and picks the first node you haven't checked off yet. Finish that one and the next-step card moves forward automatically.
Yes. Your checked nodes are stored in your browser's localStorage under the key jb_tree. They survive refreshes and closed tabs, but they live on this device only — clearing browser data resets the tree.
Not strictly, but the path is designed that way: skipping foundations usually means you'll use advanced tools poorly. If you're already fluent with AI chat tools, feel free to jump ahead and check off nodes that genuinely fit.
A practical standard: you could explain the node's idea to a colleague and actually use it on a real task this week. Naming the tool isn't enough — being able to apply it is.
Yes. Every tool on this site is free, requires no sign-up and has no paywall. Your answers never leave your browser.
Who this tool is for
The tree is built for people in non-technical roles who have used an AI chat tool a few times and now want an honest picture of what they can actually do. Typical users are support team leads, HR coordinators, marketing generalists, operations staff and finance analysts — people whose learning budget is an occasional lunch break rather than a training programme.
You do not need to be technical, and the tree will not ask for your email address. It is a bad fit if you want a course recommendation, a salary estimate, or a certificate to show a manager. There are 17 nodes here and no content behind them; the tree is a map and a self-check, and the learning itself happens elsewhere.
How to read your result
Two numbers sit above the tree: a percentage and a count in the form 9 of 17 nodes mastered. The percentage is checked nodes divided by total nodes, rounded. It is not a competence score and it does not weight difficulty — one foundation node and one automation node are worth exactly the same.
Below that, the next-step card names a single node and tells you to work through it once on a real task before checking it off. The rule is positional: the tree scans the five layers in order and returns the first node without a check. That is why a checked node in layer four cannot hide an unchecked node in layer two. If every node is checked, the card switches to a completion message and the percentage locks at 100.
Read the card as a suggestion about sequence, not a verdict about readiness. A support lead who has checked nine nodes and is told to practise follow-up prompts has not failed at agents; she simply has unfinished work one layer below.
A worked example
Daniel leads a six-person customer support team. He opens the tree and honestly checks file and cloud basics, spreadsheet fluency, email and calendar habits, and critical thinking — all four foundation nodes, because he does those daily. He adds ChatGPT and Claude, which he uses for reply drafts, and Google Gemini, which his company pays for. Nine checks, 53 percent, and the next-step card points to iterate with follow-up prompts in layer three.
That result is accurate rather than flattering. He has tools but has never deliberately sent a second and third instruction to improve an answer. He spends the next two weeks doing exactly that on ticket replies, then checks the node. Later he checks asking for a specific output format, understands what agents actually do, and builds one no-code agent for weekly ticket summaries — 13 of 17, 76 percent, next step always review agent output. The remaining node is the one he is least comfortable with, which is the point of the layout.
Common mistakes
- Checking tools you have only heard of. Naming a product is not mastery. The working test is: could you use it on a task this week and explain the result to a colleague?
- Starting at layer two. Chat tool buttons feel like progress, but without the foundation layer the outputs are hard to judge and easy to over-trust.
- Skipping critical thinking. Verifying sources is the node that protects every other node. It is also the one people quietly uncheck.
- Waiting for a clean run. Nodes are checkboxes, not stages. Check what you can genuinely do, leave the rest, and let the card keep pointing.
- Reading 100 percent as a certificate. The tree has 17 boxes and no assessment. Completion means you claimed every node, nothing more.