Content
81%Weight 40%Scale 1-5Reviews 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |