Maven Full Runner

The skill's name/description match its code and instructions: it is a passthrough wrapper that only consumes --dir and forwards all other arguments to mvn. However, the registry metadata lists no required binaries while the SKILL.md and the script both state that node and mvn must be present in PATH — that metadata mismatch is inconsistent and should be corrected.

SKILL.md and the script limit the wrapper to parsing --dir and forwarding all other args unchanged. The script only checks that the target directory exists and then spawns 'mvn' with shell:false and stdio inherited. This is consistent with the stated purpose. Important security note: because all Maven goals/arguments are forwarded, running this skill against untrusted repositories or build files can execute arbitrary code (via Maven plugins, lifecycle hooks, downloaded artifacts), and Maven itself may perform network activity to fetch dependencies — these are expected behaviors for a build runner but are risks the user should understand.

No install spec; the skill is instruction-only with an included script file. Nothing is downloaded or executed during install and no external install URLs are used.

The skill requests no environment variables or credentials and the script does not read secrets or unrelated config paths. It relies only on system binaries (node and mvn), which is proportionate to a Maven wrapper.

The skill does not request permanent presence (always:false), does not modify other skills’ configuration, and does not require elevated privileges. Autonomous invocation is allowed by default (platform normal) but not a special privilege here.