CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

manage-global-configurations

Create, get, edit, delete, list, validate, and consolidate all global configurations in a Mule project — 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. Use when the user asks to "add Salesforce config", "configure connector", "set up connection", "create TLS context", "set up object store", "add caching strategy", "create error handler", "set up autodiscovery", "import shared project", "create config.yaml", "set up environments", "add global property", "list global elements", "find usages", "validate config exists", "consolidate configs", or any request to manage global-level configuration in a Mule app. NEVER use MCP server tools — use only the bash scripts provided.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced operational skill: exact commands and templates, explicit interactive checkpoints, confirmation gates on destructive operations, and a validate-fix-retry loop on every write path. Its one real weakness is redundancy — a duplicated rules section, three copies of the dependency block, a redundant architecture diagram, and a hardcoded connector version — which inflates token cost without adding capability.

Suggestions

Remove the 'Tips and Best Practices' section or trim it to only guidance not already stated in Step 1 — roughly eight of its bullets repeat Step 1 rules verbatim ('Configuration structure from metadata only', 'Connector versions from Exchange only', 'No MCP server tools', 'Never output raw XML').

Replace the three full inline pom.xml dependency blocks (Step 11, Object Store, API AutoDiscovery) with a single pointer to the dependency patterns in references/global-elements-catalog.md, keeping only the read → check-if-present → add → write procedure inline.

Drop the mermaid architecture diagram (the Level 1/Level 2 routing tables in Step 2 convey the same dispatch in less space) and remove the hardcoded 'mule-objectstore-connector 1.2.5' version in favor of the live Exchange lookup the skill itself mandates.

DimensionReasoningScore

Conciseness

The body is dense operational instruction with no basic-concept padding, but it is noticeably redundant: the 'Tips and Best Practices' section restates Step 1 rules nearly verbatim ('Configuration structure from metadata only', 'No MCP server tools', 'Never output raw XML'), the full pom.xml dependency block is repeated three times (Step 11, Object Store, API AutoDiscovery) even though the Tips section says the patterns are 'documented in references/global-elements-catalog.md', and the mermaid architecture diagram duplicates the Step 2 routing tables. The hardcoded 'mule-objectstore-connector 1.2.5' version is time-sensitive information that also contradicts the skill's own versions-from-Exchange-only rule.

3 / 5

Actionability

Everything is copy-paste executable: exact script invocations with arguments ('bash scripts/get_latest_connector.sh salesforce sfdc', 'pick_connector.sh sfdc com.mulesoft.connectors:mule-salesforce-connector:11.1.0'), complete XML dependency blocks with exact namespace URIs and schemaLocation entries, a concrete validation command ('cd <project-dir> && mvn clean package -DskipTests'), and per-type reference search patterns like 'cachingStrategy-ref="{name}"' and 'listenerConfig="X"'.

5 / 5

Workflow Clarity

Steps 1–14 are explicitly sequenced with an 'Execution Paths' map routing each task type to its step subset, STOP markers as interactive checkpoints, skip-if-provided logic, mandatory user confirmation before destructive DELETE/CONSOLIDATE operations, and a build-validation feedback loop ('Fix and re-run until BUILD SUCCESS'). This matches the anchor-5 pattern of clear sequence, explicit validation, and error-recovery loops.

5 / 5

Progressive Disclosure

The References table is exemplary — each of the three files gets a content summary and a 'When to Read' condition, references are one level deep (verified: the reference files contain no nested document references), and the Scripts table documents purpose and arguments. It falls short of a 5 because content the catalog reference already owns (the pom dependency patterns) is duplicated inline in three places rather than purely referenced, and the 490-line body carries routing information twice (mermaid diagram plus Step 2 tables).

4 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: comprehensive concrete capabilities in third person, an explicit 'Use when' clause with seventeen quoted natural trigger phrases, and a distinct Mule-specific niche with a catch-all clause for uncovered phrasings. The only debatable element is the trailing 'NEVER use MCP server tools' instruction, which is behavioral guidance rather than trigger information, but it does not dilute the capability or trigger coverage.

DimensionReasoningScore

Specificity

Opens with seven concrete verbs ('Create, get, edit, delete, list, validate, and consolidate') and enumerates every element type ('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') — comprehensive coverage of the skill's capabilities in third-person voice.

5 / 5

Completeness

Clearly answers both questions: the first sentence states 'what' (all CRUD-style operations plus listing/validation/consolidation across all element types), and 'Use when the user asks to "add Salesforce config"...' gives an explicit 'when' with concrete trigger phrases — matching the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Seventeen quoted natural phrases users would actually say ('add Salesforce config', 'set up object store', 'create TLS context', 'consolidate configs', 'create config.yaml') plus a catch-all ('any request to manage global-level configuration in a Mule app') give comprehensive coverage including synonyms and concrete file/element names.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous and Mule-specific ('in a Mule project', 'in a Mule app', MuleSoft-only element names like API AutoDiscovery and Object Store), so it occupies a clear niche with distinct triggers and minimal risk of firing for a non-Mule skill.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (509 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

mulesoft/mulesoft-dx

Path

skills/mule-development/manage-global-configurations/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.