// 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"
Create new OpenCode agents with a gpt-5.2-codex default.
Create OpenCode custom commands for repeatable tasks.
Create targeted Cal links for specific people or teams
Use Chrome MCP to verify OpenWork UI flows, especially any feature that touches remote behavior. Triggers when user mentions: - "test with chrome mcp" - "ui verification" - "remote behavior test"
Start the OpenWork dev stack via Docker and verify real user flows via Chrome MCP. Triggers when user mentions: - "dev-up.sh" - "docker dev stack" - "verify in chrome mcp" - "test the real flow"
Run owpenbot/openwrk integration tests with Telegram test tokens. Triggers when user mentions: - "owpenbot tests" - "telegram test tokens" - "openwrk integration test"
| name | sandbox-lifecycle-fastlane |
| description | 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" |
skills/sandbox-lifecycle-fastlane/scripts/preflight.sh
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
Use the existing end-to-end skill:
skills/openwork-docker-chrome-mcp/SKILL.mdThat flow is the source of truth for:
_repos/openwork/packaging/docker/dev-up.shgit submodule update may refuse to move it. Stash changes inside that submodule repo.RECURSIVE=1 in preflight.sh.