From sandbox
Use when a sandbox workspace task needs repeatable setup, discovery, scaffolding, or verification commands. Guides when to create scripts, how to run them, and what not to automate.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sandbox:sandbox-scripts <task or command intent><task or command intent>bashThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use scripts for repeatable mechanical work. Keep source edits deliberate.
Use scripts for repeatable mechanical work. Keep source edits deliberate.
Scripts/ exists, use it.scripts/ exists, use it.scripts/.If both scripts/ and Scripts/ exist as distinct directories, use the one that already contains the majority of project scripts.
Memory/tasks/<task>.md when the task has
task memory.If PowerShell exists, the sandbox plugin includes a task-memory helper at
../../scripts/workspace-task-start.ps1 relative to this skill directory.
If you cannot run from the skill directory, compute the absolute path first:
SKILL_DIR=$(dirname "$(realpath "$0")") && pwsh "$SKILL_DIR/../../scripts/workspace-task-start.ps1" -TaskName "$ARGUMENTS"
If pwsh is unavailable and the task does not require repeated scaffolding,
skip the PowerShell helper and proceed directly to step 1 of the Procedure
using available shell tools.
If pwsh is unavailable and the task needs repeated task-memory scaffolding,
create a workspace-local helper in the workspace's scripts/ directory.
npx claudepluginhub gautam-achieveai/claudeplugins --plugin sandboxBlocks Edit/Write/Bash actions until Claude investigates importers, data schemas, and user instructions. Improves output quality by forcing concrete facts before edits.