
Description
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.
SKILL.md
Smoke-test Sprites
Use MCP only. Do not install the Sprites CLI, call the REST API, or register a second MCP server.
- Confirm that Sprites tools are available; otherwise report the loading issue and stop.
- Call
list_sprites. An empty result is valid. - Create a short-lived name such as
mcp-smoke-<shortid>when no token prefix is known. If creation reports a different required prefix, retry once with that prefix. - Call
execwith a harmless command such asuname -aorecho smoke-ok. - Destroy the temporary sprite only when the user already requested teardown; otherwise ask before cleanup because destruction is irreversible.
- Report:
Sprites smoke test
- list: OK (N sprites) | empty (OK)
- create: NAME — STATUS — URL
- exec: exit CODE — brief output
- destroy: destroyed | skipped (kept) | not requested
- prefix learned: PREFIX | full access/none | unknown
Do not install packages, start services, or change network policy during this test.
More skills from the sprites-agent-plugin repository
View all 2 skillsMore from Fly.io
View publisherSprites.dev API
manage Fly.io Sprites cloud sandboxes
claude-plugins
Jul 12CLICode ExecutionInfrastructureSandboxingsprites
manage persistent microVMs with Sprites
sprites-antigravity-plugin
Jul 12Code ExecutionInfrastructureSandboxingsprites-checkpoint
manage Sprite checkpoints and snapshots
sprites-antigravity-plugin
Jul 12AutomationMaintenanceOperationssprites-cleanup
clean up stale Sprites and environments
sprites-antigravity-plugin
Jul 12AutomationMaintenanceOperationssprites-list
list and inspect Fly.io Sprites
sprites-antigravity-plugin
Jul 12CLIInfrastructureSandboxingsprites-new
create isolated Sprite development environments
sprites-antigravity-plugin
Jul 12Code ExecutionInfrastructureSandboxing