메뉴
Run project commands (build, test, lint) in a cloud sandbox with common runtimes and on-demand toolchains.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Read Slack threads or channel history and post concise bot replies through slack-post-message when the user asks to answer in Slack or when a Slack event payload provides channel and thread context.
GitHub CLI surface allowed by Thor's server-side gh policy. Append-only: Thor can create PRs, comments, and non-approval reviews but cannot approve, merge, edit, or delete prior artifacts.
Query and analyze Langfuse observability data (observations, metrics, scores) via the mcp CLI for debugging LLM behavior, cost, and user activity.
Orchestrate real browser interaction, screenshots, recordings, and UI evidence without encoding app-specific flows.
Inspect LaunchDarkly feature flags, environments, segments, and metrics through the read-only ldcli wrapper.
Git command surface allowed by Thor's server-side policy. Thor's git is append-only to the local repo and to origin. Load this skill to see what commands are allowed and the common redirect patterns.
SOC 직업 분류 기준
| name | sandbox |
| description | Run project commands (build, test, lint) in a cloud sandbox with common runtimes and on-demand toolchains. |
Use sandbox to run project commands: builds, tests, lints, and anything that needs runtimes not available locally (Java, Python, etc.). The sandbox auto-creates on first use, syncs your worktree, and stops automatically when idle.
For technical browser orchestration guidance — choosing between existing UI automation, lightweight interaction, deterministic visible capture, verification, and artifact patterns — use the dedicated browser skill. Keep app-specific browser flows in repo runbooks or task prompts.
Supported forms:
sandbox <command> [args...]sandbox bash -c '<command>'sandbox bash -lc '<command>'sandbox sh -c '<command>'sandbox sh -lc '<command>'Examples:
sandbox mvn test -pl module-auth
sandbox ./gradlew build
sandbox bash -c 'make build && make test'
sandbox npm test
For a single command, write it naturally: sandbox mvn test -pl module-auth.
For shell chaining, pipelines, or redirects, wrap the command explicitly:
sandbox bash -c 'make build && make test'
sandbox bash -c 'npm run build && npm test'
cd /workspace/worktrees/myrepo/feat/auth
sandbox mvn test -pl module-auth # auto-creates sandbox, syncs, runs
# edit code (no need to commit)...
sandbox mvn test -pl module-auth # syncs uncommitted changes, reuses sandbox
sandbox ./gradlew spotlessCheck # same sandbox, different command
The sandbox image is intentionally slim. Preinstalled by default:
uv available for fast installs.ondrej/php, with common CLI extensions installed.sudo dockerd & before use.agent-browser with Chrome for Testing preinstalled, plus ffmpeg, xvfb, xdotool, tree, and ImageMagick (identify, convert, compare).Browser examples:
sandbox agent-browser --session qa open https://example.com
sandbox agent-browser --session qa screenshot /tmp/example.png
sandbox identify /tmp/example.png
sandbox xvfb-run -a agent-browser --session qa open https://example.com --headed
Install less-common toolchains on demand per task by running the appropriate
installer inside the sandbox (for example via nvm, pyenv, rustup, or by
downloading a release tarball into $HOME/.local). Use sandbox bash -lc '...'
to run install commands, then invoke the toolchain the same way.
To use a non-default version, either set it permanently or inline it with your command:
# Permanent (persists across sandbox calls, only need to set once)
sandbox sdk default java 17.0.18-tem
sandbox mvn test
# Inline (one-off version switch + command)
sandbox bash -c 'sdk use java 17.0.18-tem && mvn test'
sandbox bash -c 'nvm use 20 && npm test'
/workspace/sandbox inside the sandbox — paths in error output will show this prefixsandbox commands on the same worktree can run in parallel