Sign inSign up

docker/sbx-kit-ecc

Verified Publisher

By Docker, Inc.

•Updated 9 days ago

The agent-harness optimization content pack for Claude Code: rules, agents, commands, and — whe...

Sandbox Kit
0

130

docker/sbx-kit-ecc repository overview

Digest

sha256:4e0c502d6b24…

Size

4.4 kB

Schema

v3

Pushed

9 days ago

Specificationspec.yaml

MIXIN

The agent-harness optimization content pack for Claude Code: rules, agents, commands, and — when the sandbox skills store is writable — skills, installed from upstream's minimal profile (no hooks runtime). Pinned to v2.0.0.


CapabilitiesExpand a row to see its full configuration. See the full spec for the complete descriptor.
TypeRequiredDescription
com.docker.sandbox/network-policy@1Required—
com.docker.sandbox/agent-skills@1OptionalECC installs its skills module into the shared store when it is writable
com.docker.sandbox/lifecycle@1Required—
com.docker.sandbox/agent-context@1Required—

Requiresclaude

Apply this mixin to a sandbox

sbx run <agent> --kit docker/sbx-kit-ecc:latest

Make sure you have docker sbx installed

Run the following command to install sbx on your machine.

macOS
brew install docker/tap/sbx
Windows
winget install Docker.sbx
Learn more about docker sbx⁠

Note

Experimental: Sandbox Kit v3

This kit uses the experimental Sandbox Kit specification⁠, specifically v3⁠. The format and runtime behavior may change before v3 is stable.

⁠ecc

A mixin installing affaan-m/ECC⁠ — "Everything Claude Code": a large agent-harness content pack of skills, agents, rules, and commands. Pinned to v2.0.0, installed from upstream's minimal profile; the skills part of it needs a writable skills store (see the design note below). The content is Claude-Code-specific, so the kit declares requires: ["claude"], which either the claude⁠ workload or claude-mixin⁠ satisfies.

⁠Usage

sbx run --kit "docker.io/docker/sbx-kit-ecc:latest" claude

Or from a git URL targeting this repo:

sbx run --kit "git+https://github.com/docker/sbx-kits-contrib.git#dir=ecc" claude

The installer places rules under ~/.claude/rules/ecc/, plus agents and commands, and tracks every file in ~/.claude/ecc/install-state.json (reversible via upstream's uninstall.js). Skills land under ~/.claude/skills/ecc/ only when the sandbox's skills store is writable.

⁠Design notes

  • No hooks runtime: the minimal profile installs the content (rules/agents/commands, plus skills when the skills store is writable) but not the hooks runtime ("instincts"/continuous-learning memory). Upstream documents that the installer leaves ~/.claude/settings.json untouched, so there's no conflict with the platform-seeded settings. Want the hooks? Re-run upstream's installer with --profile core from inside the session — core is a superset of minimal, so it writes the skills too and needs a writable skills store; without one, pass --modules and leave the skills module out.

  • Read-only skills store: since sbx v0.43.0 the shared skills store is bind-mounted read-only at ~/.claude/skills by default, and upstream's installer aborts at its first read-only write, leaving a partial install. So when the store is read-only the kit installs the modules rules-core,agents-core,commands-core,platform-configs instead of the whole minimal profile, dropping workflow-quality — ECC's skills, and nothing else. For the full profile, create the sandbox with a writable store:

    sbx run --skills readwrite --kit "docker.io/docker/sbx-kit-ecc:latest" claude
    

    --skills off also works: no store is mounted, so the installer creates ~/.claude/skills itself.

    The kit now also asks for a writable store, through an agent-skills@1 capability declaring ~/.claude/skills at mode: readwrite. That is the one declaration the v3 migration added rather than carried over: v2 had no grammar for it, which is why the instructions above could only tell you to pass a host-side flag. The ask is not a demand — both sides bound the result, so a host whose store is read-only or off still yields read-only or off, and the write probe in the install hook keeps doing its job. It is optional, because the rules, agents and commands install either way.

  • Upstream warns "do not stack install methods" — this kit uses only the manual path; don't additionally /plugin install ecc@ecc in the same sandbox.

  • ECC is a big pack (260+ skills upstream; this kit installs a subset of the content) — expect some context-window cost from the rules it loads.

  • No telemetry found upstream; github.com + registry.npmjs.org are contacted at install time only.

This week's pulls

Pulls:

54

Last week