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.
A folder of material is processed as one set, so cross-document patterns surface instead of being read one file at a time.
Ambiguities are settled with you up front, so the run does not quietly assume the wrong scope.
The run pauses for a person to confirm the facts that matter before the deliverable is composed.
Findings are written up as a document that reads like professional output rather than raw model text.
Each row gains derived columns from the analysis, keeping the source data and the judgement side by side.
Results 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.
Build a competency framework
Groups and merges skills from role profiles, standards and existing drafts into a single structured, consistently worded competency framework.
Role benchmark research
Researches how a role is defined externally and reshapes the findings into a structured benchmark you can hold your own definition against.
Potential and readiness
Assesses potential and readiness separately against calibrated criteria, showing the supporting evidence behind each bucket for talent review discussions.