plugins/sprite/skills/sprite-cli/SKILL.md
This skill should be used when the user asks to "create a sprite", "run in sprite", "execute in sprite", "sprite exec", "open sprite console", "list sprites", "destroy sprite", "create checkpoint", "restore checkpoint", "proxy through sprite", or mentions Sprite, isolated environments, or persistent microVMs. Also triggers on requests to manage sprite authentication, checkpoints, or port forwarding.
npx skillsauth add tavva/ben-claude-plugins sprite-cliInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
sprite)Command-line interface for Sprites - persistent, hardware-isolated Linux microVMs for safe code execution. Sprites maintain filesystem and memory between runs, wake instantly from hibernation, and charge per-second of compute.
sprite login # Authenticate with Fly.io
sprite logout # Remove configuration
sprite create [name] # Create a new sprite
sprite use <name> # Activate sprite for current directory
sprite use --unset # Remove sprite association
sprite list # List all sprites (alias: ls)
sprite destroy [-f] <name> # Remove a sprite
sprite exec <command> # Run command in sprite (alias: x)
sprite exec -file src:dst <cmd> # Upload file before execution
sprite console # Open interactive shell (alias: c)
sprite checkpoint create [-c] # Save current state
sprite checkpoint list # List checkpoints (alias: ls)
sprite checkpoint info <id> # Show checkpoint details
sprite checkpoint delete <id> # Remove checkpoint (alias: rm)
sprite restore [version-id] # Restore from checkpoint
sprite proxy <port> # Forward local port to sprite
sprite url update --auth <type> # Set URL access (public/default)
sprite api <path> [curl-opts] # Make authenticated API calls
sprite upgrade # Update CLI to latest version
Available with any command:
--debug[=<file>] - Enable debug logging-o, --org <name> - Specify organization-s, --sprite <name> - Specify sprite-h, --help - Display help# Create a new sprite
sprite create my-dev-env
# Activate sprite for current directory (creates .sprite file)
sprite use my-dev-env
# Now commands run in this sprite context
sprite exec npm install
# Run a single command
sprite exec ls -la
# Short alias
sprite x python script.py
# With environment variables
sprite exec -e API_KEY=secret ./run.sh
# Upload a file before execution (source:dest format)
sprite exec -file ./local-file.txt:/tmp/local-file.txt cat /tmp/local-file.txt
# Run with TTY (for interactive commands)
sprite exec -t vim file.txt
# Open shell (auto-detects bash/zsh/fish/tcsh/ksh)
sprite console
# Short alias
sprite c
# Save current state with comment
sprite checkpoint create -c "Before risky changes"
# List all checkpoints
sprite checkpoint list
# View checkpoint details
sprite checkpoint info <version-id>
# Restore to a checkpoint
sprite restore <version-id>
# Delete a checkpoint
sprite checkpoint delete <version-id>
# Forward local port 3000 to sprite port 3000
sprite proxy 3000
# Forward local 8080 to sprite 3000
sprite proxy 8080:3000
# Multiple ports
sprite proxy 3000 5432 6379
# Make sprite publicly accessible
sprite url update --auth public
# Require authentication (default)
sprite url update --auth default
# Interactive login via Fly.io
sprite login
# Or with pre-generated token
sprite auth setup --token <token>
# List configured tokens
sprite org list
# Add API token to organization
sprite org auth
# Remove all tokens
sprite org logout
# Toggle keyring storage
sprite org keyring enable
sprite org keyring disable
~/.sprites/sprites.json.sprite file in project directoryThe .sprite file stores organization and sprite selection, similar to .nvmrc or .python-version.
For complete CLI documentation including all options:
references/cli-reference.md - Full command reference with all flagstools
This skill should be used when working on frontend code, debugging UI issues, verifying visual changes, scraping web pages, testing web features, or inspecting page state. Also triggers on "open browser", "take screenshot", "navigate to URL", "scrape website", "extract page content", "check accessibility", or any web automation task. Use proactively during frontend development to verify changes visually.
tools
This skill should be used when the user asks to "send an email", "send email via Resend", "list emails", "check email status", "cancel scheduled email", "manage domains", "add domain", "verify domain DNS", "create API key", "list API keys", "manage templates", "create email template", or mentions Resend, transactional email, or email delivery. Also triggers on requests to configure Resend, check domain verification, or manage email infrastructure.
documentation
This skill should be used when the user asks to "create a README", "write a README", "generate a README", "improve my README", "make my README better", "README best practices", or mentions needing project documentation. Provides guidance for creating excellent READMEs following patterns from awesome-readme.
tools
This skill should be used when working on Obsidian plugins, testing plugin changes, verifying plugin UI, debugging plugin behaviour, or running automated tests against Obsidian. Also triggers on "start Obsidian", "take Obsidian screenshot", "test plugin", "run plugin command", "execute in Obsidian", or any Obsidian automation task. Use proactively during plugin development to verify changes visually.