Conciseness

The body is mostly lean and Stripe-specific, but it inlines time-sensitive version data outside any 'old patterns'/'deprecated' section: 'Latest Stripe API version: 2026-08-26.dahlia', a full 7-language 'Latest SDK versions' table (Ruby 19.6.0 … .NET 52.4.0), and a dated reference to 'API version 2026-03-25.dahlia'. These stale-prone version numbers cost tokens now and will rot, which fits the 'mostly efficient but includes some unnecessary content' anchor rather than the 'minor trim' anchor above it.

Actionability

Guidance is fully concrete and executable: exact commands ('npm i -g @stripe/cli', 'stripe sandbox create', 'stripe whoami --format json'), exact endpoints ('Accounts v2 (/v2/core/accounts)'), and exact parameter-level rules ('automatic_tax: { enabled: true }', "payment_method_types: ['card_present']", 'allowed_payment_method_types', 'integration_identifier'). The explicit deprecated-pattern list ('stripe.api_key = …', 'Stripe.setApiKey', 'stripe.Key = …') makes the rules copy-checkable; absence of full code samples is appropriate for an instruction/routing skill.

Workflow Clarity

The integration routing table plus 'Read the relevant reference file before answering any integration question or writing code' gives a clear, unambiguous decision sequence, and the tax rule includes a real pre-flight checkpoint ('confirm the user has an active registration' before enabling automatic_tax). Not a 5 because other checkpoints are implicit rather than explicit — the webhook fulfillment gating and the go-live checklist are stated as rules or afterthoughts rather than sequenced validation steps. Not a 3 because the sequence that exists is coherent and the main failure mode (most common Stripe Tax mistake) is explicitly guarded.

Progressive Disclosure

The body is a true overview routing to six one-level-deep reference files (payments.md, connect.md, billing.md, tax.md, treasury.md, security.md), all of which exist in ./references/ and are clearly signaled per task in the routing table. Not a 5 because the routing links point at absolute web URLs ('[references/payments.md](https://docs.stripe.com/references/payments.md)') instead of relative paths to the bundled files, so navigation can misdirect to the hosted page rather than the local reference.

Specificity

It enumerates many concrete capability areas with specific artifacts: 'development and test environment planning (separate sandboxes vs the shared test mode sandbox)', 'API selection (Checkout Sessions vs PaymentIntents)', 'Connect platform setup (Accounts v2, controller properties)', 'tax and registrations (Stripe Tax, automatic_tax, product tax codes)', 'security best practices (API key management, API key permissions, webhooks, OAuth)'. This matches the 'multiple specific concrete actions; comprehensive coverage' anchor; the abstract opener 'Guides Stripe integration decisions' is fully backed by enumerated specifics, so 4's 'minor gaps' does not fit.

Completeness

Both halves are explicit: 'what' is 'Guides Stripe integration decisions across [nine enumerated domains]' and 'when' is 'Use when planning, building, modifying, testing, or reviewing any Stripe integration, including [eight concrete trigger phrases]'. This mirrors the anchor-5 example structure exactly; 4's 'when could be more explicit' does not apply.

Trigger Term Quality

The 'Use when' clause is dense with natural user phrasing including synonyms: 'accepting payments', 'processing payments', 'building marketplaces', 'setting up subscriptions', 'collecting sales tax, VAT, or GST', 'creating connected accounts', 'implementing secure key handling', 'choosing a development environment'. This matches the comprehensive-with-synonyms anchor; secondary terms (refunds, invoices) are missing but the anchor is coverage of natural terms, which is met.

Distinctiveness Conflict Risk

The skill occupies a clear niche (Stripe integration guidance) with domain-locked triggers ('Checkout Sessions', 'PaymentIntents', 'Stripe Tax', 'connected accounts', 'automatic_tax') that no generic payments, tax, or security skill would claim. Minimal conflict risk; matches the clear-niche anchor.