Back to skill
Skillv1.0.1
ClawScan security
Mobilerun · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
BenignMar 15, 2026, 4:48 AM
- Verdict
- Benign
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- The skill's requirements, runtime instructions, and requested credential (MOBILERUN_API_KEY) are consistent with its stated purpose of remotely controlling Android devices via the Mobilerun API.
- Guidance
- This skill appears coherent and does what it says: it uses a single Mobilerun API key to control Android devices via the Mobilerun cloud. Before installing, consider: - Trust & sensitivity: controlling a phone (screenshots, UI tree) can expose extremely sensitive personal data. Only enable this skill if you trust the Mobilerun service and the agent using the skill. - API key handling: the skill expects a dr_sk_... key. Do not paste or share your key in chat; use the platform's secure credential storage and revoke the key from the Mobilerun dashboard if you stop using the skill. - Webhooks & tasks: the platform supports webhooks and server-side tasks that can stream events; be careful when configuring webhook targets or running tasks that might send screenshots or UI data to external servers. - Least privilege & billing: confirm the API key/account scope and billing plan (cloud devices and autonomous agent tasks may consume credits). Avoid granting more permissions than necessary. If you want extra caution, require explicit user confirmation before the skill performs high-impact actions (installing apps, uninstalling, or running autonomous Tasks), or disable autonomous invocation for this skill if your agent platform allows that.
Review Dimensions
- Purpose & Capability
- okName/description (phone control) aligns with required items: a single Mobilerun API key and API calls to https://api.mobilerun.ai. No unrelated credentials, binaries, or config paths are requested.
- Instruction Scope
- okSKILL.md and the included docs only instruct using the documented Mobilerun API endpoints (devices, screenshot, ui-state, tap, swipe, keyboard, tasks). It explicitly warns not to print the API key and not to share screenshots/UI trees with others. There is no guidance to read unrelated files, system credentials, or to send data to unexpected endpoints.
- Install Mechanism
- okInstruction-only skill with no install spec and no code files to download or execute. This minimizes disk-writing and supply-chain risk.
- Credentials
- okOnly a single required environment variable (MOBILERUN_API_KEY) is declared and used; that is proportionate to the described API access. The docs explicitly instruct not to expose the key.
- Persistence & Privilege
- okThe skill is not forced always-on (always: false) and requests no special system privileges beyond using the supplied API key. Autonomous model invocation remains allowed by default but is not combined with other privileges that would increase concern.