setting-up-a-box
Skill490 starsChanged 6 days agoApache-2.0View on GitHub
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.
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Follow the rules in the prompt under "Set up with your coding agent" on that page.
- Distinctive: line 20
Use the page in this checkout, not the copy on GitHub, so the steps match the code you build.
- Very specific: line 27
When the operator wants to change what the box allows, use the authoring-box-policy skill.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Setting up a box
Walk the operator through 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-containmenthere, then copy the three binaries into~/box-tutorial/box-corethe 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 skill.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- authoring-box-policySkill
- debug-os-failure-on-githubSkill
- docs-auditSkill
- docs-plannerSkill
- docs-reviewerSkill
- docs-syncSkill
- docs-writerSkill
- exploreSkill
- kdSkill
- specSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.