Skills Catalog
The Skills Catalog brings together, in one place, the technical and soft competencies your company wants to track (for example "Advanced Excel", "Customer Service" or "Forklift Operation"). It's not used on its own: it's the shared base that Positions (what skills a job requires), Employees and Candidates (what skills they have) and Performance Evaluations (how well they master them) all draw from, so you can compare what's required against what's real.
What is it and what is it for?
Each catalog record is a single skill or competency, with a Type that classifies it (for example "Technical", "Language" or "Soft skill"), a free-text description and an evaluation criteria that explains how that skill is measured or graded. On its own, a skill says nothing about a specific person or job: its value comes from being linked from other screens in the system.
With the Enterprise Human Resources (HHRR) module active, that link enables automatic comparisons — such as a Position's radar chart comparing the skills the job requires against those a specific employee or candidate has — and gap reports that tell you exactly what someone is missing to fill a position.
Where the catalog is used
| Screen | What it does with skills |
|---|---|
| Positions | The "Skills" tab of a Position (requires HHRR) lets you define which skills the job requires and the expected level for each. AdmCloud can suggest these skills for you with Artificial Intelligence based on the job title. |
| Employees | An employee's record lists their registered skills, along with type, evaluation criteria and level reached. |
| Candidates | A candidate's record lists their skills the same way, so they can be compared against what the job opening they're applying to requires. |
| Performance Evaluations | When evaluating an employee, you can grade their level on each relevant skill, leaving a historical record of their progress. |
| Reports | The Skills Catalog itself, "Positions with Skills", "Employee Skills", "Candidate Skills", and the gap reports ("Employee/Candidate Position Skills Gap") that compare what's required against what's real. |
How to use it, step by step
- Register the skill in the catalog (the "Skills" menu), filling in its Name, Type, Description and Evaluation Criteria. You can also let it be created automatically from a Position (see the next step).
- Assign it to a Position that requires it, with the Enterprise HHRR module active: from the job's "Skills" tab, add it manually or use the AI suggestion based on the job title — AdmCloud proposes a list of typical skills with their type and evaluation criteria, and accepting them creates in the catalog any that don't exist yet.
- Record it on an Employee's or Candidate's profile with the level they actually have, to document their real competency.
- Grade it on a Performance Evaluation when appropriate, to track how that skill evolves over time.
- Check the gap reports ("Skills Gap") to see, position by position or employee by employee, which skills are missing or below the expected level.
Key capabilities
- Classification by Type with a color and initial: every skill shows a small avatar with its Type's initial and an automatically assigned color, so you can spot at a glance which family it belongs to (technical, language, soft skill...) in any list where it appears.
- Reusable evaluation criteria: the text explaining how to grade the skill travels with it to Positions, Employees, Candidates and Performance Evaluations, so everyone grades against the same criteria.
- AI skill suggestions: when creating or editing a Position (with HHRR active), you can ask AI to suggest the typical skills for a job based on its title, review the proposed list, check only the ones you want and create them all at once in the catalog (or fill in the evaluation criteria of one that already existed but didn't have one).
- One catalog, many uses: the same skill is reused across Positions, Employees, Candidates and Performance Evaluations, avoiding separate duplicate catalogs on every screen.
- Protected against deletion while in use: you can't delete a skill while it's still assigned to a Candidate, a Position, an Employee or an HR transaction; the system tells you exactly which records are using it.
Key fields
| Field | What it's for |
|---|---|
| Name | The skill's name (for example "Advanced Excel"). Required and unique: it can't be repeated in the catalog. |
| Type | A free-text category to group similar skills (for example "Technical", "Language", "Soft skill"). Determines the color and initial of the avatar that identifies it in lists. |
| Description | Free text explaining what the skill consists of. |
| Evaluation Criteria | How the skill is measured or graded when assigned to a Position, an Employee, a Candidate or a Performance Evaluation. |
| Notes | Additional internal comments about the skill. |
Validations on save
- The name is required and can't exceed 50 characters.
- The name must be unique. If a skill with that exact name already exists, saving is rejected, indicating the record already exists.
- The type can't exceed 50 characters either.
- A skill in use can't be deleted: if it's assigned to a Candidate, a Position, an Employee or an HR transaction (for example a Performance Evaluation), the system blocks deletion and lists the affected records.
Availability
- The Skills Catalog requires the Enterprise Human Resources (HHRR) module active on your company. Without this module, the screen and its links from Positions, Employees, Candidates and Performance Evaluations are not available.
- It also requires the "Skills" permission assigned to your user group to view, create, edit or delete records, depending on the level granted.
- The AI skill suggestion depends on a feature that must be enabled for your company; if you don't see the option, you can still create skills manually from the catalog or from a Position.
Tips and common mistakes
Let AI jump-start the catalog for you. When creating a new Position, use the skill suggestion with the job title: it saves you from typing the Type, Name and Evaluation Criteria of the most common skills for that role.
Use the same Type consistently (for example always "Language", not sometimes "Languages"), since the color avatar and the groupings in selection lists rely on the Type's exact text.
"Can't delete due to dependencies": before deleting a skill, remove it from any Positions, Employees, Candidates or Performance Evaluations where it's assigned; the error message tells you which records still use it.