How do I install the Sandbox Lifecycle Fastlane skill?

Run npx skillmds@latest add different-ai/sandbox-lifecycle-fastlane in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sandbox Lifecycle Fastlane safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sandbox Lifecycle Fastlane?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sandbox Lifecycle Fastlane free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sandbox Lifecycle Fastlane?

different-ai (@different-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sandbox Lifecycle Fastlane by different-ai

Name: Sandbox Lifecycle Fastlane
Author: different-ai

Sandbox Lifecycle Fastlane

Fast preflight for sandbox lifecycle work: sync pins, create a worktree, and run the standard Docker + Chrome MCP verification path. Triggers when user mentions: - "sandbox lifecycle" - "sandbox stuck" - "docker + chrome mcp"

different-ai adb30ed 5 files · 3.5 KB Updated Sep 17, 2026

File contents

Quick Usage (Already Configured)

1) Preflight (sync + sanity checks)

skills/sandbox-lifecycle-fastlane/scripts/preflight.sh

2) Create a worktree for this task

Recommended (uses a timestamped branch name):

skills/sandbox-lifecycle-fastlane/scripts/worktree.sh

Override branch name/base:

BRANCH="sandbox-lifecycle" BASE_REF="origin/main" \
  skills/sandbox-lifecycle-fastlane/scripts/worktree.sh

3) Verify the real flow

Use the existing end-to-end skill:

skills/openwork-docker-chrome-mcp/SKILL.md

That flow is the source of truth for:

starting the stack via _repos/openwork/packaging/docker/dev-up.sh
verifying user flows via Chrome MCP

What This Skill Optimizes For

Snappy setup: one command preflight, one command worktree.
Reliability: avoid accidental recursive submodule operations unless explicitly requested.
Debuggability: print the minimum git context that matters when sandboxes behave oddly (pin drift, dirty state).

Common Gotchas

If a submodule is dirty, git submodule update may refuse to move it. Stash changes inside that submodule repo.
If you do need recursive submodule checks, set RECURSIVE=1 in preflight.sh.

Frequently asked questions