---
title: "Edit existing skills in SkillPanel"
canonical: "https://help.skillpanel.com/space/TBG/2893348874/Edit%20existing%20skills%20in%20SkillPanel"
format: markdown
---
**Why:** editing skills keeps your organization’s skills graph accurate and relevant. Updated relationships, names, and descriptions improve role matching, analytics, and learning recommendations.

---

## When to use this

- updating a skill’s definition or description
- linking related or prerequisite skills
- hiding or disabling outdated competencies
- correcting naming inconsistencies

---

## Prerequisites

- Manager rights in **Skills directory**
- access to either **Skills Manager** or **Skills Map**
- clear naming rules for your skill taxonomy

---

## Quick start

1. Go to **Skills directory → Skills manager**.
2. Find the skill using the **search bar** or expand the relevant skill group.
3. Click the **three dots** next to the skill → select **Edit**.
4. Update the name, description, or relationships.
5. Click **Save skill** to confirm.

---

## Detailed steps

### 1. Edit skills from the Skills Manager

- Navigate to **Skills manager**.
- Use the **search bar** (yellow rectangle) or browse manually.
- Click the **three-dot icon** (red arrow) next to a skill.
- Choose from the menu: **View details**, **Edit**, **Hide skill**, or **Disable skill** (green arrow).

**Why this matters:** hiding or disabling unused skills keeps your directory clean and avoids confusion in assessments.

![image-20251008-100503.png](media://92970e92-2104-4c75-b676-51cf8f5d13cd)

**Why this matters:** hiding or disabling unused skills keeps your directory clean and avoids confusion in assessments.

After clicking **Edit**, a pop-up window opens:

- Use **+ Add relation** (red arrow) to connect the skill with others (e.g., *requires*, *is prerequisite for*, *counterpart*).
- Edit the skill name or description.
- Click **Save skill** (yellow arrow) when done.**Skills Manager**

![image-20251008-100639.png](media://f8027340-a19d-4113-87fe-92dd58cdafb8)

### 2. Edit skills from the Skills Map

- Go to **Skills directory → Skills map**.
- Use the **search bar** to find a skill or locate it directly on the map.
- Select the skill. A preview panel opens on the right.
- Click the skill name (red arrow) to view full details.

![image-20251008-100723.png](media://8720b5f0-39e6-4709-8594-5cd86fd10e72)

In the skill panel:

- Click the **three-dot icon** (yellow arrow) → choose **Edit skill** (red arrow).
- The edit window allows you to update the same fields as in Skills Manager:
  - add relationships via **+ Add relation**
  - rename or re-describe the skill
  - adjust dependencies
- Click **Save skill** to apply changes.

**Why this matters:** editing from the map gives visual context—useful when checking dependencies or related domains.

![image-20251008-100809.png](media://7d8bbb87-0b05-4362-833d-0e6fd5e45cbb)

### 3. Naming rules

When adding or renaming skills:

- Names must be **specific and self-explanatory** (e.g., “pytest,” not “Testing”).
- Avoid repeating branch or category names (the skill stands alone).
- Keep language clear enough for new hires to understand during onboarding.

---

## Use the product to go faster / safer / clearer

| Step | Feature | Benefit | How? |
| --- | --- | --- | --- |
| Skill lookup | Global search + filters | Locate skills instantly in large frameworks | Type part of a name or toggle “Show hidden” |
| Edit context | Skills Manager & Map views | Choose between structured or visual editing | Manager = list-based precision; Map = visual relationships |
| Relationship linking | Add relation types | Build logical skill dependencies | Select from “requires,” “is prerequisite for,” or “counterpart” |
| Access control | Manager rights | Prevent unauthorized edits | Only authorized users can modify or rename skills |

---

## Examples

**Example 1**  
A skill “Advanced Maths” needs to reference “Basic Maths.”  
→ Add relation: *Requires → Basic Maths*.  
Result: future job positions automatically recognize this dependency.

**Example 2**  
“Java Fundamentals” becomes “Core Java Programming.”  
→ Update name and description; save.  
Result: skill remains linked to existing roles without duplication.

---

## FAQ

**Q:** What’s the difference between hiding and disabling a skill?  
**A:** Hidden skills stay visible to managers; disabled ones are removed from all mappings.

**Q:** Can I add a new relation type?  
**A:** No, relation types are predefined in the platform.

**Q:** Why can’t I see the Edit option?  
**A:** You need Manager rights in the **Skills directory**.

**Q:** Will editing a skill affect existing job positions?  
**A:** Yes, updates sync automatically across related skillsets and positions.

---

## Pitfalls & tradeoffs

- Don’t rename a skill casually, because renames cascade through linked job positions.
- Avoid adding redundant relations (e.g., circular dependencies).
- Keep descriptions factual; avoid project- or tool-specific notes.
- Editing too many skills at once can break consistency—review hierarchy after major updates.