Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Production readiness audit - checks unwrap elimination, error handling, clippy, docs, channel usage, and test count.
Install Check Production Ready
$ npx skills add nwiizo/ccswarm --skill check-production-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nwiizo/ccswarm check-production-ready --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nwiizo/ccswarm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/check-production-ready .claude/skills/check-production-ready && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "check-production-ready" agent skill from https://github.com/nwiizo/ccswarm/tree/master/.agents/skills/check-production-ready into .claude/skills/check-production-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-production-ready", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nwiizo/ccswarm/tree/master/.agents/skills/check-production-readyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nwiizo/ccswarm --skill check-production-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nwiizo/ccswarm check-production-ready --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nwiizo/ccswarm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/check-production-ready .agents/skills/check-production-ready && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "check-production-ready" agent skill from https://github.com/nwiizo/ccswarm/tree/master/.agents/skills/check-production-ready into .agents/skills/check-production-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-production-ready", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nwiizo/ccswarm --skill check-production-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nwiizo/ccswarm check-production-ready --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nwiizo/ccswarm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/check-production-ready .cursor/skills/check-production-ready && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "check-production-ready" agent skill from https://github.com/nwiizo/ccswarm/tree/master/.agents/skills/check-production-ready into .cursor/skills/check-production-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-production-ready", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nwiizo/ccswarm.git --path .agents/skills/check-production-ready--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nwiizo/ccswarm --skill check-production-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nwiizo/ccswarm check-production-ready --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nwiizo/ccswarm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/check-production-ready .gemini/skills/check-production-ready && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "check-production-ready" agent skill from https://github.com/nwiizo/ccswarm/tree/master/.agents/skills/check-production-ready into .gemini/skills/check-production-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-production-ready", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nwiizo/ccswarm check-production-readyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nwiizo/ccswarm --skill check-production-ready -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nwiizo/ccswarm.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/check-production-ready .github/skills/check-production-ready && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "check-production-ready" agent skill from https://github.com/nwiizo/ccswarm/tree/master/.agents/skills/check-production-ready into .github/skills/check-production-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-production-ready", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nwiizo/ccswarm --skill check-production-ready -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nwiizo/ccswarm check-production-ready --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nwiizo/ccswarm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/check-production-ready .opencode/skills/check-production-ready && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "check-production-ready" agent skill from https://github.com/nwiizo/ccswarm/tree/master/.agents/skills/check-production-ready into .opencode/skills/check-production-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-production-ready", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
check-production-ready- GitHub stars
- 153
- Token cost
- ~246 tokens
- SKILL.md length
- 90 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Production readiness audit - checks unwrap elimination, error handling, clippy, docs, channel usage, and test count.
- Development work in your project
- Calls cargo
What it does
Check Production Ready is an agent skill from nwiizo/ccswarm. Production readiness audit - checks unwrap elimination, error handling, clippy, docs, channel usage, and test count.
Its SKILL.md is about 250 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: Multi-agent orchestration system using Claude Code with Git worktree isolation and specialized AI agents for collaborative development. The licence is MIT.
When your agent uses it
- Development work in your project
Example prompts
- “/check-production-ready”
What it can do on your machine
Read from SKILL.md and the folder at commit 611bf15. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
cargo
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Check Production Ready loads about 246 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 90 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from nwiizo/ccswarm at commit 611bf15, republished under its MIT licence (© nwiizo). 90 words, ~246 tokens.
Download SKILL.mdSave it as
.claude/skills/check-production-ready/SKILL.md (or your agent's skills folder).- name
- check-production-ready
- description
- Production readiness audit - checks unwrap elimination, error handling, clippy, docs, channel usage, and test count.
- user-invocable
- true
- context
- fork
- agent
- rust-fix-agent
When subagents are enabled in Codex, prefer delegating this workflow to the rust-fix-agent custom agent.
Verify 7 production quality criteria:
| # | Item | Check |
|---|---|---|
| 1 | unwrap() elimination | grep -r "\.unwrap()" crates/ccswarm/src/ --include="*.rs" (exclude tests) |
| 2 | Error handling | thiserror usage, custom error types |
| 3 | Async patterns | tokio runtime, proper async usage |
| 4 | Documentation | cargo doc --workspace --no-deps |
| 5 | Clippy clean | cargo clippy --workspace -- -D warnings |
| 6 | Channel-Based | Channel vs Arc<Mutex> ratio |
| 7 | Minimal testing | ~8-10 focused tests |
Score: 7/7 = PRODUCTION_READY, 5-6/7 = NEEDS_WORK, 0-4/7 = CRITICAL.
Fix any issues found, then report results as JSON.
© nwiizo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/check-production-ready of nwiizo/ccswarm.
Open the folder on GitHubat commit 611bf15
Compare with similar skills
Check Production Ready next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Check Production Ready this skillnwiizo/ccswarm | 153 | — | ~246 | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 4 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from nwiizo/ccswarm
All 12 skills in this repoDeploy Workflow
nwiizo/ccswarm
Release deployment process for ccswarm. An agent skill from nwiizo/ccswarm.
Review Fix
nwiizo/ccswarm
Review uncommitted changes, fix actionable correctness issues, and verify the result.
Review Fix
nwiizo/ccswarm
Code review with automatic fix. An agent skill from nwiizo/ccswarm.
Review Fix
nwiizo/ccswarm
Code review with automatic fix. An agent skill from nwiizo/ccswarm.
Nwiizo Coding Style
nwiizo/ccswarm
nwiizoの方針でコードを実装・修正し、過剰設計をレビューする。最小実装・YAGNIの依頼にも使う。Rustでは型・所有権・依存の選定、Edition・MSRVに応じた機能選択と構造診断を行う。
Benchmark Runner
nwiizo/ccswarm
Run performance benchmarks with criterion. An agent skill from nwiizo/ccswarm.
Related
Categories
Questions about Check Production Ready
What does Check Production Ready do?
Production readiness audit - checks unwrap elimination, error handling, clippy, docs, channel usage, and test count. Check Production Ready is an agent skill from nwiizo/ccswarm. Production readiness audit - checks unwrap elimination, error handling, clippy, docs, channel usage, and test count.
When should I use Check Production Ready?
Check Production Ready fits situations like: development work in your project.
How do I install Check Production Ready in Claude Code?
Run `npx skills add nwiizo/ccswarm --skill check-production-ready -a claude-code`. Or copy the skill folder (.agents/skills/check-production-ready in nwiizo/ccswarm) into .claude/skills/check-production-ready in your project. Claude Code loads it when a task matches its description.
How do I install Check Production Ready in Codex?
Run `npx skills add nwiizo/ccswarm --skill check-production-ready -a codex`. Or copy the skill folder (.agents/skills/check-production-ready in nwiizo/ccswarm) into .agents/skills/check-production-ready in your project. Codex loads it when a task matches its description.
Can I use Check Production Ready in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nwiizo/ccswarm --skill check-production-ready -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/check-production-ready, .gemini/skills/check-production-ready, .github/skills/check-production-ready and .opencode/skills/check-production-ready in your project.
What does Check Production Ready need to run?
Going by SKILL.md and its folder, Check Production Ready needs the command-line tools its instructions call (cargo).
Does Check Production Ready access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Check Production Ready safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Check Production Ready use?
Check Production Ready is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Check Production Ready use?
About 246 tokens (SKILL.md is roughly 984 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Check Production Ready?
Skills that share tags, products or a category with Check Production Ready: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Check Production Ready?
nwiizo (a GitHub user) maintains it in nwiizo/ccswarm, which has 153 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 9, 2026.
Source: nwiizo/ccswarm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.