Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions modules/ROOT/nav.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,7 @@
** xref:vibes-workflows-commands.adoc[]
** xref:vibes-conversation-history.adoc[]
** xref:vibes-mcp-server.adoc[]
** xref:vibes-skills.adoc[]
** xref:vibes-api-ai-create-spec.adoc[]
** xref:vibes-create-integrations.adoc[]
** xref:vibes-prompt-examples.adoc[]
Expand Down
7 changes: 5 additions & 2 deletions modules/ROOT/pages/mulesoft-vibes.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,8 @@ MuleSoft Vibes integrates with the xref:mulesoft-mcp-server::index.adoc[MuleSoft
* Deploying and managing instances
* Securing your applications

You can also use xref:vibes-skills.adoc[skills], reusable instruction sets that Agentforce activates when your task matches a skill's description. Agentforce uses the `use_skill` tool to load and run a skill's full instructions when your task matches that skill.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is small distinction between skill being supported as feature vs. allowing the option to enable/disable individual skills (toggle).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bpolat1, you're right that it's not the same, but what would be the use of highlighting the support of "skills" if the "Skill" toggle is not on? Am I missing something? Can you elaborate? Thanks!

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So the "Skills" capability will always be available with this release (the red box). Whereas the "skills" (blue box) for global or workspace are user-created and they can be edited, disabled/enabled, or removed.

Image

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Please ignore the "Salesforce Skills" section for now. That is not part of this release)

Copy link
Copy Markdown
Contributor Author

@Crispy-Salesforce Crispy-Salesforce Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bpolat1, can you elaborate on the difference between "Global Skills" and "Workspace Skills"? Is the information included in this PR not enough? Thanks!

These features are powered by large language models (LLMs) that operate within the Salesforce Shared Trust Boundary.

MuleSoft Vibes is part of the broader MuleSoft AI ecosystem, which also includes capabilities such as Map with AI and Map and Transform with AI. For an overview of all MuleSoft AI features, see the xref:general::learning-map-mulesoft-ai.adoc[Learning Map: MuleSoft AI].
Expand All @@ -36,5 +38,6 @@ NOTE: Authentication happens through the user logged in to Anypoint Code Builder

== See Also

* xref:troubleshoot-generative-ai.adoc[Troubleshooting MuleSoft Vibes]
* xref:mulesoft-mcp-server::index.adoc[MuleSoft MCP Server]
* xref:vibes-skills.adoc[]
* xref:troubleshoot-generative-ai.adoc[]
* xref:mulesoft-mcp-server::index.adoc[]
6 changes: 5 additions & 1 deletion modules/ROOT/pages/vibes-get-started.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ To ensure the best results:
* Make sure MuleSoft Vibes is invoking these specialized tools.
* Verify that all required prerequisites for MuleSoft Vibes and MCP Server are enabled in your environment.

For more information about how MuleSoft’s AI generation pipelines work, see the https://blogs.mulesoft.com/automation/how-mulesoft-turns-generative-output-into-value/[MuleSoft research blog^].
For more information about how MuleSoft AI generation pipelines work, see the https://blogs.mulesoft.com/automation/how-mulesoft-turns-generative-output-into-value/[MuleSoft research blog].


== Provide MuleSoft Vibes with Context
Expand Down Expand Up @@ -83,3 +83,7 @@ The available options include:
* *Execute safe commands*: Allow MuleSoft Vibes to execute safe terminal commands.
* *Execute all commands*: Allow MuleSoft Vibes to execute any terminal command.
* *Use the browser*: Allow MuleSoft Vibes to launch and interact with websites in a browser.

== Skills in MuleSoft Vibes

xref:vibes-skills.adoc[Skills] are reusable instruction sets that load when your prompt matches a skill's description. For information about skills and MCP tools, see xref:vibes-skills.adoc[].
27 changes: 27 additions & 0 deletions modules/ROOT/pages/vibes-skills.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
= Use Skills with MuleSoft Vibes
:page-deployment-options: cloud-ide, desktop-ide

Skills are reusable instruction sets that Agentforce 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 prompts.

When your request matches a skill's description, Agentforce 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.

Skills are always available in MuleSoft Vibes where the feature is supported. You can't turn it on or off.

== Set Up Skills in Your 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.

== 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 xref:vibes-mcp-server.adoc[].

== See Also

* xref:mulesoft-vibes.adoc[]
* xref:vibes-get-started.adoc[]
* xref:vibes-mcp-server.adoc[]
* xref:troubleshoot-generative-ai.adoc[]