Standing up a skills taxonomy
Build the first levelled catalogue from documents you already hold rather than from a vendor's generic library.
— Talent & Leadership
Codes recurring themes from a set of role and framework documents into a levelled skills catalogue, with a review pause before it's finalised.
2–3 weeks → ~15 minutes
For a typical multi-document review workflow
No coding required
— USE CASES
Build the first levelled catalogue from documents you already hold rather than from a vendor's generic library.
Merge overlapping frameworks from different functions or acquired entities into one levelled structure.
Re-run against updated role documents so the catalogue is maintained rather than rebuilt.
— HOW IT BEHAVES
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
All of your role documentation and capability evidence is processed as one set, so patterns across documents surface instead of being read one file at a time.
Ambiguities about the role or function in scope are resolved with you up front, so the run does not quietly assume the wrong scope.
The run pauses for a person to confirm the skills that matter before the deliverable is composed.
Findings on the role or function in scope are written up as a document that reads like professional output, with each claim tied back to a skill.
Derived columns are added row by row, keeping your source data and the judgement about each skill side by side.
The skills land as a clean table you can sort, filter or drop straight into the deliverable.
A skills taxonomy assembled by hand takes months and drifts immediately. Standing up a skills taxonomy is the typical trigger — build the first levelled catalogue from documents you already hold rather than from a vendor's generic library. Done properly it is defensible; done at pace it becomes a judgement call nobody can retrace. And "properly" usually means 2–3 weeks of manual work.
Skillsize turns that work into a Skill: you supply the material, and what comes back is a levelled skills catalogue, with themes coded consistently across every source document. What sits between input and output is the codified method: thresholds, sequencing and the points where a human confirms a call — all of it visible and editable in the Skill. Net effect: 2–3 weeks down to ~15 minutes, no drift between runs, and every conclusion traceable back to the evidence behind it.
Build skills catalogue exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.
Builds evidence-backed employee skills profiles within HR systems, mapping documented experience to the organisation’s skills catalogue and assigning proficiency levels using consistent rules.
Assesses how clearly people explain their technical work against a consistent four-level rubric, producing a human-approved report with quoted evidence behind every score.
Reveals how organisational culture is lived through anonymous employee accounts, producing an evidence-backed diagnostic of shared themes, differences between functions and gaps between values and practice.
Turns a high-potential's assessment evidence into an acceleration plan weighted to real experience and exposure, naming the stretch assignments, mentors and programmes that will compound fastest.
Builds a calibrated, reusable benchmark from source material so every later screen, shortlist or review is graded against the same bar.
Screens candidate evidence against a saved Blueprint, applying the same calibrated bar and traceable reasoning to every applicant.