Python Executor
Analysis
This skill coherently provides a remote Python execution service, but users should notice that it relies on a third-party CLI/account and can run broad Python code with network access.
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.
curl -fsSL https://cli.inference.sh | sh && infsh login
The documented setup installs a CLI by piping a remote script into a shell. This is disclosed and user-directed, but it depends on a remote installer outside the reviewed artifact.
"code": "print('Hello World!')"The input schema accepts arbitrary Python code for execution. This is the skill's stated purpose and is routed through the provider sandbox, but it remains a powerful capability.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
infsh login
The skill requires or expects logging into the inference.sh CLI, so it will use a provider account/session even though registry metadata lists no primary credential.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Execute Python code in a safe sandboxed environment via [inference.sh](https://inference.sh)
The execution environment is provided by an external service, so submitted code, inputs, and outputs cross a provider boundary.
