Conciseness

The body is dominated by lean, executable code with terse steps, but the opening paragraph ("Wire Stripe to Convex using @convex-dev/stripe: a checkout action, an httpAction webhook registered by the component (signature-verified automatically), subscription state stored in the component's tables...") restates what the Workflow shows, signature-verification handling is stated twice (step 4 and the Rules bullet), and the version pin "@convex-dev/stripe@^0.1.4" is time-sensitive without a deprecated/old-patterns section. Not 5 for these minor trims; well above 3 since nothing explains concepts Claude already knows.

Actionability

Three complete, copy-paste-ready files (convex.config.ts, convex/http.ts, convex/billing.ts with argument/return validators and auth checks), exact commands ("npm install @convex-dev/stripe", "npx convex dev --once"), and dashboard steps naming exact webhook events. The common cases (checkout, webhook registration, subscription gating) are all covered with executable code; the one delegation ("use the `env` micro power" for keys) is explicit rather than a gap.

Workflow Clarity

Seven clearly sequenced steps with one explicit validation checkpoint ("Verify output shows `✔ Installed component stripe.`"), plus a gotcha called out (the required .js import extension). Not 5 because there is no end-to-end webhook verification or error-recovery loop (e.g., testing with a Stripe CLI event or a test checkout run); not 3 because a concrete checkpoint and key pitfalls are present, and the operation is additive rather than destructive/batch.

Progressive Disclosure

This is a single-file skill with no references/, scripts/, or assets/ directories, and all content is needed for the one task. It is well organized into a short overview, a numbered Workflow, and a Rules section, with no inlined material that belongs in separate files — matching the simple-skill exception where well-organized sections alone warrant a 5.

Specificity

"Add Stripe billing/payments to the Convex app via @convex-dev/stripe (checkout + webhook + gating)" names the domain, the exact component, and three concrete actions (checkout, webhook, gating). It falls short of 5 because coverage has minor gaps — e.g., subscriptions/customers, which the body actually implements, are not mentioned.

Completeness

The 'what' is clear and concrete (add Stripe billing via the component: checkout + webhook + gating), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' is specific rather than vague.

Trigger Term Quality

Natural terms users would say are present: "Stripe", "billing/payments", "checkout", "webhook", plus the specific package name @convex-dev/stripe. A few natural terms are missing — notably "subscriptions" (the flow is subscription-gating), "paywall", and "upgrade" — so it does not reach 5.

Distinctiveness Conflict Risk

"to the Convex app via @convex-dev/stripe" carves out a clear niche — Convex + Stripe + a specific npm component — so it is unlikely to trigger for generic payment or non-Convex Stripe skills. Clear niche with distinct triggers and minimal conflict risk.