get-started-stinger — Claude Code skill: install
The get-started-stinger skill brings a new or incomplete repository to a documented baseline with CI and project-health files. Use it during first-session setup or when wasp-nest.lock is missing.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install wasp-nest-core@wasp-nestWhat get-started-stinger does
get-started-stinger inspects the repository root, then copies setup files in dependency order. Its templates cover .gitignore, .editorconfig, .nvmrc, .env.example, .github/ workflows and templates, README.md, contributor and security files, a changelog, and library/. Placeholder values such as {placeholder} are resolved from repository signals like package.json, the git remote, LICENSE, and the lockfile.
The skill is safe to rerun. Missing files are created, matching files remain untouched, and differences are reported rather than overwritten. Each run ends with a report of existing files, files created during the run, and decisions that require a repository owner. It does not change GitHub Settings such as branch protection, push protection, CodeQL, or license selection. For repositories that already contain code, knowledge-stinger runs before wasp-nest.lock is written.
What it helps with
- bootstrap a new repository before feature work
- add starter GitHub CI and repository templates
- create baseline security and maintenance files
- report drift during repeated setup runs
- summarize files created in the current run
Example prompts for the agent
- Set up this new repository with the starter baseline and report every file you create.
- Add the missing CI and repository-health files, but leave existing hand-edited files untouched.
- Run the repository checks, then create
wasp-nest.lockonly after the setup passes.
How to install get-started-stinger
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install wasp-nest-core@wasp-nestThis installs the whole wasp-nest-core plugin with all its skills
2Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill get-started-stinger -a claude-code3Manually: put the files in place
~/.claude/skills/get-started-stinger/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/get-started-stinger/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill get-started-stinger -a codex2Manually: put the files in place
.agents/skills/get-started-stinger/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill get-started-stinger -a cursor2Manually: put the files in place
.cursor/skills/get-started-stinger/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install legioncodeinc/vibe-coding-tools plugins/wasp-nest-core/skills/get-started-stinger2Manually: put the files in place
.github/skills/get-started-stinger/SKILL.md1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill get-started-stinger -a gemini-cli2Platform CLI
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/wasp-nest-core/skills/get-started-stingerManually: put the files in place
.devin/skills/get-started-stinger/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about get-started-stinger
How do I install get-started-stinger in Claude Code?
Add the marketplace with /plugin marketplace add legioncodeinc/vibe-coding-tools, then install the plugin with /plugin install wasp-nest-core@wasp-nest. Run npx skills add legioncodeinc/vibe-coding-tools --skill get-started-stinger -a claude-code, then check ~/.claude/skills/get-started-stinger/SKILL.md.
What does get-started-stinger do?
It initializes a new or partially configured repository with documentation, GitHub CI, README content, and project-health files. On later runs, it reports drift instead of replacing manual edits.
Does the skill change GitHub repository settings?
No. Branch protection, push protection, CodeQL, license selection, and similar GitHub Settings actions remain human decisions because the skill has no API or admin access.