CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

manage-api-version

Read, check for updates, and change the version of one or more API dependencies in a Mule project — the same values the Anypoint Studio Project Properties → API Specs tab sets, stored as <{artifactId}.version> properties in pom.xml. Use when the user asks to "get API version", "show API version", "display version info", "check what version an API is on", "any new versions", "any updates available", "check for updates", "update API version", "change API version", "bump API version", "set API version", or any request to read, check, or modify an API dependency version in a Mule project.

Quality

92%

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

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 operational, well-sequenced workflow skill with excellent actionability and real validation/rollback loops for a batch pom.xml-editing operation. Its main weakness is token efficiency: several rules are repeated across sections and some rationale-heavy passages could be deduplicated or offloaded to a reference file.

Suggestions

State the one-call version-discovery rule, the absolute-path invocation rule, the describe-fallback caveat, the no-redirection rule, and the automatic-rescaffold rule once each in the Rules section, and reduce their in-line repetitions in the Bundled Scripts, Version Discovery, and Step 9 sections to brief pointers.

Move the Troubleshooting detail on CLI auth (ANYPOINT_BEARER / client-credential conflicts) and the extended describe-fallback diagnosis into a short references/ file, keeping only a one-line pointer in SKILL.md.

Trim Step 1 case 3's nested narrative to the decision rule and the user-facing message; the explanatory asides (e.g. why not to ask 'which project') can be cut without losing the routing behavior.

DimensionReasoningScore

Conciseness

The step procedures are dense and operational, but key rules are restated verbatim across sections — "never loop and invoke `anypoint-cli-v4` yourself, one API at a time" appears in the Bundled Scripts table, the Version Discovery intro, and the Rules section; the describe-fallback caveat, the absolute-path instruction, the no-redirection rule, and the automatic-rescaffold rule are each repeated 2–3 times, and Step 1 case 3's disambiguation narrative ("a name that only exists in one place is not actually ambiguous") is padded with rationale. Mostly efficient, but noticeably tightenable through deduplication.

3 / 5

Actionability

Fully executable throughout: exact commands ("mvn clean package -DskipTests", the awk property-update snippet, npm install/conf commands for the CLI), the exact script invocation format "<groupId>:<artifactId>:<currentVersion>" with the returned JSON shape, and copy-paste-ready AskUserQuestion question/option templates. Only Case 2 (hardcoded version) lacks a code snippet, which is a trivial gap against the common cases being covered.

5 / 5

Workflow Clarity

Clear routing table ("User intent | Path" mapping to numbered step chains), STOP markers as explicit checkpoints, and genuine feedback loops for a batch/destructive operation: "back up the current pom.xml content in memory", automatic restore on Exchange error or "BUILD FAILURE", per-`source`-field handling (list / describe-fallback / error), and "BUILD SUCCESS" as the completion gate. Anti-drift check against anchor 4: the error-recovery loop (restore → report verbatim → user investigates) is explicit, which anchor 4 lacks.

5 / 5

Progressive Disclosure

The single bundle file `scripts/fetch_versions.sh` is real, well-signaled (Bundled Scripts table + dedicated Version Discovery procedure), and one level deep — no nested references. However, at ~400 lines the body inlines content that would benefit from splitting (the Troubleshooting CLI-auth detail, the describe-fallback deep-dive, Step 1's extended disambiguation cases), so content is not fully "appropriately split" as anchor 5 requires.

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.

An exemplary description: concrete three-verb capability statement anchored to the exact storage mechanism, an explicit 'Use when' clause with an extensive list of natural trigger phrases and synonyms, and a tightly scoped Mule/Anypoint niche that minimizes conflict risk. Third-person voice is used throughout with no fluff.

DimensionReasoningScore

Specificity

Names three concrete, comprehensive actions — "Read, check for updates, and change the version of one or more API dependencies" — and anchors them to a precise data model: "stored as <{artifactId}.version> properties in pom.xml" and the "Anypoint Studio Project Properties → API Specs tab". This matches anchor 5's multiple specific concrete actions with comprehensive coverage; it is above anchor 4 because the three verbs cover the skill's full operation space with no gaps.

5 / 5

Completeness

Explicitly answers both questions: the "what" is the opening clause (read/check/change API dependency versions in a Mule project, with where they're stored), and the "when" is a full "Use when the user asks to ..." clause listing concrete trigger phrases plus a closing catch-all ("any request to read, check, or modify an API dependency version in a Mule project"). This mirrors the anchor 5 example's structure exactly; anchor 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Comprehensive natural phrases with synonym coverage: "get API version", "show API version", "display version info", "check what version an API is on", "any new versions", "any updates available", "check for updates", "update API version", "change API version", "bump API version", "set API version" — get/show/display and update/change/bump/set variants are all exactly what a user would say, plus the pom.xml file anchor and a catch-all clause.

5 / 5

Distinctiveness Conflict Risk

Clear niche — Mule project API dependency versions via Anypoint Exchange and pom.xml properties — with triggers that nearly all contain "API version" and are scoped "in a Mule project" in both the opening clause and the catch-all. Anti-drift check against anchor 4: the generic-sounding phrases ("any updates available", "check for updates") are explicitly qualified to API dependency versions in Mule, leaving only minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mulesoft/mulesoft-dx

Path

skills/mule-development/manage-api-version/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.