CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

upgrade-mule-app

Workflow required before any Mule application upgrade work. Call use_skill as your FIRST action — before reading project files (pom.xml, mule-artifact.json) or editing versions yourself — whenever the user asks to upgrade, migrate, bump, modernize, or move a Mule app to a newer Java version, a newer Mule Runtime version, or both. Covers upgrading Java and/or Mule Runtime, getting latest compatible connector versions, updating connector and plugin versions, and fixing impacts from operation changes in flows, DataWeave scripts, and MUnit tests. Even a targeted single-version bump like 'move this app to Java 17' or 'upgrade the runtime to 4.6' requires this workflow — do not hand-edit pom.xml versions and attempt the change yourself. When you call this skill, it must be the only tool call in that response.

67

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

70%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.

Exceptionally actionable and workflow-safe: deterministic scripts, exact commands, explicit gates, and bounded recovery loops leave nothing ambiguous about what to run, when to stop, and how to fix failures. Its weaknesses are token efficiency (rationales and rules repeated 3-4 times across a 1650-line body) and progressive disclosure (almost everything is inlined in SKILL.md with only one reference file for a skill of this size).

Suggestions

State each rule once and reference it: the runtimeVersion/minMuleVersion rationale, the Java 17+ describe gate, and the 'use the bundled scripts, do not reimplement' discipline each appear 3-4 times (Workflow-Wide Discipline, Step 7, the scripts table, Step 14, Step 16/18) — collapse these to a single authoritative statement plus one-line pointers.

Move the Step 12.3 plan template, the Step 8 custom-Java checklist, and the Step 9 DataWeave pattern catalog into references/ files (one level deep), leaving SKILL.md as a workflow overview with per-step pointers — the body is ~47k tokens where an overview plus references would serve navigation and token budget better.

Replace the multi-hundred-word cells of the bundled-scripts table with one-line purposes plus output paths, and move each script's output-shape documentation next to the step that consumes it (or into a per-script reference), trimming 'why' justifications to one sentence where the operational rule is already unambiguous.

DimensionReasoningScore

Conciseness

Noticeably verbose: the runtimeVersion/minMuleVersion rationale is explained four times (the apply_runtime_bump.mjs table row, Step 14's bullets, the plan template's mule-artifact.json and munit-maven-plugin sections), the Java 17+ describe gate appears in Workflow-Wide Discipline, the Step 7 prerequisite, and Step 16 class 6, and the bundled-scripts table embeds multi-hundred-word cells of per-script output-shape documentation. Not 1 (severely verbose, concepts Claude already knows) because nearly all content is novel Mule-specific domain knowledge (MMP 3.x/Aether breakage on Maven 3.9, Mode-A/B/C describe shapes, feature-line minMuleVersion) rather than generic-concept padding; not 3 because the repetition and justification density is pervasive across sections, not occasional.

2 / 5

Actionability

Every step ships copy-paste-ready invocations ("node scripts/validate_prerequisites.mjs ."), a paste-verbatim fan-out loop, exact jq field reads, documented exit-code semantics per script, and a failure-classifier table mapping each mvn error class to a concrete fix source on disk; all 24 referenced scripts exist under scripts/ and references/llm-prompts.md §1 exists as cited. Not 4 because the guidance covers the common cases fully executable with no material gaps.

5 / 5

Workflow Clarity

A two-phase workflow with a hard user-approval gate (Step 12.4), explicit validation checkpoints (Step 11.5 coverage gate, Step 12.0 soft dependency-tree cross-check, Step 14.5 hard pin gate), a completeness checklist (12.1), and bounded feedback loops (Step 16's classifier + escalation triggers + 5-retry halt; Step 17's 6-attempt MUnit loop with a precise MUnit Run Summary pass gate). This is the anchor-5 pattern — clear sequence, explicit validation, error-recovery loops, and checklists — with no validation gaps for a destructive/batch workflow.

5 / 5

Progressive Disclosure

Section structure is clear and the one external reference is real and clearly signaled ("Use references/llm-prompts.md §1 verbatim"), but ~1650 lines that belong in separate one-level-deep files are inlined in SKILL.md: the full plan template (12.3), the per-script output-shape documentation, the DataWeave pattern catalog (Step 9), and the custom-Java checklist (Step 8). Not 4 because the bulk of heavy reference material lives in the body rather than being split out; not 2 because navigation is easy and the references that do exist are properly signaled and one level deep.

3 / 5

Total

15

/

20

Passed

Description

95%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.

A highly specific, complete, and distinctive description with excellent trigger-term coverage and concrete example phrasings ('move this app to Java 17'). Its only defect is voice: second-person operational directives ('editing versions yourself', 'When you call this skill, it must be the only tool call in that response') break the required third-person convention and add length without adding trigger value.

DimensionReasoningScore

Specificity

"Covers upgrading Java and/or Mule Runtime, getting latest compatible connector versions, updating connector and plugin versions, and fixing impacts from operation changes in flows, DataWeave scripts, and MUnit tests" lists multiple specific concrete actions with comprehensive coverage — an anchor-5 fit — but the description repeatedly uses second person ("editing versions yourself", "When you call this skill, it must be the only tool call in that response"), which the judging guidelines penalize by reducing specificity by 1. Not 3 because the action list itself is far more comprehensive than the anchor-3 '1-2 concrete actions' example.

4 / 5

Completeness

Both questions are explicitly answered: 'what' via "Covers upgrading Java and/or Mule Runtime, getting latest compatible connector versions, updating connector and plugin versions, and fixing impacts from operation changes in flows, DataWeave scripts, and MUnit tests", and 'when' via "whenever the user asks to upgrade, migrate, bump, modernize, or move a Mule app to a newer Java version, a newer Mule Runtime version, or both" — with concrete trigger phrases, matching the anchor-5 example exactly. Not 4 because neither half is merely implicit or underspecified.

5 / 5

Trigger Term Quality

"upgrade, migrate, bump, modernize, or move a Mule app to a newer Java version, a newer Mule Runtime version" plus concrete example phrasings ("move this app to Java 17", "upgrade the runtime to 4.6") give comprehensive coverage of the natural terms and synonyms a user would actually say. Not 4 because no common user verb or phrasing for this task is missing — the five action synonyms span the realistic request space.

5 / 5

Distinctiveness Conflict Risk

"Mule application upgrade work", "Mule Runtime", "mule-artifact.json" carve out a clear niche with distinct triggers — no non-Mule skill could plausibly fire on these phrases, and even adjacent Mule skills are separated by the upgrade/migrate/bump/modernize action verbs. Not 4 because there is no meaningful overlap risk with closely related skills.

5 / 5

Total

19

/

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 (1651 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

mulesoft/mulesoft-dx

Path

skills/mule-development/upgrade-mule-app/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.