---
schema_version: "1"
id: 48e685646884018ceea417573a0dc972839d29285f2921bbaf4ff23d627a0251
title: Using Skills with MuleSoft Vibes
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-code-builder/vibes-skills.md
canonical_url: https://docs.mulesoft.com/anypoint-code-builder/vibes-skills
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 431b202e6f3dfddb1feb8dc01d3a931333b25c83581b436cfd530e13a3dc8688
description: MuleSoft Documentation Site
latest: true
---
---
product: Anypoint Code Builder
version: master
---

# Using Skills with MuleSoft Vibes

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Skills are reusable instruction sets that MuleSoft Vibes activates only when they apply to your
task. Each skill packages guidance and optional resources so MuleSoft Vibes can follow a consistent
workflow without loading that material for unrelated messages.

When your request matches a skill’s description, MuleSoft Vibes uses the `use_skill` tool to load
the full instructions and run them for that task. Unlike workspace rules that stay active across
conversations, skills load as needed, which leaves more context available for other work.

MuleSoft publishes Mule development skills from the `mulesoft-dx` repository as the
`@salesforce/mulesoft-vibes-skills` package so you can use them across agents such as MuleSoft
Vibes, Claude Code, Cursor, Cline, and Codex.

**Default skills** are preloaded in MuleSoft Vibes and enabled by default. You can turn on and off
each default skill individually. **Workspace skills** are available only in the workspace or project
where they’re defined. **Global skills** are available in every project and workspace.

## Manage Default Skills in MuleSoft Vibes

Default skills are available automatically when you use MuleSoft Vibes where the feature is
supported.

