Team Skill Base
Skills only one engineer holds. Losing them (leave, departure) leaves no cover — consider cross-training or hiring.
How many engineers hold each recorded skill, and how many are Advanced or Expert.
Engineers across the top, skills down the side. ✓ = verified. Tap an engineer's name to open their profile.
Skill-first: pick a product and the tasks to be done (their requirements come from the Task skills mapping) and / or a skill directly. Engineers who lack a required skill are not listed as candidates; holding it below the requested level shows as partially met and never counts toward "X of Y". Dates are optional — without them availability is simply not assessed. Never a percentage; you always decide.
What each CMCT catalog task requires from an engineer, as skills from the taxonomy (optionally with a minimum level). Product-level links apply to every task of the product; task links add to them. A task with nothing linked shows "not configured" in Find engineers — it never qualifies anyone by default, and the catalog's L1–L5 level is a hint only, never translated into a skill level.
Two levels: category → skill. Vendor and product are fields on a skill. Archiving hides a skill from new entries but keeps existing records intact.