VecML AutoML
Analysis
The skill appears coherent and purpose-aligned, but it uploads CSV data to VecML and uses a VecML API key, so users should only use it with data they are comfortable sending to that service.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
post("create_project", { ... "project_name": project ... }) ... post("train_automl_model", { ... "model_name": model_name ... })The helper performs remote API actions that create projects and train models. These actions are purpose-aligned, but they mutate the user's remote VecML workspace.
Source: unknown ... No install spec — this is an instruction-only skill.
The package includes a Python helper but has limited source/provenance information and no install spec. No suspicious install behavior is shown, but provenance is worth noting.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
KEY = os.environ.get("VECML_API_KEY", "") ... "user_api_key": KEYThe skill requires a VecML API key and includes it in API requests. This is expected for a VecML integration, but it gives the script authority to act in the user's VecML account.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
API = os.environ.get("VECML_API_URL", "https://aidb.vecml.com/api") ... "X": x_b64 ... "file_data": y_b64The script sends encoded feature and label CSV data to an external API endpoint. This matches the AutoML purpose, but it means user data leaves the local environment.
