queen-wasp-stinger — Claude Code skill: setup and features
queen-wasp-stinger — an orchestrator skill for authoring, testing, and packaging Wasp Nest components, subagents, rules, and plugins in Claude Code and Codex.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install wasp-nest-core@wasp-nestWhat queen-wasp-stinger does
This orchestrator manages the lifecycle of every building block in the Wasp Nest framework: standard prompt rules such as CLAUDE.md or .cursor/rules/*.mdc, targeted subagents, commands, and standalone SKILL.md units. It does not dispatch active work across finished agents, leaving that duty entirely to pest-controller-suit.
Authoring runs through an ordered seven-step pipeline. The sequence starts with raw source harvesting into a local directory, builds factual digests with citations, writes runtime guides, and outputs verified skill definitions with harness-specific frontmatter.
Running the included validation and packaging utilities requires a local Python 3.9+ installation.
What it helps with
- build new skills, agent pairs, and custom commands across harness formats
- audit existing Wasp Nest components against current platform schemas
- validate frontmatter metadata and repository directory structures
- package distribution units for environments like Claude Cowork
Example prompts for the agent
- Forge a new database migration skill following the Wasp Nest pipeline
- Validate the current plugin components using the validation script
- Update existing project rules for Codex and Claude Code compatibility
How to install queen-wasp-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 queen-wasp-stinger -a claude-code3Manually: put the files in place
~/.claude/skills/queen-wasp-stinger/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/queen-wasp-stinger/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill queen-wasp-stinger -a codex2Manually: put the files in place
.agents/skills/queen-wasp-stinger/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill queen-wasp-stinger -a cursor2Manually: put the files in place
.cursor/skills/queen-wasp-stinger/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install legioncodeinc/vibe-coding-tools plugins/wasp-nest-core/skills/queen-wasp-stinger2Manually: put the files in place
.github/skills/queen-wasp-stinger/SKILL.md1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill queen-wasp-stinger -a gemini-cli2Platform CLI
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/wasp-nest-core/skills/queen-wasp-stingerManually: put the files in place
.devin/skills/queen-wasp-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 queen-wasp-stinger
How to install queen-wasp-stinger in Claude Code?
Register the catalog with /plugin marketplace add legioncodeinc/vibe-coding-tools, then run /plugin install wasp-nest-core@wasp-nest. Alternatively, execute npx skills add legioncodeinc/vibe-coding-tools --skill queen-wasp-stinger -a claude-code.
When should queen-wasp-stinger be used instead of pest-controller-suit?
Pick this skill whenever you need to create, update, or audit components. If the component exists and needs task routing, call pest-controller-suit instead.
What dependencies are needed for validation scripts?
The authoring scripts require Python 3.9 or higher to execute schema checks and build output distributions.