cuttle-cli

星标14

分支2

更新时间2026年7月13日 23:55

Use this skill to launch and manage Android Cuttlefish instances using the cuttle-cli and cuttle-server.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

purseclab

purseclab/kernelcveanalysis

打开 GitHub 仓库查看创作者相关仓库

下载

Cuttle CLI

Use this skill when the task is to operate a running cuttle_server environment through cuttle-cli cli tool.

Rules

Do not use --server-host, --server-port, --auth-token, or --user-id to override any configured settings.
Assume the CLI is already configured. If it fails because configuration or auth is missing, stop and report that instead of inventing overrides.
Prefer the narrowest action that satisfies the task. Avoid stop --stop-all unless the user clearly asked for it.

Main workflows

Inspect what is available

Use these first when the template or instance name is unknown:

cuttle-cli templates list
cuttle-cli templates show <template-name>
cuttle-cli list
cuttle-cli list --all

Notes:

If user specifies a template to use, do not inspect other templates.
templates list prints one template per line with CPU count and SELinux state.
templates show <template-name> prints the runtime root, kernel/initrd paths, SELinux setting, and template app list.
list shows only visible non-terminal instances by default.
list --all also includes stopped, crashed, and expired instances.

Start an instance

Basic launch:

cuttle-cli start <template-name>

Useful optional flags:

cuttle-cli start <template-name> --name <instance-name>
cuttle-cli start <template-name> --cpus <count>
cuttle-cli start <template-name> --selinux true
cuttle-cli start <template-name> --selinux false
cuttle-cli start <template-name> --no-load-apps

Guidance:

Use --name when the user wants a stable human-readable instance name.
Use --cpus and --selinux only when the user asked for those overrides.
Use --no-load-apps when the task should avoid template APK auto-loading.
Success output includes the effective instance name, instance id, state, and adb=<host:port> when available.

Stop instances

Stop a single instance by effective name:

cuttle-cli stop <instance-name>

Bulk stop modes:

cuttle-cli stop --stop-all
cuttle-cli stop --stop-all-user <user-id>

Guidance:

Pass exactly one of <instance-name>, --stop-all, or --stop-all-user.
Prefer stopping a single named instance.
If an instance was launched without a custom name, its effective stop target is its instance id.

Daemon behavior

cuttle-cli start, cuttle-cli list, and cuttle-cli stop automatically ensure the managed daemon is running.

Use explicit daemon commands only when the task is about daemon state or ADB sync behavior:

cuttle-cli daemon status
cuttle-cli daemon start
cuttle-cli daemon stop
cuttle-cli daemon sync

Guidance:

daemon status reports running, stale, or stopped.
daemon sync is for one-shot synchronization and fails if the daemon is already running.
Prefer the normal start/list/stop commands over manual daemon management.

Agent pattern

If the template or target instance is unknown, inspect with templates list, templates show, or list.
Run the smallest command that accomplishes the task.
Read stdout and return the important fields: template name, instance name, instance id, state, and ADB target when present.
If cuttle-cli reports missing config/auth or another CLI error, surface that error plainly and stop.

同仓库更多 Skills

同仓库

kartifact

purseclab/kernelcveanalysis

Create, write, list, and pull versioned exploit artifact folders through the kartifact CLI.

2026-07-2414

wrap-common-exploit

purseclab/kernelcveanalysis

Wrap an ordinary C exploit or PoC in kernel_PoCs/common so one source project can build as a Linux or Android static executable, dynamic executable, constructor-loaded shared object, or JNI library with local, listening, or reverse-shell root payloads. Use when creating a common-compatible exploit project, converting a C program with main(), setting up exploit entry and post-escalation payload code, repairing its Makefile or entrypoint integration, or initializing the bundled example project.

2026-07-2414

add-exploit-primitive

purseclab/kernelcveanalysis

