SkillAgentSearch skills...

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 en…

Install / Use

npx skills add runkids/skillshare --skill skillshare-devcontainer

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Supported Platforms

Universal

Tags

Our assessment of skillshare-devcontainer

skillshare-devcontainer scores 93/100 on our quality scale, 696th of 4,698 Development & Engineering skills we index (top 15%).

Its SKILL.md is 7.9 KB long, well organised into 26 sections with 10 code examples: a thorough specification that gives an agent plenty to work with.

With 2,689 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so skillshare-devcontainer is actively maintained.
  • Our last check on 2026-10-26 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

skillshare-devcontainer compared with similar skills

All 4 of these similar skills score higher than skillshare-devcontainer; compare them before choosing.

SkillScoreStarsUpdatedFormat
skillshare-devcontainer (this skill)by runkids932.7k54d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install skillshare-devcontainer?
Run npx skills add runkids/skillshare --skill skillshare-devcontainer. The install tabs above show the steps for each supported agent.
Which AI agents does skillshare-devcontainer work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is skillshare-devcontainer safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is skillshare-devcontainer still maintained?
The repository was last updated about 2 months ago, so skillshare-devcontainer is actively maintained.

name: skillshare-devcontainer description: >- 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. argument-hint: "[command-to-run | task-description]" metadata: targets: [claude, universal]

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.

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 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.

Zero-Rebuild Workflow

Source code is bind-mounted into the container at /workspace. The ss wrapper runs go build transparently on every invocation:

  1. Edit files on host (Read/Edit tools)
  2. docker exec $CONTAINER ss <command> — picks up your changes instantly
  3. No make build, no restart, no rebuild step

This also applies to go test — tests always compile against the latest source. The Web UI backend uses air for hot-reload (same zero-rebuild experience).

Entering the Devcontainer

The quickest way — one command builds, initialises, and enters the shell:

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

Works with or without VS Code — make devc handles the full lifecycle autonomously.

Programmatic access (for docker exec workflows)

CONTAINER=$(docker compose -f .devcontainer/docker-compose.yml ps -q skillshare-devcontainer 2>/dev/null)

If $CONTAINER is empty, tell the user:

Devcontainer is not running. Start it with make devc-up.

Then verify the binary:

docker exec $CONTAINER bash -c \
  '/workspace/.devcontainer/ensure-skillshare-linux-binary.sh && ss version'

Running Commands

Simple command (uses container's default HOME)

docker exec $CONTAINER ss <command> [flags]

Good for: ss version, ss status, ss list, ss check, ss audit.

Command with isolated HOME (clean state)

ENV_NAME="test-$(date +%s)"
docker exec $CONTAINER ssenv create "$ENV_NAME" --init
docker exec $CONTAINER ssenv enter "$ENV_NAME" -- ss status
# Cleanup when done:
docker exec $CONTAINER ssenv delete "$ENV_NAME" --force

Good for: testing init, install, sync, uninstall — anything that modifies config/state.

Multi-command sequence

docker exec $CONTAINER ssenv enter "$ENV_NAME" -- bash -c '
  ss install runkids/demo-skills --track --force
  ss list
  ss sync
'

Always use bash -c '...' for multi-command sequences inside ssenv enter.

Go tests

# All tests (unit + integration)
docker exec $CONTAINER bash -c 'cd /workspace && make test'

# Unit tests only
docker exec $CONTAINER bash -c 'cd /workspace && make test-unit'

# Integration tests only
docker exec $CONTAINER bash -c 'cd /workspace && make test-int'

# Specific test
docker exec $CONTAINER bash -c 'cd /workspace && go test ./tests/integration -run TestInit_Fresh -count=1'

# Specific package
docker exec $CONTAINER bash -c 'cd /workspace && go test ./internal/install/... -count=1'

Always cd /workspace before Go commands — ssenv changes HOME which can break module resolution.

Go tests with auth disabled

Token-resolution tests (TestResolveToken, TestAuthEnv in internal/install) need auth credentials removed:

docker exec $CONTAINER bash -lc '
  eval "$(credential-helper --eval off)"
  cd /workspace
  go test ./internal/install -run "TestResolveToken|TestAuthEnv" -count=1
  eval "$(credential-helper --eval on)"
'

Web UI Dashboard

# Start (global mode)
docker exec $CONTAINER ui

# Start (project mode — uses ~/demo-project)
docker exec $CONTAINER ui -p

# Stop
docker exec $CONTAINER ui stop

Dashboard accessible at http://localhost:45173 (Vite dev server with HMR). API backend at http://localhost:49420. Logs: /tmp/api-dev.log, /tmp/vite-dev.log.

ssenv Quick Reference

| Shortcut | Full form | Purpose | |----------|-----------|---------| | ssnew <name> | ssenv create <name> + enter | Create and enter isolated shell | | ssuse <name> | ssenv enter <name> | Enter existing isolated shell | | ssrm <name> | ssenv delete <name> --force | Delete environment | | ssls | ssenv list | List all environments | | ssback | ssenv reset | Leave isolated context | | sshelp | help | Show all devcontainer commands |

For automation (non-interactive), prefer ssenv enter <name> -- <command> over ssnew/ssuse (which launch subshells).

Ports

| Port | Service | Notes | |------|---------|-------| | 45173 | Vite dev server | React dashboard with HMR | | 49420 | Go API backend | skillshare ui server | | 48888 | Docusaurus | docs command in devcontainer |

Common Mistakes to Avoid

  1. Running ss on host — macOS binary won't match Linux container; always docker exec
  2. Forgetting cd /workspace — Go tests fail if HOME was changed by ssenv
  3. Using make test on host — builds macOS binary, then tests run against wrong arch
  4. Skipping --init on ssenv create — env won't have config; most commands will fail
  5. Not cleaning up ssenv — ssenv delete <name> --force after done; or ask user
  6. Running from /workspace root without -g — the ss wrapper auto-redirects to ~/demo-project in project mode; use -g for global or set SKILLSHARE_DEV_ALLOW_WORKSPACE_PROJECT=1
  7. Running make build before testing — unnecessary; the ss wrapper auto-builds from source every time

Rules

Apply the testing topic. If a command recipe here conflicts with that topic or current repo configuration, verify the current configuration and update both in the same change.

Related Skills

View on GitHub
GitHub Stars2.7k
CategoryDevelopment
Updated1mo ago
Forks167

Languages

Go

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions