connect-recommend

Recommends Stripe Connect account configurations and charge patterns from business research.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/divinaarmuela/Content --skill connect-recommend-divinaarmuela
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connect-recommend
Source: https://github.com/divinaarmuela/Content/tree/main/.claude/skills/connect-recommend
Command: npx skills add https://github.com/divinaarmuela/Content --skill connect-recommend-divinaarmuela

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing the right Stripe Connect integration requires navigating account configuration dimensions, charge patterns, fee economics, and compatibility constraints. This Skill guides users through a structured discovery process and produces a validated recommendation plan. ## Core Features & Use Cases - Business Research: Analyzes a company URL or description to infer business model, parties, payment flow, and fee structure with confidence levels. - Configuration Recommendation: Maps findings to Accounts v2 settings (dashboard access, fees_collector, losses_collector) and a charge pattern (direct, destination, or separate charges and transfers). - Compatibility Validation: Cross-checks every recommendation against a compatibility matrix, blocking invalid combinations and warning about tradeoffs. - Use Case: A founder building a marketplace provides their company URL; the Skill researches the business, scans the codebase, asks targeted questions, and outputs a markdown plan with the recommended Connect configuration, fee calculation approach, and embedded components. ## Quick Start Ask the assistant to recommend a Stripe Connect configuration for your marketplace or platform by providing your company URL or a short business description.

Frequently Asked Questions about connect-recommend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right Stripe Connect charge pattern?

Choose based on who owns the customer relationship and how many sellers are paid per transaction. Destination charges fit marketplaces where the platform owns checkout, direct charges fit SaaS where sellers own their payment relationships, and separate charges and transfers handle multi-seller splits or hold-and-release payouts.

What Stripe Connect account configuration should a marketplace use?

Marketplaces typically use dashboard set to express with fees_collector and losses_collector both set to application, paired with destination charges and embedded onboarding. This aligns liability with dispute flows and satisfies Express dashboard requirements.

Can I use destination charges with Stripe-owned loss liability?

No, destination charges with losses_collector set to stripe are blocked because disputes debit the platform balance while funds sit with connected accounts. Use losses_collector set to application so transfer reversals can recover funds from connected accounts.

Does application_fee_amount work with separate charges and transfers?

No, application_fee_amount is not compatible with separate charges and transfers. Platforms collect fees through transfer math instead, transferring less than the charge amount and retaining the difference minus Stripe processing fees.

When should a business not use Stripe Connect?

Businesses that sell directly to customers without routing money between multiple parties do not need Connect. A standard Stripe integration is more appropriate, and the research step flags these cases as not-connect.