Conciseness

The body is dense with non-obvious domain policy rather than concepts Claude already knows, but it can be tightened: the four-line progress checklist is repeated verbatim four times, the public-preview disclosure requirements appear in both Step 3 guardrails and two Step 4a items, and the SaaS/direct-charge guardrail is a single ~200-word run-on sentence. This matches anchor 3 (mostly efficient but could be tightened) better than anchor 4.

Actionability

Fully executable instruction guidance: exact question scripts ("Tell me about your business. Pick whichever is easiest:"), numbered option sets with defined outcomes, verbatim warning copy ("Your platform fee might be below Stripe's processing fees..."), concrete field names (dashboard, fees_collector, losses_collector, application_fee_amount), named embedded components, and specific links. This is copy-paste-ready guidance for an instruction-only skill, matching anchor 5.

Workflow Clarity

Steps 0–6 are explicitly sequenced with a visible progress checklist, mandatory validation checkpoints ("Step 4a — Compatibility validation (MANDATORY before presenting recommendation)", fee-economics check that "ALWAYS runs, even on auto-filled values"), and explicit feedback loops (BLOCKED combination → recommended fix → "re-run the recommendation with the corrected configuration"; "re-ask the relevant question"). This matches anchor 5's clear sequence with validation and error-recovery loops.

Progressive Disclosure

The body is an orchestration overview that delegates all heavy detail to eight clearly signaled, one-level-deep references (terminology-rules, company-researcher, decision-matrix, discovery-questions, account-types, charge-patterns, compatibility-matrix, recommendation-template), and all eight verified to exist. The gap keeping it from 5: Step 4a's compatibility rules substantially duplicate content that also lives in compatibility-matrix.md, splitting one concern across two places.

Specificity

Concrete domain terms are named ("Stripe Connect configuration, charge patterns, Dashboard access", "split payments", "onboarding or KYC"), but the skill's action is never stated as a capability — "recommendation" appears only indirectly in "provides a company URL or business description for a recommendation". It lists trigger scenarios rather than concrete actions, landing between anchor 3 and anchor 4.

Completeness

The "when" is maximally explicit ("Use this skill when the user asks about...") with concrete trigger phrases, but the "what" is implicit — the description never states the skill recommends a Connect configuration except via the oblique phrase "for a recommendation". Both halves are present with one weaker, matching anchor 4 rather than 5.

Trigger Term Quality

Comprehensive natural-language coverage with synonyms across every trigger family: "marketplace, platform, multi-vendor store, gig platform, or subscription platform", "sellers, vendors, or providers", "split payments, revenue sharing, multi-party payments", "white-label payments, or embedded payments". These are exactly the phrases a user building such a business would say.

Distinctiveness Conflict Risk

Stripe Connect is a clear niche with distinct triggers ("connected account Dashboard or responsibility configurations", "charge patterns"), but broad triggers like "subscription platform", "builds SaaS that routes money between parties", and "asks about onboarding or KYC for merchants" create minor overlap risk with general Stripe-integration or onboarding skills — mostly distinct, matching anchor 4.