This guide explains how to change an existing AI Skill without breaking the version your team uses every day. It is intended for organization administrators. If you are new to skills, start with AI Skills first.

A skill is not a list of independent settings. It is one coherent workflow description written in natural language. Changing a sentence at the end of a skill can influence how the agent behaves at the beginning. And because your team is already using the skill in production, an untested change is visible to everyone immediately.

The four steps below keep your working version intact while you build and test the new one.

You find your skills in Bliro under Settings > Organisation > Skills. Only organization administrators can create, edit, or deactivate them, and every change applies to the entire organization.

Never edit a live skill directly. Always work on a copy. How you create that copy depends on the type of skill.

Skills provided by Bliro. System skills that ship with Bliro have a Duplicate button in the top right corner of the skill. Click it and you get a full copy.

Your own custom skills. Custom skills do not have a Duplicate button. Create the copy manually:

However you created it, rename the copy so you can tell the versions apart, for example by adding -v1 to the name. Leave the copy deactivated, or give it a test trigger right away as described in Step 3, so that it does not compete with the live skill while you are still editing.

You now have a working skill that keeps running for your team, and a copy you can experiment with. If an edit goes wrong, you simply delete the copy and nothing is lost.

Edit the instructions of the new version. Two things are worth knowing before you start.

Let an AI assistant help you stay coherent. Because a skill is one connected workflow, a change in one place often needs a matching change somewhere else. A practical approach is to copy the full skill text into an AI assistant such as Claude, Gemini, or ChatGPT, describe the change you want, and ask it to apply the change everywhere it is needed. A well prompted assistant spots contradictions between the steps and keeps the whole skill consistent.

Check the tools your skill refers to. Skills work by calling tools, for example a tool that creates a new account object in your CRM. Tools are referenced by their ID and written in backticks inside the instructions, such as crm:create_account. A tool ID that does not exist increases the likelihood of the agent making mistakes calling that tool. Every skill ends with a short checklist of the tools it mentions. Use that checklist to confirm each tool ID is valid before you test.

Each skill has a description. The description is what the Bliro assistant uses to decide when the skill should be triggered. If your new version keeps the same description as the original, both skills compete for the same request and you cannot tell which one answered.

Give the new version a temporary description with a narrow trigger of your own invention, for example:

Trigger this skill when the user says "Hakuna Matata".

Now the original skill keeps serving your team on its normal trigger, while you reach the new version with your test phrase. Run it a few times, including the edge cases that matter to your process, and check the result end to end in the target system.

Once the new version behaves the way you want:

Keep the old version deactivated for a while rather than deleting it right away. If something unexpected shows up in daily use, you can switch back within seconds.

Questions about updating a skill, or want support with a larger rework? Contact [email protected] or your Customer Success Manager.