offload-run

Automate remote project command execution in Sprites sandboxes with output streaming.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yigitkonur/skills-by-yigitkonur-secondary --skill offload-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: offload-run
Source: https://github.com/yigitkonur/skills-by-yigitkonur-secondary/tree/main/skills/offload-run
Command: npx skills add https://github.com/yigitkonur/skills-by-yigitkonur-secondary --skill offload-run

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, sprite, git, node, python, e2b, tart, pnpm, npm, pip, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Offload-run lets you run a project's npm/pnpm install, tests, builds, or development servers in a remote Sprites cloud sandbox instead of on your local machine, preserving local CPU and memory.

Core Features & Use Cases

  • Remote execution with real-time stdout/stderr streaming from the cloud environment.
  • Golden checkpoints per project for fast warm starts and separate persistent server sprites for services.
  • Cross-backend flexibility: Sprites (default), E2B, and Tart backends to suit Linux, macOS, or Linux-on-Apple hardware.

Quick Start

Install the skill and start a remote run with offload run -- npm test to execute your project in the cloud and stream output locally.

Frequently Asked Questions about offload-run

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run npm build tests in the cloud to free up local CPU and memory?

You can offload project builds to the cloud by running them in remote Sprites sandboxes, which streams stdout and stderr directly to your local terminal while preserving your machine's resources.

How does streaming remote execution work for development servers?

Remote execution streams real-time stdout and stderr from the cloud environment to your local interface, using golden checkpoints for fast warm starts and separate persistent server sprites to maintain active services.

Can I use cloud build sandboxes with Python and Node environments?

Yes, remote execution supports Node, Python, macOS, and generic projects by bootstrapping environments, restoring state, and installing dependencies using backend tools like pnpm, npm, and pip across Sprites, E2B, and Tart.

Do I need to install the Sprite CLI before running cloud builds?

Yes, you need the Sprite CLI installed locally, along with a project lockfile to generate golden checkpoints, and specific backend tools like node, python, tart, or e2b to bootstrap the remote environments.

What is the difference between Sprites, E2B, and Tart backends for remote execution?

Sprites is the default backend, while E2B and Tart provide cross-backend flexibility to suit different infrastructure needs, including Linux environments and Linux-on-Apple hardware for macOS projects.

Why use a project lockfile when offloading builds to a cloud sandbox?

A project lockfile is required to generate golden checkpoints, which enable fast warm starts by preserving restored state and installed dependencies across multiple remote execution sessions.