> [!NOTE] When you use MuleSoft Vibes, Anypoint Code Builder automatically installs or updates
> Anypoint CLI after you restart VS Code. Some skills, such as `build-mule-integration` and
> `upgrade-mule-app`, require Anypoint CLI. When you use skills with Claude Code or another agent
> instead, you must install Anypoint CLI manually before using skills. See
> [Install MuleSoft Skills in Claude Code](#install-mulesoft-skills-in-claude-code).

Use MuleSoft Vibes settings to turn on and off each default skill based on your workflow.

## Set Up Skills in Your Project

To add **workspace skills** to a project, add skills under `.a4drules/skills/` in your workspace.
Each skill is a directory whose name matches the skill. The directory contains a `SKILL.md` file
with the instructions (and optional YAML frontmatter for metadata). You can add supporting material
in subfolders such as `references/`, `assets/`, or `scripts/` inside that skill directory.

Commit `.a4drules/skills/` with your project so everyone who uses the repository gets the same
skills. To share workspace rules and skills from GitHub, see
[Sharing Rules and Skills from GitHub with MuleSoft Vibes](https://docs.mulesoft.com/anypoint-code-builder/vibes-share-rules-skills-github).

## Install MuleSoft Skills in Claude Code

These steps are written for Claude Code and also apply to other supported agents that use the same
installer flow.

Before you install skills, create a connected app and authenticate Anypoint CLI:

- `anypoint-cli-v4 conf client_id {myClientID}`

- `anypoint-cli-v4 conf client_secret {myClientSecret}`

  For more information, see
  [Authentication to the Anypoint Platform CLI](https://docs.mulesoft.com/anypoint-cli/latest/auth).

To install MuleSoft skills:

1.  Make sure Node.js is installed.

2.  Install the `anypoint-cli-dx-mule-plugin` version 1.3.0 or later.

3.  Run:

    `npx skills add mulesoft/mulesoft-dx/skills/mule-development`

4.  Select the skills you want to install.

5.  Select the agent targets for the installation:

    - Keep **Universal (`.agents/skills`)** selected. It is always included by the installer.

    - Select **Claude Code (`.claude/skills`)** under **Additional agents**.

6.  Select a scope:

    - **Project** installs in the current directory so you can commit the skills with your project.

    - **Global** makes the skills available to all instances of supported agents.

7.  Select an installation method:

    - **Symlink (Recommended)** installs one shared copy for all selected agent types.

    - **Copy to all agents** installs independent copies for each selected agent type.

8.  Confirm the installation by typing `yes`.

> [!NOTE] Use `mulesoft/mulesoft-dx/skills/mule-development` in the `install` command. The shorter
> `mulesoft/mulesoft-dx` path doesn’t resolve the nested skills directory.

## MuleSoft Skills Catalog

The default MuleSoft skills set includes:

<table><colgroup><col> <col></colgroup><thead><tr><th>Skill Name</th><th>Description</th></tr></thead><tbody><tr><td><p><code>author-governance-ruleset</code></p></td><td><p>Create, update, or validate an Anypoint API Governance ruleset for API specifications, API instances, and MCP servers.</p></td></tr><tr><td><p><code>build-agent-broker-project</code></p></td><td><p>Build, edit, validate, publish, and deploy an Agent Broker project for Agent Network 2.0.</p></td></tr><tr><td><p><code>build-mule-integration</code></p></td><td><p>Create, update, or fix a Mule flow, subflow, or component. This skill runs a validation script at startup to check whether <code>anypoint-cli-dx-mule-plugin</code> is installed.</p></td></tr><tr><td><p><code>create-mule-run-config</code></p></td><td><p>Create a new Anypoint Code Builder run configuration.</p></td></tr><tr><td><p><code>delete-mule-run-config</code></p></td><td><p>Delete an existing Anypoint Code Builder run configuration.</p></td></tr><tr><td><p><code>develop-pdk-policy</code></p></td><td><p>Scaffold, configure, build, test locally, and publish a custom Omni Gateway policy with the Policy Development Kit (PDK).</p></td></tr><tr><td><p><code>execute-mule-run-config</code></p></td><td><p>Run or debug a Mule application by using an existing Anypoint Code Builder run configuration.</p></td></tr><tr><td><p><code>generate-doc-description</code></p></td><td><p>Add or update <code>doc:description</code> attributes in Mule XML configuration files.</p></td></tr><tr><td><p><code>manage-api-version</code></p></td><td><p>Read, check for updates, and change the version of API dependencies in a Mule project.</p></td></tr><tr><td><p><code>manage-global-configurations</code></p></td><td><p>Create, edit, delete, list, validate, and consolidate global configuration elements in a Mule project. Covers connector configs, TLS Context, Object Store, Caching Strategy, Global Error Handler, API AutoDiscovery, Import Project Reference, properties files, global-property elements, and multi-environment setup.</p></td></tr><tr><td><p><code>pdk-prerequisites</code></p></td><td><p>Verify and install the tools required to develop custom Omni Gateway policies with the Policy Development Kit (PDK).</p></td></tr><tr><td><p><code>pdk-templates</code></p></td><td><p>Apply Policy Development Kit (PDK) code templates for common Omni Gateway custom policy features.</p></td></tr><tr><td><p><code>pdk-test</code></p></td><td><p>Write and run Docker-based integration tests for a custom Omni Gateway policy.</p></td></tr><tr><td><p><code>pdk-unit</code></p></td><td><p>Write and run unit tests for a custom Omni Gateway policy built with the Policy Development Kit (PDK).</p></td></tr><tr><td><p><code>run-system-diagnostics</code></p></td><td><p>Run Anypoint Code Builder system diagnostics, including RAM, CPU, IOPS, and Windows optimizations.</p></td></tr><tr><td><p><code>secure-mule-app</code></p></td><td><p>Configure and implement Mule secure properties to encrypt sensitive data.</p></td></tr><tr><td><p><code>translate-agent-broker-old-to-new-project</code></p></td><td><p>Convert an Agent Network 1.0 project into an Agent Network 2.0 project.</p></td></tr><tr><td><p><code>update-mule-run-config</code></p></td><td><p>Edit an existing Anypoint Code Builder run configuration.</p></td></tr><tr><td><p><code>upgrade-mule-app</code></p></td><td><p>Upgrade a Mule application to a later Mule runtime version and Java version.</p></td></tr></tbody></table>

> [!NOTE] The `upgrade-mule-app` skill requires a Mule application on Mule 4.3 or later. It also
> requires `@salesforce/anypoint-cli-dx-mule-plugin` version 1.3.0 or later, which auto-provisions
> the source and target JDKs during the upgrade. To update the plugin, run:
>
> `npm install -g @salesforce/anypoint-cli-dx-mule-plugin@latest`

## Skills and MCP Tools

Model Context Protocol (MCP) servers expose **tools** that perform actions, such as generating a
flow or calling an API. **Skills** supply structured instructions and workflows the assistant
follows when a task matches the skill. You typically use both: tools carry out operations, while
skills guide how and when to apply them for specific scenarios.

For configuring MCP servers in Anypoint Code Builder, see
[Configuring an MCP Server](https://docs.mulesoft.com/anypoint-code-builder/vibes-mcp-server).

## See Also

- [MuleSoft Vibes Overview](https://docs.mulesoft.com/anypoint-code-builder/mulesoft-vibes)

- [MuleSoft Vibes for Anypoint Code Builder](https://docs.mulesoft.com/anypoint-code-builder/vibes-get-started)

- [Sharing Rules and Skills from GitHub with MuleSoft Vibes](https://docs.mulesoft.com/anypoint-code-builder/vibes-share-rules-skills-github)

- [Configuring an MCP Server](https://docs.mulesoft.com/anypoint-code-builder/vibes-mcp-server)

- [Troubleshooting AI Features in Anypoint Code Builder](https://docs.mulesoft.com/anypoint-code-builder/troubleshoot-generative-ai)
