The skill intentionally invokes the belt CLI, submits arbitrary Python to a third-party execution service, and demonstrates outbound HTTP requests. Most backtick detections are Markdown formatting, and the reconnaissance alert is unsupported, but remote execution, network access, and unpinned npx installation remain real risks.
The skill sends Python source through the inference.sh belt application. Submitted source may contain user data or secrets that cross a third-party service boundary.
The description names inference.sh, and the quick start submits Python source with belt app run. The document does not state a local-only execution path.
Capability review items (15)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The skill intentionally invokes the belt CLI, submits arbitrary Python to a third-party execution service, and demonstrates outbound HTTP requests. Most backtick detections are Markdown formatting, and the reconnaissance alert is unsupported, but remote execution, network access, and unpinned npx installation remain real risks.
The skill sends Python source through the inference.sh belt application. Submitted source may contain user data or secrets that cross a third-party service boundary.
The description names inference.sh, and the quick start submits Python source with belt app run. The document does not state a local-only execution path.
Capability review items (15)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Most static backtick findings are Markdown formatting or package names, not Ruby shell execution. Real risk remains because the skill uses the external belt CLI to run arbitrary Python and includes network-capable examples. No prompt injection attempt was found in the reviewed SKILL.md file.
Arbitrary Python Execution Through External Service
The skill grants Bash(belt *) and instructs the agent to send Python code to infsh/python-executor. This creates remote code execution and data exposure risk if prompts include secrets.
The frontmatter permits Bash(belt *) and the quick start sends Python code through belt. The use cases also state that the skill can run any Python script.
Capability review items (18)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
> **Install the belt CLI skill:** `npx skills add belt-sh/cli`
This line tells users to run npx to install an external skill, which can execute third-party package code. It is documented behavior, but it is a real supply-chain risk.
The line declares dependence on the external belt CLI and links to remote install instructions. This is legitimate dependency documentation, but it expands trust beyond the local skill.
The quick-start block runs belt login and belt app run with a Python payload. That intentionally invokes an external CLI to execute code through a hosted service.
This range includes use-case text saying the skill can run any Python script. That broad execution intent is a real code-execution risk even though the static trigger is noisy.
The example imports requests and performs an HTTP GET from sandboxed Python. This confirms network egress capability, although the target is a benign sample domain.
description: "Execute Python code in a safe sandboxed environment via [inference.sh](https://inferen
The description states execution is via inference.sh, so the skill depends on a remote service. This is a network dependency, not evidence of malicious exfiltration.
The line links to remote install instructions for the required CLI. This is not malicious by itself, but it creates an external dependency users must trust.
The Markdown backtick findings are mostly documentation false positives, but the real belt examples execute user-supplied Python through an external service. Network access is an intended feature through HTTP examples and external service links. No prompt injection text was found, but the skill remains high risk because it enables broad remote code execution.
The skill grants Bash access to belt commands and documents running arbitrary Python through infsh/python-executor. This is an intentional capability, but it can execute code, perform network requests, and return files through an external service.
The allowed-tools declaration limits Bash to belt, and multiple examples use belt app run with user-supplied Python. The use case list explicitly says it can run any Python script.
Capability review items (17)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
> **Install the belt CLI skill:** `npx skills add belt-sh/cli`
This line instructs users to run npx to install another skill, which is real external command execution. The command may install third-party marketplace content, so it should require user consent.
This bash example runs belt app run to execute supplied Python through an external service. The command is intentional, but it can execute arbitrary user-provided code and needs consent controls.
The example imports requests and performs an HTTP GET from Python, so network egress is an intended capability. It is documented behavior, but it can contact external sites.
The example imports requests and performs an HTTP GET from Python, so network egress is an intended capability. It is documented behavior, but it can contact external sites.
description: "Execute Python code in a safe sandboxed environment via [inference.sh](https://inferen
The description identifies inference.sh as the external execution service. This is a real network dependency for the skill, even though it is disclosed.
The sample Python code contains a hardcoded external URL and performs network access. The URL is part of documented examples, but network egress is real.
The sample Python code contains a hardcoded external URL and performs network access. The URL is part of documented examples, but network egress is real.
Most static backtick findings are Markdown formatting or package names, not Ruby shell execution. Real risk remains because the skill uses the external belt CLI to run arbitrary Python and includes network-capable examples. No prompt injection attempt was found in the reviewed SKILL.md file.
Arbitrary Python Execution Through External Service
The skill grants Bash(belt *) and instructs the agent to send Python code to infsh/python-executor. This creates remote code execution and data exposure risk if prompts include secrets.
The frontmatter permits Bash(belt *) and the quick start sends Python code through belt. The use cases also state that the skill can run any Python script.
Capability review items (18)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
> **Install the belt CLI skill:** `npx skills add belt-sh/cli`
This line tells users to run npx to install an external skill, which can execute third-party package code. It is documented behavior, but it is a real supply-chain risk.
The line declares dependence on the external belt CLI and links to remote install instructions. This is legitimate dependency documentation, but it expands trust beyond the local skill.
The quick-start block runs belt login and belt app run with a Python payload. That intentionally invokes an external CLI to execute code through a hosted service.
This range includes use-case text saying the skill can run any Python script. That broad execution intent is a real code-execution risk even though the static trigger is noisy.
The example imports requests and performs an HTTP GET from sandboxed Python. This confirms network egress capability, although the target is a benign sample domain.
description: "Execute Python code in a safe sandboxed environment via [inference.sh](https://inferen
The description states execution is via inference.sh, so the skill depends on a remote service. This is a network dependency, not evidence of malicious exfiltration.
The line links to remote install instructions for the required CLI. This is not malicious by itself, but it creates an external dependency users must trust.