Menú
Use this skill to launch and manage Android Cuttlefish instances using the cuttle-cli and cuttle-server.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Create, write, list, and pull versioned exploit artifact folders through the kartifact CLI.
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.
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.
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.
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.
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.
| name | cuttle-cli |
| description | Use this skill to launch and manage Android Cuttlefish instances using the cuttle-cli and cuttle-server. |
Use this skill when the task is to operate a running cuttle_server environment through cuttle-cli cli tool.
--server-host, --server-port, --auth-token, or --user-id to override any configured settings.stop --stop-all unless the user clearly asked for it.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:
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.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:
--name when the user wants a stable human-readable instance name.--cpus and --selinux only when the user asked for those overrides.--no-load-apps when the task should avoid template APK auto-loading.adb=<host:port> when available.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:
<instance-name>, --stop-all, or --stop-all-user.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.start/list/stop commands over manual daemon management.templates list, templates show, or list.cuttle-cli reports missing config/auth or another CLI error, surface that error plainly and stop.