superfly/sprites

Use this skill to create, list, inspect, operate, checkpoint, and safely clean up Sprites—isolated persistent cloud development environments. Trigger for remote sandboxes, cloud development environments, running builds or tests away from the local machine, long-running preview services, checkpoint/restore workflows, or any request that names Sprites or the Sprites MCP server.

Create, list, inspect, or restore Sprite checkpoints. Use before risky remote changes or when the user asks for a snapshot, restore point, rollback, recovery, or checkpoint history.

Safely inspect and clean up stale Sprites, services, and exec sessions. Use when the user asks to tidy, prune, stop, delete, destroy, remove old environments, or reduce Sprites clutter.

List and summarize Sprites or choose a target environment. Use when the user asks what Sprites exist, wants to find a matching or stale environment, or needs a concise inventory before remote work.

Create and verify a fresh Sprite for a task. Use when the user wants a new isolated environment, remote sandbox, preview environment, persistent development microVM, or a clean place to run code with Sprites.

Execute, test, build, inspect, install, or debug inside a Sprite. Use for one-off remote commands or isolated compute when the user names a Sprite or asks to run work in a remote sandbox.

Manage long-running services in a Sprite. Use when the user wants to create, start, stop, restart, expose, inspect, or debug a web server, worker, database, daemon, or preview service.

Run an end-to-end Sprites smoke test through MCP by listing, creating, executing, and optionally destroying a temporary Sprite. Use when the user asks to verify the plugin after installation or OAuth or explicitly requests a Sprites smoke test.

Check whether the Sprites Agent Plugin MCP tools are loaded and authenticated without creating resources. Use when the user asks whether Sprites is installed, connected, authorized, ready, or working, or requests a setup status check.