setting-up-a-box · git:20261007.158dade · 2026-10-07 · sha256 90d9f78fa70a0b99
setting-up-a-box git:20261007.158dadeA
Immutable. This exact content never changes and is served at /api/v1/blob/90d9f78fa70a0b99.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_gqpmfgiir4ivx6bm/90d9f78fa70a0b9963dfe6fddc6a60aa7f1314022bec3d6d4be6871c40ec51b3.json
Then /plugin install setting-up-a-box@markdownregistry-gqpmfgiir4ivx6bm in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: setting-up-a-box description: Walk an operator through running an agent in a Strands Box for the first time, by following the getting started guide step by step. Use when someone asks to set up Box, try Box, run an agent in a box, or follow the getting started guide. Not for changing Box itself. --- # Setting up a box Walk the operator through [`docs/user/getting-started.md`](../../../docs/user/getting-started.md) in this checkout. Read the whole page first, then follow it step by step. The page owns every step and every command. This skill adds only what the page can't know: that you're inside a clone. ## Rules Follow the rules in the prompt under "Set up with your coding agent" on that page. They say what to check first, when to ask, and what never to do: don't touch the Bedrock API key, and don't run `box run`. ## In a clone - Use the page in this checkout, not the copy on GitHub, so the steps match the code you build. - Offer to build Box from this checkout in place of the download. Run `cargo build --release -p strands-box -p strands-box-containment` here, then copy the three binaries into `~/box-tutorial/box-core` the way the page's "Build from source" section does. ## After setup When the operator wants to change what the box allows, use the [`authoring-box-policy`](../authoring-box-policy/SKILL.md) skill.