Payments & Billing · head-to-head
connect-recommend vs paddle-agent-skills
Pick the Stripe connect-recommend skill when you are building a marketplace or platform and need to choose a charge pattern and account type — it ships a compatibility matrix that rejects invalid configurations before you build them. Pick paddle-agent-skills when you would rather not own global tax registration at all: Paddle acts as merchant of record and handles VAT and sales tax as part of the deal. This is a business-model decision that payments code then follows, not the other way round.
Pick connect-recommend
You are routing money between parties — sellers, vendors, providers — and need control over onboarding, KYC, payout timing, and platform fees.
Pick paddle-agent-skills
You sell software internationally and want tax registration, VAT handling, and invoicing to be someone else's legal obligation.
Side by side
How they differ
| connect-recommend | paddle-agent-skills | |
|---|---|---|
| Model | You are the platform; Stripe processes | Paddle is the merchant of record |
| Who owns tax compliance | You | Paddle |
| Multi-party payouts | Core strength — Connect charge patterns | Not its purpose |
| What the skill does | Recommends a configuration, with a matrix that blocks invalid ones | Implementation guidance for Paddle billing |
| Credentials needed | None — it produces a plan | Paddle account for implementation |
| Best moment to use it | Before you build, while the architecture is still open | When the business model is settled and you are integrating |
Model
- connect-recommend
- You are the platform; Stripe processes
- paddle-agent-skills
- Paddle is the merchant of record
Who owns tax compliance
- connect-recommend
- You
- paddle-agent-skills
- Paddle
Multi-party payouts
- connect-recommend
- Core strength — Connect charge patterns
- paddle-agent-skills
- Not its purpose
What the skill does
- connect-recommend
- Recommends a configuration, with a matrix that blocks invalid ones
- paddle-agent-skills
- Implementation guidance for Paddle billing
Credentials needed
- connect-recommend
- None — it produces a plan
- paddle-agent-skills
- Paddle account for implementation
Best moment to use it
- connect-recommend
- Before you build, while the architecture is still open
- paddle-agent-skills
- When the business model is settled and you are integrating
Open connect-recommend or paddle-agent-skills for the composite score, license, and exact install commands, or browse the full Payments & Billing category.
Verdict
The bottom line
These answer different questions and the order matters. Decide the business model first: if you are moving money between other people, that is Connect, and the connect-recommend skill is unusually valuable because it front-loads the decisions that are painful to reverse once money is flowing. If you are selling your own software globally and tax registration is the thing you do not want to own, Paddle is the answer and the skill is about implementing it well. Choosing the payments code before the model is the mistake both skills exist to prevent.
FAQ
Common questions
Stripe Connect or Paddle for a marketplace?
Stripe Connect. Paddle is a merchant of record for selling your own product, not a platform for routing money to third-party sellers. The connect-recommend skill will map your case to a charge pattern and account type and reject combinations that cannot work.
What does the connect-recommend skill actually produce?
A written recommendation: charge pattern, account type, dashboard access and responsibility configuration, backed by a compatibility matrix that blocks invalid combinations and warns when platform fees fall below Stripe processing cost. It needs no API key because it produces a plan, not an integration.
Can I use both?
Rarely, and usually as a migration rather than a design. Running both means two reconciliation surfaces and two tax positions. The realistic case is starting on a merchant of record for speed and moving to Connect when payout control becomes the constraint.
Related
More head-to-head comparisons
- firecrawl vs browser-use
firecrawl for hosted, JavaScript-rendered extraction at scale; browser-use for driving a real browser through logins, forms, and multi-step flows.
- supabase-skill vs planetscale-skills
supabase-skill for Postgres with row-level security, auth, and realtime; planetscale-skills for MySQL with Git-style schema branching at scale.
- stripe-best-practices vs paddle-agent-skills
stripe-best-practices for maximum control over payment flows (you own tax); paddle-agent-skills for merchant-of-record billing (Paddle handles global sales tax and VAT).
- docling vs pdf
docling for reading and converting documents an agent cannot open — including scanned PDFs and RAG chunking; the Anthropic pdf skill for producing and manipulating real PDFs.
- semgrep vs trail-of-bits
semgrep runs a real static-analysis engine and writes custom rules; trail-of-bits brings a security firm's review method to a diff. Findings versus judgement.
- playwright-cli vs Browserbase browser
playwright-cli for a local browser you fully control and an existing Playwright suite; Browserbase browser for hosted sessions with CAPTCHA solving and residential proxies.
- postgres vs supabase-skill
The postgres skill for engine-level decisions — types, indexes, partitioning, extensions; supabase-skill for the platform layer — row-level security, auth, realtime.
- drawio vs mermaid-diagrams
drawio produces an editable .drawio file someone can rearrange later; mermaid keeps the diagram as text inside the document it belongs to.
Browse all best-skill guides or the full directory.