메뉴
Install, repair, verify, and orient Clawperator for Android automation by AI agents.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Measure Clawperator snapshot and daemon I/O latency on Android devices. Use when comparing emulator versus physical-device performance, timing repeated snapshot calls, validating release versus debug APK behavior, or producing performance findings for specific apps/screens.
Validates a Clawperator release candidate, creates and pushes an annotated git tag for a specific version and commit, inspects the resulting GitHub Actions release workflows, and prepares the follow-up published-version docs update.
Regenerate Clawperator landing and docs sitemap metadata from per-URL source files using each file's last git commit timestamp, then validate the resulting XML and build integration.
Orchestrates the full Clawperator release flow from an optional unreleased code-version bump through release creation, release verification, published-version updates, and the next code-version bump. Use when you need to run or resume the complete release workflow end to end and keep prerelease-stage versions in the `0.x.y` series.
Author, update, and verify public documentation pages in docs/. Use when creating new doc pages, updating existing pages to match code changes, or improving documentation quality. This skill governs content work - for build compilation, use docs-build.
Build the Clawperator public docs site from authored markdown and code-derived inputs. Use when you need to assemble sites/docs/.build/, run the MkDocs build, generate llms-full.txt, or validate the docs pipeline.
| name | clawperator-setup |
| description | Install, repair, verify, and orient Clawperator for Android automation by AI agents. |
| license | Apache-2.0 |
| compatibility | Requires Node.js 24+, npm, Java 17 or 21, adb, and a physical Android device or Android emulator. |
| metadata | {"homepage":"https://clawperator.com","docs":"https://docs.clawperator.com","repository":"https://github.com/clawperator/clawperator","installer":"https://clawperator.com/install.sh","package":"clawperator","last_verified_package_version":"0.9.5"} |
Use this skill when a user asks:
Read https://clawperator.com/skill.md and get me set up with Clawperator.
Clawperator is a deterministic actuator for Android automation by AI agents. The external agent is the brain: it reasons, asks the user for approval when needed, and decides the next step. Clawperator is the hand: it executes validated Android actions and returns structured results.
Clawperator is not an autonomous planner, credential manager, or permission bypass tool. Do not invent credentials, hide prompts from the user, or continue when no authorized Android target is available.
Use this skill for:
Do not use this file as a full runtime command guide. After setup succeeds,
prefer the public docs and the local host files written by clawperator install.
| Requirement | Required state | Check |
|---|---|---|
| Node.js | 24+ | node -v |
| npm | Available on PATH | npm -v |
| Java | 17 or 21 | java -version |
| adb | Available on PATH | adb version |
| Android target | Physical device or emulator visible to adb | clawperator devices |
Human action may be required for OS prompts, Android Developer Options, USB debugging authorization, accessibility permission, notification permission, app installation, app sign-in, and choosing which physical device or emulator to target.
If the clawperator CLI is missing or the host may need prerequisites, run the
public bootstrap installer:
curl -fsSL https://clawperator.com/install.sh | bash
If Node.js 24+ and npm are already ready and you only need the npm package, install the CLI directly and then run the canonical post-bootstrap route:
npm install -g clawperator@latest
clawperator install
If the CLI already exists, repair or refresh through the same post-bootstrap route:
clawperator install
clawperator install is the setup route after the CLI exists. It handles
Operator remediation, runtime skills, bundled host-agent skills, and local host
orientation. Do not replace it with raw adb install.
Run these checks after install or repair:
clawperator doctor
clawperator devices
clawperator snapshot --device <device_serial>
Success criteria:
clawperator doctor exits 0 and reports criticalOk as true.clawperator devices shows at least one device with state device.clawperator snapshot --device <device_serial> exits 0 and returns a
successful result envelope.If more than one adb-visible target is connected, choose one serial from
clawperator devices and pass --device <device_serial> on later snapshot,
runtime-skill, and direct action commands.
After clawperator install, read these host-local files when present:
| File | Use |
|---|---|
~/.clawperator/AGENTS.md | First local guide for what this host can do now. |
~/.clawperator/install-state.json | Install metadata such as CLI version, registry path, APK version, and last device serial. |
~/.clawperator/mcp-config-snippet.json | Generated MCP configuration for stdio MCP clients. |
These files are host-specific. Treat them as local orientation, not public documentation.
Use the public docs for stable technical detail:
Use MCP only after setup when the host agent supports stdio MCP:
clawperator mcp serve
Use runtime-skill discovery after setup when the task is app-specific:
clawperator skills list
clawperator skills search --keyword "<term>"
clawperator skills get <skill_id>
Stop and report the exact failing command and output when:
clawperator doctor does not reach criticalOk: trueclawperator snapshot --device <device_serial> failsNever guess credentials, bypass approval, or claim setup is complete before the readiness checks pass.