Every scenario on this site ships with a skill tree. It exists because a flat list of skills does not answer the question you actually have: “what do I need, in what order, to finish this task?”
The layers
A skill tree has four layers:
- The goal, which is the scenario itself.
- The phases, which group capabilities by the stage of work they belong to.
- The capability nodes, which name what must happen in tool-neutral terms.
- The skills, which are the concrete, installable ways to execute each capability.
Validation sits at the edge of the tree. It is the check that decides whether the whole tree produced the promised outcome.
Read it from the goal down
Start at the goal, then follow the phases in order. The phase names are not decoration, they are the execution sequence. If a phase says “Verify”, the tree is telling you that verification belongs in that position, not at the end as an afterthought.
Inside each phase, the capability nodes answer “what has to happen here”. The skills under each node answer “which tool or method can do it”. Capability nodes are deliberately tool-neutral, so the tree survives tool churn: if a skill stops being maintained, the capability still tells you what you need.
What the node states mean
Capability nodes link to their own pages, where you will find the input, output, risks, and acceptance criteria for that capability. Skills display their granularity and verification status. A skill marked unverified means the entry exists and was checked on the review date, but the site has not independently run it yet. That is a fact about evidence, not a judgment on quality.
On mobile
The tree collapses to a vertical flow on small screens. Read it the same way: phases stack in order, and each phase expands to its capabilities and skills. Nothing is hidden, the layout just changes from horizontal to vertical.
The tree is a contract
The most useful way to read a skill tree is as a contract you can hand to an agent. Copy the scenario’s task brief, and the tree tells the agent which capabilities exist, which skills to prefer, and what to verify. The tree is not an article about the task, it is the task broken into its executable parts.