Add a Linux or Android kernel exploit primitive to ingots_tools/primitives/src/primitive_data in the exact format consumed by primitives/src/primitives/__init__.py. Use when creating a new primitive entry with metadata.json, PRIMITIVE.md, and primitive.c, or when updating an agent to generate primitives for this repository.

2026-07-1314

android-kdebug

purseclab/kernelcveanalysis

Use the android-kdebug skill when debugging Android apps over ADB. The android-kdebug skill documents using kdebug Frida CLI, the kdebug LLDB CLI, or common adb commands.

2026-07-1314

object-db-query-api

purseclab/kernelcveanalysis

Use the high-level object_db wrapper API to scan kernel objects in Python by loading an ObjectSet and filtering HeapObject entries with helper predicates instead of raw SQL.

2026-07-1314

testvm

purseclab/kernelcveanalysis

Use the `testvm` CLI to pack and unpack initrds, build the default BusyBox initrd, and boot Linux kernels under QEMU on `x86_64`, `arm`, or `aarch64`. Use this when the user asks to run, debug, or explain `testvm` commands.

2026-07-1314

name	cuttle-cli
description	Use this skill to launch and manage Android Cuttlefish instances using the cuttle-cli and cuttle-server.

Cuttle CLI

Use this skill when the task is to operate a running cuttle_server environment through cuttle-cli cli tool.

Rules

Do not use --server-host, --server-port, --auth-token, or --user-id to override any configured settings.
Assume the CLI is already configured. If it fails because configuration or auth is missing, stop and report that instead of inventing overrides.
Prefer the narrowest action that satisfies the task. Avoid stop --stop-all unless the user clearly asked for it.

Main workflows

Inspect what is available

Use these first when the template or instance name is unknown:

cuttle-cli templates list
cuttle-cli templates show <template-name>
cuttle-cli list
cuttle-cli list --all

Notes:

If user specifies a template to use, do not inspect other templates.
templates list prints one template per line with CPU count and SELinux state.
templates show <template-name> prints the runtime root, kernel/initrd paths, SELinux setting, and template app list.
list shows only visible non-terminal instances by default.
list --all also includes stopped, crashed, and expired instances.

Start an instance

Basic launch:

cuttle-cli start <template-name>

Useful optional flags:

cuttle-cli start <template-name> --name <instance-name>
cuttle-cli start <template-name> --cpus <count>
cuttle-cli start <template-name> --selinux true
cuttle-cli start <template-name> --selinux false
cuttle-cli start <template-name> --no-load-apps

Guidance:

Use --name when the user wants a stable human-readable instance name.
Use --cpus and --selinux only when the user asked for those overrides.
Use --no-load-apps when the task should avoid template APK auto-loading.
Success output includes the effective instance name, instance id, state, and adb=<host:port> when available.

Stop instances

Stop a single instance by effective name:

cuttle-cli stop <instance-name>

Bulk stop modes:

cuttle-cli stop --stop-all
cuttle-cli stop --stop-all-user <user-id>

Guidance:

Pass exactly one of <instance-name>, --stop-all, or --stop-all-user.
Prefer stopping a single named instance.
If an instance was launched without a custom name, its effective stop target is its instance id.

Daemon behavior

cuttle-cli start, cuttle-cli list, and cuttle-cli stop automatically ensure the managed daemon is running.

Use explicit daemon commands only when the task is about daemon state or ADB sync behavior:

cuttle-cli daemon status
cuttle-cli daemon start
cuttle-cli daemon stop
cuttle-cli daemon sync

Guidance:

daemon status reports running, stale, or stopped.
daemon sync is for one-shot synchronization and fails if the daemon is already running.
Prefer the normal start/list/stop commands over manual daemon management.

Agent pattern

If the template or target instance is unknown, inspect with templates list, templates show, or list.
Run the smallest command that accomplishes the task.
Read stdout and return the important fields: template name, instance name, instance id, state, and ADB target when present.
If cuttle-cli reports missing config/auth or another CLI error, surface that error plainly and stop.