Connect Recommend
Use this skill when the user asks about Stripe Connect configuration, charge patterns...
Install
npx skills add stripe/ai --skill connect-recommend -g -a claude-code -y- Repository
- stripe/ai2k
- Category
- Business
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue sharing, multi-party payments, or similar payment distribution concepts, provides a company URL or business description for a recommendation, builds SaaS that routes money between parties (for example, POS, booking, invoicing, not operational SaaS without payment routing), asks about onboarding or KYC for merchants, sellers, and vendors, mentions connected account Dashboard or responsibility configurations, or asks about payment flows, white-label payments, or embedded payments.
Connect recommend
Recommend the right Stripe Connect integration configuration. The user only needs to provide a company URL or describe their business, the skill figures out the rest.
Interaction model
User must confirm interactions. Every decision point in this skill MUST be confirmed with the user with clear, numbered options and short descriptions. One question at a time, never overwhelm the user.
Auto-act on low-cost actions. Never ask permission for:
- Generating the markdown recommendation plan, just generate it
- Scanning the codebase, just scan it
- Reading reference files, just read them
Never end with passive text. Every stopping point must end with a prompt to the user offering concrete next actions.
Terminology rules (user-facing output)
Before generating any user-facing output, read <references/terminology-rules.md>. Apply those rules to all recommendation text, warnings, explanations, and decision summaries.
Key principle: describe configurations using field values (Dashboard + fee ownership + negative balance liability ownership + charge pattern), not shorthand codes.
Output Brevity
Keep responses concise. The user is making decisions, not reading documentation.
- Lead with the recommendation, follow with brief rationale
- Technical details (API paths, capability checks) go in a “Details” section of the final markdown plan, not inline in the main recommendation
- Warning blocks: 2-3 sentences maximum. State the issue and the fix. No mechanism deep-dives unless the user asks.
- Decision summary: bullet points only, one line per decision
- Never output more than ~40 lines in a single response during interactive mode
