1. A Mule 4 project in the workspace with standard structure (

   src/main/mule/

   ,

   src/main/resources/

   ,

   pom.xml

   )
2. Anypoint CLI v4 installed with the DX Mule plugin (

   @mulesoft/anypoint-cli-dx-mule-plugin

   )
3. Java 11+ and Maven available for build validation
4. Mule Runtime available for

   dx mule describe-connector

   metadata commands

• Create connector config: Steps 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
  • When: User asks to add a new connector configuration (Salesforce, HTTP, DB, etc.)
  • You'll need:

    projectDir

    ,

    connectorName

• Create global element: Steps 1, 2, 12
  • When: User asks to add TLS Context, Object Store, Caching Strategy, Error Handler, AutoDiscovery, or Import
  • You'll need:

    projectDir

    ,

    elementType

• Manage properties: Steps 1, 2, 13
  • When: User asks to create/edit properties files, set up environments, or manage global-property elements
  • You'll need:

    projectDir

• Management operations: Steps 1, 2, 14
  • When: User asks to list all, find usages, validate, or consolidate global elements
  • You'll need:

    projectDir

• Multi-turn interactive. At every "STOP" marker: print only questions as plain text, end your response, and wait. No tools until all questions in that phase are answered.
• Pre-supplied value extraction (skip-if-provided). Before the first STOP, parse the user's initial request and extract any values they already supplied (e.g., connector name, config name, provider name, field values, placeholder preference). Record these as "pre-supplied." At each subsequent STOP point, check whether the question is already answered by a pre-supplied value — if yes, use that value and skip the STOP entirely. Only ask questions for information NOT provided. If the user says "default placeholders" or "use placeholders for all fields," treat that as the answer to Step 8 and skip its STOP. If ambiguity remains (e.g., user says "basic provider" but metadata lists "basic-connection" and "basic-auth"), still ask.
• No MCP server tools. ALL Exchange searches and connector operations MUST use ONLY the bash scripts. Never call

  search_asset

  ,

  get_asset

  , or any MCP-based tool.
• Never output raw XML to chat — always write to file.
• Never use TaskCreate.
• Configuration structure from metadata only. Never hardcode attributes, child elements, or provider names for connectors. The

  describe-connector

  metadata is the source of truth.
• Connector versions from Exchange only. Never paste a version from memory. The only acceptable source is

  get_latest_connector.sh

  →

  pick_connector.sh

  .
• All configs go in

  global-configs.xml

  . See

  references/global-config-conventions.md

  for ordering and structure.
• pom.xml dependency is MANDATORY. Every global element that requires a dependency (connectors, Object Store, API AutoDiscovery, imports) MUST have its dependency added to

  pom.xml

  . Read

  pom.xml

  , add the

  <dependency>

  block inside

  <dependencies>

  , and write the file. The build will fail without this. Never skip this step.

scripts/

Bash

get_latest_connector.sh <search> [nickname]

pick_connector.sh <nickname> <gav>

describe_connector.sh <nickname>

dx mule describe-connector

build_gav.sh <json>

groupId:assetId:version

<skill-root>/scripts/

<skill-root>

Read

references/global-elements-catalog.md

references/global-config-conventions.md

global-configs.xml

references/properties-patterns.md

${placeholder}

AskUserQuestion

What would you like to do? (create, view, edit, delete, validate, consolidate)

What name for this connector configuration? (e.g.,

salesforceConfig

)

${connectorNamespace.fieldName}

Provide values for required fields, or choose "placeholders" for

${property}

references.

1. Write config to

   src/main/mule/global-configs.xml

   (create if missing — see

   references/global-config-conventions.md

   ).
2. Add namespace + schemaLocation.
3. Write/update

   src/main/resources/config.yaml

   .
