Run

Security checks across static analysis, malware telemetry, and agentic risk

Overview

This instruction-only skill claims to provide a secure execution sandbox but gives broad instructions for arbitrary code execution, automation, and production deployment without any implementation or clear safeguards.

Review carefully before installing. This skill does not include an actual sandbox implementation, yet it encourages broad code execution, persistent automation, and production deployment. Only use it if you can independently verify the runtime, approval controls, network limits, and rollback protections.

Static analysis

No static analysis findings were reported for this release.

VirusTotal

VirusTotal findings are pending for this skill version.

View on VirusTotal

Risk analysis

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

If followed using available local tools, the agent could run unreviewed code or install dependencies in ways that affect the user’s machine or data.

Why it was flagged

The skill directs the agent toward arbitrary code execution and automatic dependency handling without showing any implementation, dependency provenance, sandbox boundary, or approval mechanism.

Skill content
"scope": "Run arbitrary code snippets with auto-dependency injection"
Recommendation

Do not rely on this skill as a safe execution sandbox unless it ships a reviewed implementation with explicit execution, dependency, network, and file-system limits.

What this means

An agent could interpret this as permission to make high-impact production or cloud changes without enough user control.

Why it was flagged

The instructions include production deployment authority, but do not define target scope, credentials, approvals, rollback, audit, or containment.

Skill content
"deploy": { "scope": "Instant deployment of local logic to cloud-edge nodes", "trigger": "Run this in production" }
Recommendation

Require explicit human approval, named deployment targets, reviewable diffs, rollback steps, and scoped credentials before any production action.

What this means

Automation could continue after the immediate request and perform actions later without the user noticing.

Why it was flagged

The skill describes persistent autonomous activity but does not define duration limits, cancellation, monitoring, or user consent requirements.

Skill content
"automate": { "scope": "Long-running cron jobs and event-driven triggers" }
Recommendation

Only allow scheduled or event-driven work with explicit user opt-in, visible job listings, expiration times, and easy cancellation.

What this means

A user may over-trust the skill and allow dangerous execution because they believe sandboxing and biometric approval are enforced.

Why it was flagged

These strong safety claims are not backed by any provided code, install mechanism, required runtime, or capability declaration, making them potentially misleading.

Skill content
"security": "Strict hardware-level sandboxing (gVisor/Firecracker)" ... "High-risk commands ... require explicit biometric confirmation."
Recommendation

Treat the safety claims as unverified until the skill provides auditable implementation artifacts and clear enforcement details.