ワンクリックで
geelark-shared
Use when first setting up geelark-cli, running config init, verifying authentication, or handling API errors.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when first setting up geelark-cli, running config init, verifying authentication, or handling API errors.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
GeeLark cloud phone management: list, create, start, stop, delete, update, clone, screenshot, GPS, shell, ADB, file, library, app, analytics, webhook, OEM, automation, and more.
GeeLark browser management: list, create, start, stop, delete, edit, clone, clear cache, cookies, bookmarks, kernels, transfer, move group, automation tasks, and more.
GeeLark billing management: query balance, transaction details, plan info, upgrade/renew plans, and buy time add-ons. Use when managing account billing and subscriptions.
GeeLark group management: query, create, update, and delete cloud phone groups. Use when managing cloud phone groups or organizing phones by group.
GeeLark proxy management: list, add, update, delete, and check proxies. Use when managing proxy configurations for cloud phones.
GeeLark tag management: list, create, update, and delete cloud phone tags. Use when managing tags for organizing cloud phones.
| name | geelark-shared |
| version | 1.0.0 |
| description | Use when first setting up geelark-cli, running config init, verifying authentication, or handling API errors. |
This skill guides you on how to operate GeeLark resources via geelark-cli and important notes.
Run geelark-cli config init to set up your API Token on first use.
# Interactive setup
geelark-cli config init
# Provide token directly
geelark-cli config init --token "your_api_token"
You can find your API Token in the GeeLark client Settings page.
After configuration, verify your token is valid:
geelark-cli auth status
code: 0 → Authentication successfulcode: 40003 → Token invalid or expired, re-configure requiredAll APIs return a unified JSON envelope:
{
"traceId": "A25B0025BA886B1EB2679AAAAC599998",
"code": 0,
"msg": "success",
"data": { ... }
}
| Field | Type | Description |
|---|---|---|
traceId | string | Request trace ID; provide this when troubleshooting |
code | integer | 0 means success, non-zero is an error code (see each command's error code table) |
msg | string | Result description; error message on failure |
data | object/null | Business data on success; may be null on failure |
code == 0, data contains business datacode != 0, msg contains error descriptionThe "Response Fields" section in each skill reference only describes the
datainner structure. The actual response is always wrapped in the envelope above.
| Code | Description |
|---|---|
| 0 | Success |
| 40003 | Token invalid or authentication failed |
| 40004 | Parameter validation failed |
| 40007 | Rate limit exceeded |
| 40011 | Paid plan required |
| 41001 | Insufficient balance |
| 50000 | Internal server error |
Module-specific error codes are listed in each skill reference. Full error codes:
Control output format with --format:
geelark-cli phone list --format json # JSON (default)
geelark-cli phone list --format pretty # Pretty-printed JSON
geelark-cli phone list --format table # Table
~/.geelark/config.json; tokens are masked in display