Give Claude 462 Offline Production Skills with Spawner

A prompt file tells an agent what to do. Spawner Skills treats each skill as a four-file knowledge system: implementation patterns, the gotchas that bite in production, automated checks, and rules for handing off to other skills. One install command puts 462 of them on your machine — free, and working offline.

Why This Skill Matters

The repo's headline claim is "462 production-grade skills for Claude. Zero cost, works offline. Full MCP integration." That count holds up: the README's 35-category table sums to exactly 462, from game-dev (51 skills) and marketing (36) down to startup (3). The 880-star leaderboard snapshot is what put it on the board.

The four files per skill each carry a different kind of knowledge: skill.yaml holds identity, patterns, anti-patterns, and handoffs; sharp-edges.yaml documents gotchas with severity levels and detection patterns; validations.yaml defines automated quality checks, including regex checks; collaboration.yaml wires skills to delegate to each other.

Installation

The full setup installs the skills and configures the MCP server in one command:

# Full setup: Skills + MCP server (recommended)
npx github:vibeforge1111/vibeship-spawner-skills install --mcp

This installs 462 skills to ~/.spawner/skills/, configures the Spawner MCP server for Claude Desktop and Claude Code, and enables project memory, code validation, and sharp edge detection. Skills-only and manual-clone paths are documented too (install without --mcp, or clone into ~/.spawner/skills), plus update and status commands.

Real Workflow: Pressure-Test a Micro-SaaS Idea

1. Install with --mcp. Beyond local skills, six MCP tools become available: spawner_orchestrate auto-routes requests, spawner_validate runs guardrail checks, spawner_watch_out surfaces relevant sharp edges, spawner_skills searches and loads skills by context, spawner_remember saves decisions, and spawner_unstick helps when you are going in circles.
2. Point Claude at the launcher skill directly — the README's documented usage is a plain file read:

Read: ~/.spawner/skills/maker/micro-saas-launcher/skill.yaml
Build the MVP for my scheduling tool using the 2-Week MVP pattern.

3. The skill pushes back before you over-build. Its sharp edges include a critical one, no-distribution-plan: building without knowing where customers come from, with symptoms like "I'll figure out marketing later". Its validations flag a project with no payment integration as "you're building a hobby, not a business."
4. Chain the team. collaboration.yaml documents combinations — the "Full SaaS Launch" workflow runs micro-saas-launcher + stripe for an MVP with payments, then landing-page-design, then seo for organic growth.

Tips

• Skill packs scope the set: essentials (auto-installed) for app building, complete for all 462, with packs for finance, education, enterprise, and more.
• Skills work without the MCP server — Claude reads the YAML files directly from ~/.spawner/skills/.
• Sharp edges carry severity levels (critical, high, medium, low); start with the critical ones.
• Browse the full directory on the project's site (linked from the README) before installing, to see whether your stack is covered.

When Not to Use This

The system is built around Claude — the skills live in ~/.spawner/skills/ for Claude to read, and the MCP server targets Claude Desktop and Claude Code. The leaderboard snapshot also records the repo's last push in January 2026; check upstream activity before betting a production workflow on it. And 462 skills is a lot of surface area — rely on search (spawner_skills) or direct file reads rather than loading everything at once.

See the leaderboard for more skills.