deploy-check
Skill1 starsChanged 6 months agoMITView on GitHub
Check whether a website, web app, or AI-built product is actually production-ready: domain, SSL, env vars, backend/API, database, auth, email/SMS, storage, payment, CMS, analytics, monitoring, SEO, privacy, backup, and rollback.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- Bartolome69/garmin-mcptheir own version, first seen Nov 1, 2026
- ProxiBlue/claude-skillstheir own version, first seen Oct 7, 2026
- faizkhairi/claude-code-blueprinttheir own version, first seen Jul 3, 2026
- GlamgarOnDiscord/claude-saas-blueprinttheir own version, first seen May 17, 2026
- tadeurosa-ai/claude-code-setuptheir own version, first seen May 1, 2026
- mean-weasel/bullhorntheir own version, first seen Apr 14, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- nwiizo/claudelytics★ 88same name
- faizkhairi/claude-code-blueprint★ 73same name
- ProxiBlue/claude-skills★ 18same name
- Bartolome69/garmin-mcp★ 4same name
- mean-weasel/bullhorn★ 4same name
- GlamgarOnDiscord/claude-saas-blueprint★ 2same name
- kawehtaher/deploycheck★ 1same name
- tadeurosa-ai/claude-code-setup★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/audit-live-workbench.mdcCursor rule
- accept-fiveSkill
- agent-diagnoseSkill
- ai-product-auditSkill
- auditSkill
- flow-testSkill
- harnessSkill
- physical-flow-testSkill
- skill-studySkill
- visual-qaSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use this skill to expose what is missing before a site or app can be called production-ready.
- Distinctive: line 19
Check every deployment readiness row.
- Very specific: line 23
Use S0-S4 severity; production blockers are usually S0 or S1.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deploy Check
Use this skill to expose what is missing before a site or app can be called production-ready.
Do
- Identify the product's runtime dependencies.
- Separate visible proof from source claims.
- Inventory deployment-relevant public surfaces: forms, auth, uploads, payment, documents, third-party scripts, APIs, storage, analytics, and security headers.
- Apply the permission model before testing production dependencies or authenticated paths.
- Check every deployment readiness row.
- Mark unknown dependencies as
UNKNOWN, not pass. - Flag fake-complete demos where UI exists but backend, persistence, auth, or email is unproven.
- Produce a deployment readiness table and blocker list.
- Use
S0-S4severity; production blockers are usuallyS0orS1. - Emit progress updates after major dependency groups when the check spans more than a few items.
Reference
Read references/deployment-readiness.md.
For broad production reviews, also read ../audit/references/web-surface-discovery.md, ../audit/references/permission-model.md, and ../audit/references/progressive-reporting.md.
Output
- Deployment readiness table.
- Production blockers.
- Unknown dependency list.
- S0-S4 severity.
- Copyable setup/fix prompts.
- Regression checks.
- Lessons.
- Final readiness verdict.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.