payment-audit
Determine what a repo can actually charge for and what it is exposed to — by reading the code, not the landing page.
When this skill is meant to trigger
Determine what a repo can actually charge for and what it is exposed to — by reading the code, not the landing page. Inventories payment infrastructure (Stripe/Paddle/LemonSqueezy keys, checkout routes, webhook handlers, price IDs, entitlement logic), auth and PII surfaces, database tables holding user or minor data, and the gap between published prices and working checkouts. Produces a per-repo Revenue Readiness record that answers: can this take a dollar today, what is missing, and what liability is it carrying while earning nothing. Trigger on: 'payment audit', 'can this take money', 'revenue readiness', 'is Stripe wired up', 'why can't this charge', 'audit payment infra', 'what's my checkout status', 'do we collect PII', 'does this hold student data', 'FERPA check', 'COPPA check', 'auth without revenue', 'wire up checkout', 'add Stripe'. Run this in a repo with filesystem and shell access — it is useless from a browsing-only environment.
Parts of this skill expect files, a shell, or a browser. It works from your input and returns any files inline.
Fast and cheap. The default for most skills. Catalog rates $0.3 in and $2.5 out per million tokens. The receipt uses OpenRouter's billed cost.
Paste your input and run the skill. The result is written here as it streams.