ship-check
/ship-check
Pre-launch audit for a web app - leaked secrets in client code, Supabase keys and Row Level Security, Stripe webhook signature checks, and the basics Google needs to index the site (real links, real URLs, unique titles, no leftover noindex). Use before launching, before a big deploy, or when the user asks "is this safe to ship?" or "why isn't my site on Google?".
- Author
- raymondaalvarez ↗
- Repository
- claude-code-starter-kit ↗
- Licence
- MIT
- Last repository change
- 08.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 08.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Pre-launch audit for a web app - leaked secrets in client code, Supabase keys and Row Level Security, Stripe webhook signature checks, and the basics Google needs to index the site (real links, real URLs, unique titles, no leftover noindex). Use before launching, before a big deploy, or when the user asks "is this safe to ship?" or "why isn't my site on Google?".
Triggers from the description
Original author description
Pre-launch audit for a web app - leaked secrets in client code, Supabase keys and Row Level Security, Stripe webhook signature checks, and the basics Google needs to index the site (real links, real URLs, unique titles, no leftover noindex). Use before launching, before a big deploy, or when the user asks "is this safe to ship?" or "why isn't my site on Google?".
How it works
- Security
- Can Google index it?
- Output
SKILL.md preview
--- name: ship-check description: Pre-launch audit for a web app - leaked secrets in client code, Supabase keys and Row Level Security, Stripe webhook signature checks, and the basics Google needs to index the site (real links, real URLs, unique titles, no leftover noindex). Use before launching, before a big deploy, or when the user asks "is this safe to ship?" or "why isn't my site on Google?". --- # Ship check Audit the project for the items below. **Report first, change nothing yet.** For each finding give the file and line, why it matters (one sentence), and the proposed fix. Then wait for the user's OK. ## Security 1. Secrets in client code: any secret in a `NEXT_PUBLIC_` or `VITE_` variable, or otherwise bundled into code the browser downloads. 2. A Supabase secret / `service_role` key used anywhere outside server code. 3. Supabase tables without Row Level Security enabled, or with policies that let anyone read or write private data (check migrations and `supabase/` SQL). 4. Stripe webhook handlers that don't verify the `Stripe-Signature` header with the endpoint secret on the raw request body, or that grant access from data the browser sends. ## Can Google index it? 5. Navigation built with buttons or `onClick` handlers instead of `<a href>` links (or the framework's Link). 6. Hash routes (`/#/page`) instead of real URLs. 7. Pages that share the same `<title>` or meta description (including template defaults like "Vite + React"). 8. Any `noindex` robots meta tag or `X-Robots-Tag` header, or a `robots.txt` rule that blocks the site. ## Output A table: `# | finding | file:line | fix`, sorted most serious first, then "Nothing found" for each item that's clean. End by asking which fixes to apply. Sources: Next.js and Vite env var docs, Supabase API keys and RLS docs, Stripe webhooks docs, Google Search Central (crawlable links, JavaScript SEO basics, title links, block indexing).
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · raymondaalvarez/claude-code-starter-kit | 90 | MIT |
| danielmedinac22/pmai-skills | 100 | MIT |
| nirkaufman/claude-code-workshop-assets | 100 | MIT |
| subculture-collective/generic-skills | 90 | GPL-3.0 |
| DimitriSmagliy/loop-ai-skills | 90 | MIT |
Database snapshot: 13.11.2026 · package version b3e138b6a2cb (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100check
Pre-launch security and production-readiness audit for AI-built ("vibe-coded") apps. Finds leaked API keys, secrets shipped to the browser, missing Supabase RLS or open Firebase rules, API routes without auth or ownership checks, Stripe and AI-endpoint billing abuse ("denial of… - 100viberaven
Use for Supabase RLS and migrations, grants and 42501 errors, a service role key in client code, Vercel env vars, Stripe webhook signature checks, or a Vercel + Supabase review before deploy. Choose local repository checks or hosted SQL/error guidance by the actual tools… - 100viberaven
Use for Supabase RLS and migrations, grants and 42501 errors, a service role key in client code, Vercel env vars, Stripe webhook signature checks, or a Vercel + Supabase review before deploy. Choose local repository checks or hosted SQL/error guidance by the actual tools… - 100vibe-preflight
Pre-launch security scan for Supabase + Stripe apps (Next.js, Vite, Expo; Lovable, Bolt, Cursor and Claude Code builds). Finds tables without Row Level Security, `using (true)` policies, user-editable plan/role columns, views and SECURITY DEFINER functions that skip RLS, exposed… - 100supabase-rls-audit
Security audit of Supabase Row Level Security and database exposure for any app on Supabase (Flutter, Next.js, React, Expo, SvelteKit). Use when asked to check or review RLS policies, Supabase security, "can users see each other's data", migrations in supabase/migrations,… - 95memstack-security-rls-checker
Use this skill when the user says 'check RLS', 'audit RLS', 'RLS policies', 'row level security', 'Supabase security audit', or needs to verify table-level access control. Audits Supabase Row Level Security policies across all tables. Do NOT use for non-Supabase projects or…