skillshare-devcontainer
Run CLI commands, tests, and debugging inside the skillshare devcontainer. Use this skill whenever you need to: execute skillshare CLI commands for verification, run Go tests (unit or integration), reproduce bugs, test new features, start the web UI, or perform any operation that requires a Linux environment. All CLI execution MUST happen inside the devcontainer — never run skillshare commands on the host. If you are about to use Bash to run `ss`, `skillshare`, `go test`, or `make test`, stop and use this skill first to ensure correct container execution.
npx skills add runkids/skillshare --skill skillshare-devcontainer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
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. ## When to Use This - Running `ss` / `skillshare` commands for verification - Running `go test`, `make test`, `make check` - Reproducing a bug report - Testing a feature you just implemented - Starting the web UI dashboard - Any command that needs the skillshare binary or Go toolchain ## When NOT to Use This - Editing source code (do that on host via Read/Edit tools) - Running `git` commands (git works on host) - Running `make fmt`, `make lint` (host-safe Go toolchain commands; no container needed) - E2E test runbooks → use `cli-e2e-test` skill instead (it handles ssenv isolation) ## Architecture: Two Layers of 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
- When to Use This
- When NOT to Use This
- Architecture: Two Layers of Isolation
- Zero-Rebuild Workflow
- Entering the Devcontainer
- Programmatic access (for docker exec workflows)
- Running Commands
- Simple command (uses container's default HOME)
- Command with isolated HOME (clean state)
- Multi-command sequence
- Go tests
- Go tests with auth disabled
- Web UI Dashboard
- ssenv Quick Reference
make devc # build + init + interactive shell (one step) make devc-up # start only (no shell) make devc-down # stop make devc-restart # restart + re-run start-dev.sh make devc-reset # full reset (remove volumes), then `make devc` to re-init make devc-status # show container status docker exec $CONTAINER bash -c \ docker exec $CONTAINER ss <command> [flags] docker exec $CONTAINER ssenv create "$ENV_NAME" --init docker exec $CONTAINER ssenv enter "$ENV_NAME" -- ss status
What does the skillshare-devcontainer skill do?
Run CLI commands, tests, and debugging inside the skillshare devcontainer. Use this skill whenever you need to: execute skillshare CLI commands for verification, run Go tests (unit or integration), reproduce bugs, test new features, start the web UI, or perform any operation that requires a Linux environment. All CLI execution MUST happen inside the devcontainer — never run skillshare commands on the host. If you are about to use Bash to run `ss`, `skillshare`, `go test`, or `make test`, stop and use this skill first to ensure correct container execution.
How do I install it?
Run `npx skills add runkids/skillshare --skill skillshare-devcontainer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From runkids/skillshare, a repository with 2,519 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.