# Creating Skills

Skills are created by builders and admins. You can create a skill from the skill management page, or directly from within an agent chat session.

### Creating a Skill from the Skill Page

1. Navigate to the skills section in your project
2. Click **Create Skill**
3. Fill in the skill details:
   * **Name** — A clear, descriptive name (e.g. "Order Processing", "Quote Generation")
   * **Description** — What the skill does. If you leave this empty, a description is auto-generated when you leave the page.
   * **Instructions** — The core of the skill: detailed instructions telling the agent what to do, how to behave, and what output to produce.

### Creating a Skill from Agent Chat

You can also ask the agent to create a skill during a conversation. For example:

* *"Create a skill that processes incoming purchase orders from email attachments"*
* *"Turn what you just did into a reusable skill"*

The agent will generate the skill configuration and save it. You'll see visual feedback in the chat showing the skill being created.

### Adding Components

Once a skill exists, you can add components that give it access to external systems and data:

#### Integrations

Connect apps that the skill needs to use. When you add an integration:

1. Select the integration app (e.g. Gmail, Business Central, Slack)
2. Connect your account if not already connected
3. The agent gains access to that app's actions when running the skill

Credentials are attached to the skill and honoured at runtime — the agent only uses the credentials scoped to the skill, not any others in the project.

#### Knowledge Bases

Attach knowledge bases that the skill should be able to search:

1. Select an existing knowledge base or create a new one
2. Upload relevant documents (PDFs, Word docs, spreadsheets, etc.)
3. The agent can query this knowledge base when the skill runs

This is useful for skills that need reference data — product catalogues, pricing rules, policy documents, or technical manuals.

#### Data Tables

Connect data tables that the skill should read from or write to. Data tables provide structured, queryable data that the agent can use during skill execution.

### Publishing a Skill

A skill must be **published** before operators can use it. Before publishing, the skill must have:

* A **description**
* **Instructions**

Draft skills are only visible to builders and admins. Once published, the skill becomes available to all operators in the project (unless disabled).

### Version History

Skills maintain a version history. Each time you update a published skill, a new version is created. You can view the version history inline above the skill to see what changed and when.

### Managing Skills

From the skill detail page, you can:

* **Edit** the skill's instructions, description, and components
* **Enable / disable** the skill for the current project
* **View version history** to see past changes
* **Delete** the skill if it's no longer needed

> 💡 Operators never see draft or disabled skills. They only interact with published, enabled skills through the agent.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lleverage.ai/operator-agent/skills/creating-skills.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.