connect-recommend

Recommends Stripe Connect account configurations and charge patterns for marketplaces and platforms.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/FarooqProProgrammer/the-magician --skill connect-recommend-farooqproprogrammer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: connect-recommend
Source: https://github.com/FarooqProProgrammer/the-magician/tree/main/agent/skills/connect-recommend
Command: npx skills add https://github.com/FarooqProProgrammer/the-magician --skill connect-recommend-farooqproprogrammer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing the right Stripe Connect integration is complex: account configuration dimensions (dashboard access, fee collection, loss liability), charge patterns (direct, destination, separate charges and transfers), and compatibility constraints interact in ways that can silently create liability or margin problems. This Skill guides users through a structured discovery process and produces a validated recommendation plan. ## Core Features & Use Cases - Business research and auto-fill: Researches a company URL or description, maps findings to a decision matrix with confidence levels, and pre-fills discovery answers. - Codebase scanning: Detects existing Connect integration patterns and prior recommendation plans in the project to avoid redundant questions. - Compatibility validation: Cross-checks every proposed configuration against a compatibility matrix, blocking invalid combinations (for example, Stripe-owned losses with destination charges) and explaining the fix. - Fee economics checks: Warns when platform fees may fall below Stripe processing fees and recommends margin-preserving calculation approaches. - Use Case: A founder building a marketplace for freelance designers provides their company URL; the Skill researches the business, recommends Express dashboard with platform-owned fees and losses plus destination charges, and generates a markdown implementation plan. ## Quick Start Ask the assistant to recommend a Stripe Connect configuration for your marketplace or platform, optionally providing your company URL or 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 direct charges when sellers own the customer relationship (SaaS model), destination charges when the platform owns checkout (typical marketplaces), and separate charges and transfers for multi-seller carts or hold-and-release payouts. The Skill maps your business model to the correct pattern using a decision matrix.

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 uses the Accounts v2 API rather than legacy account types like standard, express, or custom.

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

No, that combination is blocked. With destination charges, disputes debit the platform balance and recovery requires transfer reversals, which only work when losses_collector is application. The Skill detects this and recommends the nearest allowed alternative.

Does Stripe Connect support application fees 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 as margin.

Why might my marketplace platform fee lose money on each transaction?▼

With destination charges the platform always pays Stripe processing fees, so a low platform fee can produce thin or negative net margin. The Skill runs a mandatory fee economics check and recommends including estimated Stripe fees in application_fee_amount or using the Platform Pricing Tool.