Python Executor

PassAudited by ClawScan on May 1, 2026.

Overview

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.

Install only if you trust inference.sh, verify the CLI installer/checksum, and review any Python code that will run—especially code involving private data, API calls, or generated files.

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.

What this means

Installing the CLI requires trusting inference.sh's installation script and downloaded binary.

Why it was flagged

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.

Skill content
curl -fsSL https://cli.inference.sh | sh && infsh login
Recommendation

Verify the installer source and checksum, or use the documented manual installation path before logging in.

What this means

Runs may be associated with the user's inference.sh account and any account limits, billing, or permissions tied to that login.

Why it was flagged

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.

Skill content
infsh login
Recommendation

Use an account appropriate for this purpose and understand what permissions or charges the infsh CLI session may have.

What this means

The agent can submit generated Python code that may make web requests, process data, or create returned files.

Why it was flagged

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.

Skill content
"code": "print('Hello World!')"
Recommendation

Review sensitive or high-impact code before running it, especially code that contacts external services or processes private data.

What this means

Private data included in code, inputs, API responses, or generated output files may be processed by the external provider.

Why it was flagged

The execution environment is provided by an external service, so submitted code, inputs, and outputs cross a provider boundary.

Skill content
Execute Python code in a safe sandboxed environment via [inference.sh](https://inference.sh)
Recommendation

Avoid sending secrets or sensitive datasets unless the provider's privacy, retention, and security terms are acceptable.