> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/ai-agent-composer/configure-agent-skills.md).

# Configure agent skills

Use **Skills** to configure the application capabilities an agent can use. Add the smallest set needed for its purpose, then verify each skill with controlled inputs.

The Skills tab contains Actions, a skill counter and Add Skill. The screenshot’s 0/20 counter is an example interface state; confirm the limits available in your edition.

### Add a skill and connect its application

<figure><img src="https://3857940684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJcSHU5jP5GABQrGmWvW2%2Fuploads%2FdyehVQ2Awc8CLlbZyNpG%2Fagent-skills.jpg?alt=media&amp;token=be12146e-e068-4724-aa85-0fe1fc1dd4cb" alt="Add Skill connection step, with Connect available and Next disabled"><figcaption></figcaption></figure>

1. Open the agent's **Skills** tab.
2. Select **Add Skill**.
3. Select the intended application and action from the available choices.
4. At **Connect the application to configure skill**, select **Connect** and configure or choose the authorized application connection.
5. Continue with **Next** once the required connection is in place, and complete the remaining configuration shown for that action.
6. Return to the Skills list and verify that the expected capability is present.

The example selects Xurrent → Get Any Object with ID. Complete the application connection before Next becomes available.

If **Next** is disabled at this step, resolve the connection requirement shown by the dialog. Do not substitute a prompt instruction for a missing connection.

### Choose capabilities deliberately

Before adding a skill, answer four questions:

| Question                                   | Why it matters                                                                  |
| ------------------------------------------ | ------------------------------------------------------------------------------- |
| What should this skill do?                 | Keeps a broad application catalogue from becoming an unnecessarily broad agent. |
| Which account and environment will it use? | Prevents a demo agent from reaching the wrong destination.                      |
| Which inputs must the user provide?        | Avoids invented record identifiers or business values.                          |
| What evidence confirms the result?         | Separates a conversational answer from an actual application response.          |

The exact inputs and behavior depend on the selected action. A name such as **Get Any Object with ID** is not a complete contract: inspect the action's configuration and use a real, authorized identifier before testing it.

### Illustrative first skill

For a service-desk assistant, begin with a narrow retrieval task:

> Retrieve a known service record by its identifier and summarize the returned information. If the identifier is missing, ask the user for it. If access fails, explain the failure without inventing a record.

Use this retrieval task for a first test. Ticket creation and account changes require their own input contract, authorized connection and result checks.

### Verify before widening scope

* Test a known accessible item and compare the returned data with the source application.
* Test a missing or invalid input; confirm the agent asks for what it needs or explains the error.
* Test the agent's explanation when the connection lacks access.
* For any skill that changes data, use an approved test destination and verify the actual change.

Compare the returned result with the source application before accepting the task as complete.

### Related capabilities

Skills inside **AI Agent Composer** and tools exposed by the **Autom Mate MCP Server** are separate interfaces. Adding a Composer skill does not establish that an external MCP client has the same tool. For the exposed MCP contracts, see [MCP overview](/userguide/mcp-and-ai-reference/connect-an-ai-client-with-mcp.md).

Open Autom Edit in the agent header and Open in Autom Builder in Logs open the underlying Hyperflow. Use that view when you need to inspect the implementation beyond the Composer settings.