Talent & Leadership

Build skills catalogue

Codes recurring themes from a set of role and framework documents into a levelled skills catalogue, with a review pause before it's finalised.

  • Talent & Leadership
  • Human review built in
  • Traceable reasoning
  • Runs anywhere
Preview methodology

2–3 weeks ~15 minutes

For a typical multi-document review workflow

No coding required

Input
Role profiles and framework documents as a set
Output
A levelled skills catalogue
Runs in
Skillsize · ChatGPT · Claude · Copilot
Export
SKILL.md · MCP
Time saved
~2–3 weeks per run

— USE CASES

What people use Build skills catalogue for

Standing up a skills taxonomy

Build the first levelled catalogue from documents you already hold rather than from a vendor's generic library.

Consolidating inherited frameworks

Merge overlapping frameworks from different functions or acquired entities into one levelled structure.

Keeping the catalogue current

Re-run against updated role documents so the catalogue is maintained rather than rebuilt.

What it works from

  • Role profiles and framework documents as a set
  • Your level definitions and house terminology
  • Any skills you require to be retained

What you get back

  • A levelled skills catalogue
  • Themes coded consistently across every source document
  • A human review point before the catalogue is finalised

— HOW IT BEHAVES

How Build skills catalogue produces its result

The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.

Whole document sets at once

A folder of material is processed as one set, so cross-document patterns surface instead of being read one file at a time.

Clarified before it runs

Ambiguities are settled with you up front, so the run does not quietly assume the wrong scope.

Human review gate

The run pauses for a person to confirm the facts that matter before the deliverable is composed.

Composed as work product

Findings are written up as a document that reads like professional output rather than raw model text.

Enriched row by row

Each row gains derived columns from the analysis, keeping the source data and the judgement side by side.

Delivered as a working table

Results land as a clean table you can sort, filter or drop straight into the deliverable.

Why this is expensive by hand

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.

How this Skill produces it

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.

Who it's for

  • Independent consultants codifying their own methodology
  • Strategy and transformation teams standardising delivery
  • Internal advisory functions under pressure to produce faster
  • Operators who need defensible output, not a one-off chat answer

Run it in Skillsize — or export it anywhere

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.

ChatGPTClaudeCopilotAI Products (MCP)

More Talent & Leadership Skills

Browse the full library →