The Skill Request object - SkillsDB

Quick Summary: A skill request proposes a name and description for a new library skill. Approving it creates the skill and assigns it to the requester; rejecting it records the decision. Either way the decision is final — a decided request returns a conflict if decided again.

Attributes

Field	Type	Description
`id`	string	Opaque request id
`name`	string \| null	The requested skill name
`description`	string \| null	The requested description
`status`	string	`pending`, `approved` or `rejected`
`requestedById`	string \| null	Person id who requested the skill
`requestedAt`	string \| null	When it was requested (ISO 8601 UTC)
`reviewedById`	string \| null	Person id who decided it, once decided
`decidedAt`	string \| null	When it was decided
`reviewNotes`	string \| null	The `reason` given when the request was decided, if any

{
  "id": "17",
  "name": "Hydraulic Systems",
  "description": "Maintenance of hydraulic power units.",
  "status": "approved",
  "requestedById": "91",
  "requestedAt": "2026-03-01T09:00:00.000Z",
  "reviewedById": "88",
  "decidedAt": "2026-03-02T14:00:00.000Z",
  "reviewNotes": "Approved for the fabrication track."
}

Workflow

POST /api/v1/skill-requests submits a proposed name and description. The request starts pending.
POST /api/v1/skill-requests/{id}/approve accepts it, with an optional reason. Approving creates the skill in the library and assigns it to the requester.
POST /api/v1/skill-requests/{id}/reject declines it, with an optional reason — the same field name every rejection in this API takes. (notes is accepted as a deprecated alias.)

Filter the list with status=pending|approved|rejected. The underlying record also carries a category and a free-text category suggestion; both are deprecated and neither is exposed.