Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →runkids/skillshare-devcontainer
Run CLI commands, tests, and debugging inside the skillshare devcontainer.
Passed 13 of 16 test cases with the skill, and 2 of 16 without it.
and 15 more in the full report
15 fixed3 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/3/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
I started the web UI dashboard in global mode inside the container. What are the default local ports used for the Vite frontend server and the Go API backend?
| Checked | Without skill | With skill |
|---|---|---|
| The response identifies port 45173 for the frontend server. | Missed | Passed |
| The response identifies port 49420 for the API backend server. | Missed | Passed |
The instructions your model reads when the skill loads.
Execute CLI commands and tests inside the devcontainer. The host machine is macOS but the project binary is Linux — running CLI commands on the host will silently produce wrong results or fail. This skill prevents that mistake.
Before acting, run python3 scripts/ai-context.py testing and follow that topic. The topic is the source of truth for repository execution boundaries and test rules; this skill retains the interactive workflow and command recipes.
ss / skillshare commands for verificationgo test, make test, make checkgit commands (git works on host)make fmt, make lint (host-safe Go toolchain commands; no container needed)cli-e2e-test skill instead (it handles ssenv isolation)Host (macOS)
└─ Devcontainer (Linux, Debian-based)
├─ Default HOME: /home/developer (persistent volume)
├─ Source: /workspace (bind-mount of repo root)
└─ ssenv environments: ~/.ss-envs/<name>/ (isolated HOME dirs)
Devcontainer = Linux environment with Go, git, pnpm, air (hot-reload). Source code is at /workspace (bind-mount of the host repo). The ss / skillshare wrapper auto-builds from source on every invocation — no manual make build needed. Edit code on the host, then immediately docker exec to run it; the change is picked up automatically.
ssenv = Isolated HOME directories within the devcontainer. Each env gets its own ~/.config/skillshare/, ~/.claude/, etc. Use ssenv when you need a clean state (testing init, install, sync) without polluting the container's default HOME.
Source code is bind-mounted into the container at /workspace. The ss wrapper runs go build transparently on every invocation:
docker exec $CONTAINER ss <command> — picks up your changes instantlytest cases passed, vs 2 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.