Competency Matrix

Competency Matrix defines expected skill levels for confirmed roles. It recommends a small set of proficiency levels and attaches competencies to the relevant roles, adding grades only when the user has named them. Its basic workflow is roles, competencies, level expectations and assessment. Links to gap records or training appear only when the user confirms that outcome. It fits the Scale stage of development.

The skill distinguishes setup, import, review, advice and correction requests. A review works from the supplied material without opening an intake questionnaire. Setup or import asks which roles need a model if roles are missing, then asks only questions that would change the result. Unknown competencies, roles and labels remain unknown rather than being invented.

Grade Level means job grade; Expected Level means proficiency. Before asking how many levels exist, the skill clarifies which of those two facts the user means. Confirmed names and counts replace the starting options, so a user-defined four-level system does not receive a five-level default. Country and software are requested only when specific requirements materially affect the output.

Use it for a competency matrix, skills framework, role competency model or capability matrix. It can recommend a model, check existing material, correct confirmed defects or convert a documented process. Advice receives a short recommendation and an offer to build, rather than unsolicited artifacts.

This skill defines expectations per role; it does not assess named people against those expectations or certify competence. A person's actual-versus-expected gap belongs to skill-gap-analysis. Payroll, tax, leave calculations, KPIs, reminders and synchronization are also outside this template's scope. Consequential HR, privacy or legal decisions require a qualified human reviewer.

Inputs include the confirmed roles, competencies and their basis, job grades if applicable, proficiency labels, assessment method and desired outcome. The shared field list contains Competency, Category, Job Title, Grade Level, Expected Level, Description, Assessment Method, Linked Skill Area and Competency ID. It has no money or date columns.

Only requested formats are produced: CSV, SQL DDL, JSON Schema, a Notion property mapping or an Excel workbook. Outputs derive from one field list, retain consistent display names and document normalized SQL identifiers. Machine-readable artifacts are delivered as data. Templates are empty unless examples are explicitly requested, in which case the examples are synthetic. Excel-compatible CSV uses UTF-8 with a byte order mark; it is not a workbook.

Linked Skill Area is a text reference to a separate skill-gap record. The target table is not created by this build, so the field must not become a Notion relation to an invented database. It becomes a foreign key only if that target is actually built in the same artifact set.

Notion output routes to notion-manual-import. Manual mapping requires no connection; authorized workspace changes require verified tools and a verified target. A static mapping is not a completed workspace build, and sensitive review material is repeated only where needed.

We want a consistent way to describe what good looks like per role.