Connect Recommend

You've built a marketplace or platform and need to figure out which Stripe Connect setup makes sense. This skill walks you through the decision process by researching your company URL or business description, scanning your codebase for existing patterns, then recommending a specific configuration (dashboard access, fee ownership, charge pattern). The interaction model is thoughtful: it auto-fills high-confidence decisions from research, confirms medium-confidence assumptions, and only asks questions when actually needed. It also validates fee economics so you don't accidentally configure a setup where platform fees are thinner than Stripe's processing costs. Built for the common case where you know you need Connect but the 12+ configuration permutations are overwhelming.

skills.sh installs: 3.7K
GitHub stars: 2.1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add stripe/ai --skill connect-recommend --agent claude-code

Installs into .claude/skills of the current project.

Files

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.