sprite_skill

This skill enables you to manage OuterClaude and InnerClaude on Sprites.dev VMs, streamlining testing, checkpointing, and Claude-to-Claude interactions.
  • Python

0

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill spm1001/trousse --skill sprite

  • SKILL.md16.3 KB
  • test-outer-inner.sh1.5 KB

Overview

This skill controls InnerClaude instances running on Sprites.dev VMs for testing workflows, install patterns, and Claude-to-Claude interaction. It documents the tmux + pipe-pane capture pattern, checkpoint/restore behavior, and bootstrap steps so OuterClaude can reliably operate an InnerClaude. Use it before any sprite exec, InnerClaude, or remote VM operations that involve automating CLI-driven Claude sessions.

How this skill works

The skill automates a tmux session on the sprite to run the claude CLI, captures the interactive UI with tmux pipe-pane (not capture-pane), and sends keystrokes into the session using tmux send-keys. It ensures a valid CLAUDE_CODE_OAUTH_TOKEN is exported inside the tmux session, handles workspace trust and permission dialogs, and documents the TWO-ENTER submission pattern required by the InnerClaude UI. It also covers checkpointing and restoring VM state and explains that environment variables are not preserved by snapshots.

When to use it

  • Testing automated workflows where Claude controls another Claude (Outer→Inner pattern).
  • Remote development on persistent Sprites.dev Ubuntu VMs requiring an interactive claude session.
  • Creating reproducible install or bootstrap tests that need checkpoint/restore of VM state.
  • Bootstrapping new sprites with auth and tooling installed for subsequent automated runs.
  • Diagnosing interactive UI behavior that capture-pane cannot observe.

Best practices

  • Always export CLAUDE_CODE_OAUTH_TOKEN inside the tmux session; snapshots do not persist env vars.
  • Use the literal NVM path /.sprite/languages/node/nvm/nvm.sh — avoid $NVM_DIR to prevent escaping issues.
  • Use tmux pipe-pane "cat > /tmp/claude-output.txt" to capture the alternate-screen UI, then filter with strings.
  • Wait 20–30 seconds after starting claude before reading output; verify with wc -c on the output file.
  • Submit messages with Enter Enter (first adds newline in input box, second actually sends).

Example use cases

  • Run end-to-end tests where OuterClaude issues prompts and verifies InnerClaude responses on a sprite.
  • Automate install flows that require interactive permission prompts and file edits inside InnerClaude.
  • Create checkpoint before a risky install, restore to a clean snapshot, and repeat tests deterministically.
  • Bootstrap a fresh sprite: install tools, authenticate GH, save a checkpoint, and replay builds.
  • Capture and replay dialog interactions to validate UI prompts and permission flows.

FAQ

That usually means the OAuth token was not present in the tmux session. Export CLAUDE_CODE_OAUTH_TOKEN inside the tmux session and restart claude; verify with ps aux | grep node and wc -c /tmp/claude-output.txt.

Why not use tmux capture-pane?

Claude's interactive UI uses the alternate screen buffer which capture-pane misses. pipe-pane streams the terminal output (including alternate screen) to a file; then use strings to filter ANSI control codes.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational