Full content audit identified inaccuracies verified against source code: Critical fixes: - declarative-manifest: skills: migrated from config.yaml to registry.yaml - private-enterprise-skills: fix token list, add --track, fix dir separator - supported-targets: fix universal canonical name, kimi/replit paths, aliases - with-multiple-tools: fix target list output format, opencode path Moderate fixes: - tracked-repositories, project-skills: update config examples for registry.yaml - skill-format: name rule "underscore" -> "number" (per validSkillNameRegex) - understand/index: fix opencode path in diagram, add copy mode - comparison: ~/.cursor/rules -> ~/.cursor/skills - configuration: fix backups path, add registry migration note - with-devcontainer: add non-interactive flags for postCreateCommand - migration: .source -> .skillshare-meta.json - docker-sandbox: make --cmd -> ./scripts/test_docker.sh --cmd - security: audit rule count 31 -> 32 - ci-cd-skill-validation: production -> CI docker image - cross-machine-sync-recipe: replace unimplemented ignore with include/exclude - environment-variables: add GH_TOKEN entry
2.2 KiB
sidebar_position
| sidebar_position |
|---|
| 5 |
Using skillshare in Dev Containers
Open in VS Code, skills are ready — no local install needed.
Prerequisites
How It Works
VS Code Dev Containers let you develop inside a Docker container. You define the environment in .devcontainer/, and VS Code handles the rest — open the project, click "Reopen in Container", and everything is ready.
skillshare fits naturally into this workflow. Add it to postCreateCommand and skills are installed and synced when the container starts.
Setup
Add two things to your .devcontainer/devcontainer.json:
{
"postCreateCommand": "curl -fsSL https://raw.githubusercontent.com/runkids/skillshare/main/install.sh | sh && skillshare init --no-copy --all-targets --no-skill && skillshare sync"
}
That's it. When a team member opens the project in VS Code and clicks "Reopen in Container":
- skillshare is installed automatically
initruns non-interactively — adds all detected AI CLI targets, skips copy prompts and built-in skill installationsyncdelivers skills to all targets
Adding Project Skills
For team-shared skills, commit a .skillshare/ config to the repo:
# Inside the container
skillshare init -p
skillshare install your-org/team-skills -p
Then commit and update postCreateCommand to also sync project skills:
{
"postCreateCommand": "curl -fsSL https://raw.githubusercontent.com/runkids/skillshare/main/install.sh | sh && skillshare init --no-copy --all-targets --no-skill && skillshare sync && skillshare sync -p"
}
Now every team member gets the same skills when they open the container.
GitHub Codespaces
The same .devcontainer/ config works in Codespaces with no changes. Codespaces runs postCreateCommand the same way VS Code does.