pdk-prerequisites

Verify and install all prerequisites for Omni Gateway custom policy development with PDK — Anypoint CLI v4 with the PDK plugin, Rust toolchain, wasm32-wasip1 target, Docker, and Anypoint Platform credentials. Use when any PDK skill reports a missing tool, when the user asks "how do I set up PDK", "what do I need for custom policies", "PDK prerequisites", or when a build/publish/test command fails with a toolchain error.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

The body is a highly actionable, well-sequenced setup guide: dependency-ordered checks, per-install verification, and a comprehensive troubleshooting section, all with copy-paste commands. Its main weaknesses are minor duplication between the install steps and the Troubleshooting section, and the absence of any bundle structure to move the extensive troubleshooting content out of SKILL.md.

Suggestions

Deduplicate content repeated between install steps and Troubleshooting (npm PATH fix, legacy wasm32-wasi note, plugin-name migration) by stating each once and cross-referencing the Troubleshooting section.

Move the ~85-line Troubleshooting section into references/troubleshooting.md, keeping a short list of error symptoms in SKILL.md that links to it, so the main file stays a lean overview.

Trim per-OS install variants (e.g., macOS/Linux Docker instructions) into a small reference table to reduce body length without losing actionability.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable commands rather than prose and assumes Claude's competence, but the npm PATH fix, the legacy wasm32-wasi guidance, and the plugin-name migration fix are each stated twice (in install steps and again in Troubleshooting). This is efficient with minor duplication that could be trimmed — the 4 anchor — rather than the fully lean 5, and well above the padded or over-explained 3.	4 / 5
Actionability	Every step gives copy-paste-ready bash (e.g., `anypoint-cli-v4 plugins:install anypoint-pdk-plugin`, `rustup target add wasm32-wasip1`), each with a Verify: command, and even failure branches have concrete fixes (401/403 → re-login, grant Exchange Contributor). Fully executable guidance covering the common cases matches the 5 anchor.	5 / 5
Workflow Clarity	"Run checks first, report what's missing, then guide installation one tool at a time. After each installation, re-verify before moving on" plus the dependency-ordered tool table, per-step verification commands, the results checklist, and a Final Verification re-run loop. Clear sequence with explicit validation checkpoints and feedback loops — the 5 anchor; a 4 would imply missing checkpoints, which are all present.	5 / 5
Progressive Disclosure	Sections are well-organized with clear headers and external doc links are clearly labeled in "Additional Resources", but this is a ~300-line single file with no bundle: the ~85-line Troubleshooting section and per-OS install details could be split into a references file to keep SKILL.md an overview. Good structure with minor placement gaps matches the 4 anchor; it is not a 5 because content that could be split is inlined, and not a 3 because navigation is easy and nothing is buried.	4 / 5
	Total	18 / 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: third-person voice, concrete actions, a complete enumeration of the prerequisite toolchain, and an explicit trigger clause covering both user queries and toolchain-error conditions. It is concise while remaining comprehensive and is cleanly distinguishable from neighboring skills.

Dimension	Reasoning	Score
Specificity	"Verify and install all prerequisites for Omni Gateway custom policy development with PDK — Anypoint CLI v4 with the PDK plugin, Rust toolchain, wasm32-wasip1 target, Docker, and Anypoint Platform credentials" states concrete actions and comprehensively enumerates every tool in the niche. Coverage is complete rather than having minor gaps, so it matches the 5 anchor over the 4.	5 / 5
Completeness	Explicitly answers "what" (verify and install the listed prerequisites) and "when" via a concrete "Use when..." clause with quoted trigger phrases. This mirrors the 5 anchor example's structure; a 4 would require a less explicit or specific "when" clause, which is not the case.	5 / 5
Trigger Term Quality	Includes natural user phrasings ("how do I set up PDK", "what do I need for custom policies", "PDK prerequisites") plus failure-based triggers ("build/publish/test command fails with a toolchain error", "any PDK skill reports a missing tool"). Both query-style and error-style variations are covered, matching the comprehensive 5 anchor.	5 / 5
Distinctiveness Conflict Risk	"Omni Gateway custom policy development with PDK", "Anypoint CLI v4 with the PDK plugin", and "wasm32-wasip1" pin a clear niche with distinct triggers that would not fire for unrelated skills. Minimal conflict risk matches the 5 anchor.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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/pdk-prerequisites/SKILL.md
Commit: 0606917

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.