⚠
Purpose & Capability
The SKILL.md and code clearly expect an API key and environment variables (MULEROUTER_API_KEY, MULEROUTER_BASE_URL or MULEROUTER_SITE) and require Python + uv and network access to api.mulerouter.ai / api.mulerun.com, but the registry metadata lists no required env vars or binaries. That mismatch is incoherent: the skill will fail or prompt for secrets at runtime unless an API key is provided, yet metadata doesn't declare the requirement.
ℹ
Instruction Scope
Runtime instructions ask the user/agent to check and print environment variables, load a .env from the current directory, run dependency installation (uv sync) and execute Python scripts that will read local image/video files and convert them to base64 to send to remote APIs. Reading and uploading local files is expected for this skill, but the instructions explicitly recommend running from the skill root and will load any .env found in the current working directory — this can unintentionally load unrelated secrets. The configuration-check commands also print the base URL and may expose variable values if run carelessly.
ℹ
Install Mechanism
There is no install spec (instruction-only install), which is low risk for installation, but the package contains many Python source files that will be executed locally. The SKILL.md requires the 'uv' runner and Python 3.10+, so the real runtime dependency is heavier than metadata indicates. No network downloads from untrusted URLs are present in an install step, but running the scripts will contact remote APIs.
⚠
Credentials
The code requires an API key (MULEROUTER_API_KEY) and optionally a base URL or site selector; those are appropriate for a remote API integration. However, registry metadata declared no required env vars. The skill also loads a .env file from the current directory (dotenv) which can pull in unrelated secrets if the working directory contains such a file. The number and sensitivity of environment variables requested is moderate and appropriate for the purpose, but the failure to declare them in metadata and the .env loading behavior are concerning.
✓
Persistence & Privilege
The skill does not request permanent inclusion (always:false) and does not modify other skills or system-wide settings. It identifies itself in outgoing requests via User-Agent headers but does not request elevated system persistence. Autonomous model invocation is allowed by default (disable-model-invocation:false), which is normal for skills; combined with the network access requirement this increases the operational blast radius but is expected for this integration.