What is a professional skill tree?
A professional skill tree organizes capabilities as connected branches instead of an isolated checklist. The root can represent a field, role, or professional direction. Branches can represent skills, work, education, projects, credentials, and learning goals. The structure makes relationships easier to see while leaving room for different experience levels, career changes, and paths that do not fit neatly into one job title.
How The Arbor Primus uses the tree metaphor
The Arbor Primus uses a Professional Build as a living capability map. You decide what the foundation means, then grow branches from real experience and learning. A branch can show a capability you already use, a project where you practiced it, or a direction you are intentionally developing. The map is a way to add context—not a test, score, or promise about your future.
- Start with one honest capability, role, field, or project.
- Add branches for skills and the areas where they apply.
- Connect education, work experience, projects, and credentials when they clarify the story.
- Review the map and choose the next branch that is useful to you.
What can you add to a Professional Build?
A useful Build can hold more than a list of keywords. Add the information that helps you explain your capability and keep the source of each signal clear. Evidence and verification are optional; they should never be treated as automatic proof of every claim.
- Skills and capability areas
- Work experience, responsibilities, and practical experience
- Education, training, courses, and an Education Tree
- Projects, achievements, and portfolio context
- Credentials, certifications, and licenses
- Optional evidence, links, and learning goals
- A separate Hobby Tree for interests and personal projects
How a skill tree differs from a resume
A resume is a focused document for a particular purpose. A Professional Build is a broader, connected map that can keep more context available as your direction changes. The two can work together: use an Arbor to organize the source material, select the parts that fit a role, and create a resume without forcing every branch into the final document.
Privacy is part of the map
Professional Builds start private. You control whether a Build is private, unlisted, or public, and you can choose which capabilities, records, hobbies, evidence, social links, or resume sections appear in a shared view. Private and unlisted content is excluded from public discovery systems. Public sharing never changes self-reported information into independent verification.