---
title: "Editing and Improving an Existing Skill"
description: "How to refine a skill: locate the step causing unstable results, tighten its wording, add checks, and keep your team in sync."
url: https://help-takeoff.kreo.net/fr/articles/11688708-editing-and-improving-an-existing-skill
collection: "Skills"
updated: 2026-07-25
language: fr
alternates: [en]
---

# Editing and Improving an Existing Skill

How to refine a skill: locate the step causing unstable results, tighten its wording, add checks, and keep your team in sync.

Skills are meant to be refined. The first version rarely behaves perfectly — and that's expected. This article covers how to iterate on a skill until it runs predictably.

## Opening a skill for editing

Go to the **Skills** page (or the Skills section of a project), find the skill, and open it. All components are editable: steps, If/Else conditions, notes, name, description, and tags.

![](https://staticfiles.gleap.io/gattachments/LQQfsuojLgQK7dWFycGAjq2n039hQGzxnI9y6lhrF64Sq8T6QTSRIvVvnWnOBGOeJWTwyc2K9ny.png)

## The improvement loop

1.  **Run the skill** on a real page in a project.
    
2.  **Check the output.** Which parts are correct? Which drift from run to run?
    
3.  **Locate the problem step.** An unstable result almost always traces back to one specific step, not the whole skill.
    
4.  **Tighten the wording of that step.** Make it more specific: name the exact objects, pages, or measurement groups. See [Writing Effective Skill Instructions: Best Practices](https://help-takeoff.kreo.net/en/articles/11688707-writing-effective-skill-instructions-best-practices.md).
    
5.  **Run again.** Repeat until the result is stable.
    

## When to add an If/Else check

If a step behaves correctly most of the time but occasionally slips, don't fight it with wording alone — add an If/Else check after it. The agent will verify the result and redo the step when needed. See [Using If/Else Branching for Quality Control](https://help-takeoff.kreo.net/en/articles/11688703-using-ifelse-branching-for-quality-control.md).

## Keep the team in sync

When you change a skill others use:

-   Update the **notes** on the steps you changed, so teammates see why. See [Adding Notes to Skills for Team Collaboration](https://help-takeoff.kreo.net/en/articles/11688704-adding-notes-to-skills-for-team-collaboration.md).
    
-   Update the **Skill Description** if the skill's behavior or output changed.
    

## Growing a skill

Once individual parts of a workflow run reliably, you can combine them into one larger skill — up to a full cost estimator's workflow, from page search to the final report. Build big skills from proven parts, not from scratch.

## Related

- [Qu'est-ce que les compétences ? Un aperçu](https://help-takeoff.kreo.net/fr/articles/11688700-qu-est-ce-que-les-competences-un-apercu.md)
- [Créer votre première compétence](https://help-takeoff.kreo.net/fr/articles/11688701-creer-votre-premiere-competence.md)
- [Skill Steps: How to Describe Tasks](https://help-takeoff.kreo.net/fr/articles/11688702-skill-steps-how-to-describe-tasks.md)
- [Utilisation de la ramification If/Else pour le contrôle de qualité](https://help-takeoff.kreo.net/fr/articles/11688703-utilisation-de-la-ramification-ifelse-pour-le-controle-de-qualite.md)
- [Adding Notes to Skills for Team Collaboration](https://help-takeoff.kreo.net/fr/articles/11688704-adding-notes-to-skills-for-team-collaboration.md)