4. Add connector dependency to pom.xml (MANDATORY — do not skip):
   • Read the project's

     pom.xml

     .
   • Check if the connector's

     <artifactId>

     already exists in

     <dependencies>

     .
   • If NOT present, add this dependency block inside

     <dependencies>

     :
     xml

     <dependency>
         <groupId>{groupId}</groupId>
         <artifactId>{artifactId}</artifactId>
         <version>{version}</version>
         <classifier>mule-plugin</classifier>
     </dependency>

   • The

     groupId

     ,

     artifactId

     , and

     version

     come from the GAV saved by

     pick_connector.sh

     in

     tmp/connector-choices/

     .
   • Write the updated

     pom.xml

     with the new dependency added.
5. Validate:

cd <project-dir> && mvn clean package -DskipTests

BUILD SUCCESS

src/main/mule/*.xml

<*:*-config>

config-ref="{name}"

os:config

1. Write XML (config BEFORE object-store) to

   global-configs.xml

   .
2. Add

   os

   namespace:

   xmlns:os="http://www.mulesoft.org/schema/mule/os"

   and its schemaLocation entry.
3. Add

   mule-objectstore-connector

   dependency to pom.xml (MANDATORY — do not skip):
   • Read

     pom.xml

     and check if

     mule-objectstore-connector

     already exists in

     <dependencies>

     .
   • If NOT present, add this dependency block inside

     <dependencies>

     :
     xml

     <dependency>
         <groupId>org.mule.connectors</groupId>
         <artifactId>mule-objectstore-connector</artifactId>
         <version>1.2.5</version>
         <classifier>mule-plugin</classifier>
     </dependency>

   • Write the updated

     pom.xml

     .
4. Validate build:

   cd <project-dir> && mvn clean package -DskipTests

   .

1. Write XML to

   global-configs.xml

   :
   xml

   <api-gateway:autodiscovery apiId="${api.id}" flowRef="{flow-name}" doc:name="API AutoDiscovery" />

2. Add

   api-gateway

   namespace:

   xmlns:api-gateway="http://www.mulesoft.org/schema/mule/api-gateway"

   and its schemaLocation entry.
3. Add

   mule-api-gateway

   dependency to pom.xml (MANDATORY — do not skip):
   • Read

     pom.xml

     and check if

     mule-api-gateway

     already exists in

     <dependencies>

     .
   • If NOT present, add this dependency block inside

     <dependencies>

     :
     xml

     <dependency>
         <groupId>org.mule.modules</groupId>
         <artifactId>mule-api-gateway</artifactId>
         <version>${app.runtime}</version>
         <classifier>mule-plugin</classifier>
         <scope>provided</scope>
     </dependency>

   • Write the updated

     pom.xml

     .
4. Add

   api.id

   to config.yaml (MANDATORY — do not skip):
   • Read

     src/main/resources/config.yaml

     .
   • Add

     api.id: "YOUR_API_ID"

     (or user-specified value) under an appropriate section.
   • Write the updated config.yaml.
5. Validate build:

   cd <project-dir> && mvn clean package -DskipTests

   .

1. Scan all Mule XML files under

   src/main/mule/

   .
2. Identify every top-level element inside

   <mule>

   that is NOT

   <flow>

   or

   <sub-flow>

   .
3. Categorize: Connector Configs, Configuration Properties, Global Properties, Global Error Handlers, API AutoDiscovery, TLS Context, Object Store, Caching Strategy, Import References, Application Configuration, Other.
4. Count usages per named element (search

   config-ref

   ,

   tlsContext

   ,

   objectStore

   ,

   cachingStrategy-ref

   ,

   defaultErrorHandler-ref

   ,

   errorHandler-ref

   ,

   listenerConfig

   ).
5. Present grouped table with name, type, file, usage count.
6. Highlight issues: unresolved placeholders, scattered configs (not in

   global-configs.xml

   ), unused elements (0 references).

1. Identify target element (list all if not specified, ask which).
2. Search ALL Mule XML files for references using per-type patterns:

   • config-ref="{name}"

     — connector operations/sources

   • listenerConfig="{name}"

     — OAuth callback configs

   • tlsContext="{name}"

     — HTTP configs

   • objectStore="{name}"

     — caching strategies

   • cachingStrategy-ref="{name}"

     —

     <ee:cache>

     scopes

   • defaultErrorHandler-ref="{name}"

     —

     <configuration>

   • errorHandler-ref="{name}"

     — individual flows
3. Present: file, line, flow/element, attribute, context snippet.

config-ref

tlsContext

objectStore

cachingStrategy-ref

defaultErrorHandler-ref

errorHandler-ref

listenerConfig

1. Scan all Mule XML under

   src/main/mule/

   for reference attributes (

   config-ref="X"

   ,

   tlsContext="X"

   ,

   objectStore="X"

   ,

   cachingStrategy-ref="X"

   ,

   defaultErrorHandler-ref="X"

   ,

   errorHandler-ref="X"

   ,

   listenerConfig="X"

   ).
2. Collect all declared global element names (top-level elements with a

   name

   attribute).
3. For each reference: check if the referenced name exists in the declared set.
4. Report any dangling references — attributes pointing to a global element that does not exist in the project. Include file, line, and the missing name.
5. Suggest fix: create the missing global element, or correct the reference to an existing one.

references/global-config-conventions.md

1. Scan all files for global elements outside

   global-configs.xml

   .
2. Classify each as movable or flow-coupled (per decision matrix).
3. Present report: what to move, what to keep, with reasons.
4. Wait for explicit confirmation → STOP.
5. Execute: move elements, add namespace declarations, remove from source, clean unused namespaces.
6. Validate build:

   mvn clean package -DskipTests

   .
7. Report: moved count, namespace cleanup, build result.

• Configuration structure from metadata only. Never hardcode attributes or child elements for connectors. The

  describe-connector

  metadata is the source of truth.
• Connector versions from Exchange only. Never paste a version from memory — use

  get_latest_connector.sh

  →

  pick_connector.sh

  .
• All configs go in

  global-configs.xml

  . See

  references/global-config-conventions.md

  for ordering and structure.
• Multi-turn interactive. At every decision point: print only questions as plain text, end the response, and wait for user input before proceeding.
• Skip-if-provided. When the user's initial request includes details (config name, provider, placeholder preference, field values), skip the corresponding STOP points. Only ask for information that was NOT provided or is ambiguous.
• Never output raw XML to chat — always write to file.
• No MCP server tools. ALL Exchange searches and connector operations MUST use ONLY the bash scripts provided.
• Always update pom.xml. Every connector/module that needs a dependency MUST be added to

  pom.xml

  . This is the #1 cause of build failures. The dependency XML patterns are documented in

  references/global-elements-catalog.md

  . Read pom.xml → add dependency → write pom.xml. Do this BEFORE running

  mvn clean package

  .
• Always update config.yaml for placeholders. When using

  ${property.name}

  placeholders in XML, the corresponding property MUST be added to

  src/main/resources/config.yaml

  . For AutoDiscovery, always add

  api.id

  to config.yaml.

• Build fails after adding config: Check namespace declarations match the connector's XSD URL. Verify the schemaLocation URL is correct.
• Connector not found in Exchange: Ensure Anypoint CLI is authenticated. Try broader search terms with

  get_latest_connector.sh

  .
• Describe-connector fails: Verify Java 11+ is available and the connector GAV is valid. Check

  tmp/connector-choices/

  for the saved JSON.
• Unresolved placeholders at runtime: Ensure

  <configuration-properties>

  is registered in

  global-configs.xml

  and the properties file exists in

  src/main/resources/

  .
• Namespace conflicts: Run consolidation to centralize all global elements and clean up duplicate namespace declarations.

• build-mule-integration: Build Mule flows that reference the global configurations created by this skill
• secure-mule-app: Configure secure properties encryption for sensitive configuration values
• create-project-template: Generate a new Mule project with proper structure before adding configurations