78% of Fortune 500 companies are adopting AI coding assistants. 45% of that generated code ships with security vulnerabilities. On the content side, 76% of readers identify AI-written text within three seconds, and engagement drops around 47% when they do.
Those three numbers describe the same problem from two angles: AI outputs need guardrails, whether the output is code or writing. Today we're shipping two Claude Code skill packs that sit on those guardrails.
A Claude Code skill is a packaged slash command that augments your AI coding agent with a specific expertise, readable via SKILL.md and invocable from any AGENTS.md-compatible runtime. The Skills Wave is two of those packs, released the same day because the failure modes on both sides of the AI workflow deserve the same fix.
I'm Kacper, AI Engineer at Vstorm, an Applied Agentic AI Engineering Consultancy. We've shipped 30+ production AI agent implementations and open-source our tooling at github.com/vstorm-co.
production-stack-skills: 10 Claude Code Skills for Production-Ready AI Code
production-stack-skills is a 10-skill pack that audits AI-generated code across six weighted categories and hands back a 0 to 100 production-readiness score with a prioritized action plan.
The flagship command is /production check. You point it at a repo, it reads the FastAPI routes, Postgres migrations, Dockerfiles, and config, and returns:
- A headline score (e.g., "Production Readiness: 34/100")
- Six category scores: security, error handling, observability, deployment, data layer, code quality
- A Quick Wins section with point deltas
- An Action Plan sorted by weighted impact
In first internal runs across client repos, Quick Wins alone consistently moves the score about 30 points. That's the number I'd quote if a CTO asked "what does running this for a morning actually buy me".
The other nine skills split by surface area: /production review, /production planner, /production fastapi, /production postgres, /production docker, /production deploy, /production monitoring, /production security, /production error-handling. Each is a focused slash command rather than a sub-mode of a monolithic agent.
content-skills: 14 Brand-First Skills That Kill AI Slop
content-skills is a 14-skill pack with a /brand/ directory at its core, so every piece of content generated after a five-minute brand interview reads your BRAND.md, VOICE.md, VISUAL.md, and voice samples before writing a word.
Run /content setup once. Five questions. It writes /brand/. From that moment, every content skill auto-reads that directory on every invocation.
The exit point is /content audit. Score any piece of content 0 to 100 on voice consistency, anti-slop markers, visual consistency, and brand alignment.
Between setup and audit sit 12 production skills: strategy, calendar, blog, twitter, linkedin, reddit, hackernews, presentation, infographic, image, video, repurpose.
One Install, Dual-CLI, Uninstall-Safe
curl -fsSL https://raw.githubusercontent.com/vstorm-co/production-stack-skills/main/install.sh | bash
curl -fsSL https://raw.githubusercontent.com/vstorm-co/content-skills/main/install.sh | bash
Each install mirrors the skills into both ~/.claude/ (Claude Code) and ~/.agents/ (Codex, Amp, and anything AGENTS.md-compatible). You don't pick the runtime up front. A skill written for Claude Code works identically in Codex.
Uninstall is boring by design. /content-skills uninstall removes the skills. Your /brand/ stays.
Both repos are MIT.
Why Two Packs Shipped the Same Day
In 30+ production AI agent deployments at Vstorm, the failures cluster into two shapes: code that passes demo but fails the first prod incident, and content that sounds like the AI wrote it because the AI wrote it.
One pack addresses the first. The other addresses the second. Both use the same architecture because the lesson that skills beat monolithic agents applies to both. You don't want "one AI that does everything". You want 24 small, composable, auditable slash commands that you can swap, tune, or remove when they stop pulling weight.
Key Takeaways
- production-stack-skills ships 10 skills with a 0-100 scorer and Quick Wins section that typically moves scores +30 in under five minutes.
-
content-skills ships 14 skills built around a
/brand/directory auto-read on every invocation. - Both packs install via one
curlcommand, mirror into~/.claude/and~/.agents/, work on Claude Code, Codex, and any AGENTS.md-compatible runtime. - Skill-first architecture beats monolithic agents for auditability and local updates.
- Both repos are MIT.
Frequently Asked Questions
What are Claude Code skills and how do I install them?
Claude Code skills are packaged slash commands backed by a SKILL.md file that extends a coding agent with specific expertise. You install a skill pack with a single curl command that mirrors files into ~/.claude/ and ~/.agents/. After install, slash commands become available immediately without restart.
What's the difference between production-stack-skills and content-skills?
production-stack-skills audits and hardens AI-generated code across security, error handling, observability, deployment, data, and code quality, returning a 0-100 score. content-skills audits and produces on-brand content using a /brand/ directory you set up once, returning voice-consistency and anti-slop scores.
Do these skills work with Codex or only Claude Code?
Both. Each install script mirrors files into both ~/.claude/ and ~/.agents/, so the same skill works in Claude Code, Codex, Amp, and any AGENTS.md-compatible runtime without modification.
How long does /production check take on a real repo?
On a typical FastAPI + Postgres repo of a few thousand lines, about a minute. The Quick Wins section is what you act on first, usually under five minutes to apply.
When should I use a Claude Code skill instead of writing a full agent?
Use a skill when the job is scoped expertise invoked explicitly (audit this, write a post in my voice). Use a full agent when the job is open-ended, multi-step, and requires planning across tools. Skills are composable building blocks; agents orchestrate them.
Get Started
- production-stack-skills: github.com/vstorm-co/production-stack-skills
- content-skills: github.com/vstorm-co/content-skills
- Full writeup: oss.vstorm.co/blog/skills-wave-launch-claude-code-skills
Follow me on LinkedIn for the follow-ups: Wednesday's production deep-dive, Thursday's content walkthrough, Friday's "8 Lessons from Shipping 24 Claude Code Skills".