---
title: "Creating Your First Skill"
description: "A step-by-step guide to building your first skill: describing steps, adding If/Else checks, naming, tagging, and testing it on a real page."
url: https://help-takeoff.kreo.net/en/articles/11688701-creating-your-first-skill
collection: "Skills"
updated: 2026-07-26
language: en
alternates: [fr]
---

# Creating Your First Skill

A step-by-step guide to building your first skill: describing steps, adding If/Else checks, naming, tagging, and testing it on a real page.

This article walks you through creating a skill from scratch. For an introduction to what skills are, see What Are Skills? An Overview.

## Before you start

Pick a simple process you repeat often — three to five steps is a good size for a first skill. For example: find all pages with floor plans and prepare them for work. You can build longer workflows later.

## Step 1. Open the skill editor

There are two ways to create a skill:

-   Go to the **Skills** page and click **Create Skill**, or
    
-   Open any project, go to the **Skills** section, and click **Create Skill**.
    

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

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

## Step 2. Describe the steps

Add your steps one by one. Each step is one task written in plain text — no programming needed. You can write in business language or technical language, whichever suits you.

Examples of steps:

-   "Find all pages that contain floor plans"
    
-   "Analyze my measurements"
    
-   "Create a report"
    

Keep each step to a single task: one action — one step. See [Skill Steps: How to Describe Tasks](https://help-takeoff.kreo.net/en/articles/11688702-skill-steps-how-to-describe-tasks.md) for details.

![](https://staticfiles.gleap.io/gattachments/okCMANIk6ABXm7FPbiDJIBhEELixhjjky3IxIqqOBy08mDVs1y5MKp2pCYvrjawjzrabCmdoA5Y.gif)

## Step 3. Add If/Else where quality matters

Where a mistake would cost the most, add an **If/Else** control point: the agent will check the result of a step before moving on, and send it back for a redo if something is off. See [Using If/Else Branching for Quality Control](https://help-takeoff.kreo.net/en/articles/11688703-using-ifelse-branching-for-quality-control.md).

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

## Step 4. Name and tag the skill

Give the skill a **name**, a **Skill Description**, and **tags** (comma-separated). This makes it easy to find and reuse in future projects. See [Naming, Describing, and Tagging Skills](https://help-takeoff.kreo.net/en/articles/11688705-naming-describing-and-tagging-skills.md).

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

## Step 5. Run it and check the result

Launch the skill on a real page in your project and review the output. If a step produces an unstable result, tighten its wording and run again. A couple of iterations is normal — see [Writing Effective Skill Instructions: Best Practices](https://help-takeoff.kreo.net/en/articles/11688707-writing-effective-skill-instructions-best-practices.md).

## Related

- [What Are Skills? An Overview](https://help-takeoff.kreo.net/en/articles/11688700-what-are-skills-an-overview.md)
- [Skill Steps: How to Describe Tasks](https://help-takeoff.kreo.net/en/articles/11688702-skill-steps-how-to-describe-tasks.md)
- [Using If/Else Branching for Quality Control](https://help-takeoff.kreo.net/en/articles/11688703-using-ifelse-branching-for-quality-control.md)
- [Adding Notes to Skills for Team Collaboration](https://help-takeoff.kreo.net/en/articles/11688704-adding-notes-to-skills-for-team-collaboration.md)
- [Naming, Describing, and Tagging Skills](https://help-takeoff.kreo.net/en/articles/11688705-naming-describing-and-tagging-skills.md)