Skills - SkillsDB

Quick Summary: A skill is a company-level definition: a name, a description, and its usage across careers and people. What a person scores on a skill is a person skill in Team Data. What a skill is configured as on a career — its benchmark, Required status and per-level activation — belongs to the career.

The resources

Resource	What it is
Skill	The company-level definition: identity, description, usage, versions and activity
Skill request	The workflow by which someone asks for a skill to be added to the library

One definition, three places it is used

A single skill definition is referenced from three directions, and keeping them distinct is the thing to get right:

Where	What it means	Resource
The library	The definition itself — name, description, version history	Skill
On a career	The benchmark, Required status and per-level activation for that career	Career
On a person	The self and manager grades, benchmark and flags for that person	Person skill

Changing the library definition never rewrites a grade. Skills are versioned, and a training completed against an earlier version is identifiably stale rather than silently valid.

Adding to the library

A skill request proposes a name and description. Approving it creates the skill and assigns it to the requester; rejecting it records the decision. Either way the decision is final — deciding a decided request returns a conflict.

Activity

GET /api/v1/skills/{id}/activity is a version log, not a change feed — exactly three event types (baseline, version_created, renew_training). See the activity event envelope for the shared shape.