CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

connect-recommend

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.

68

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is connect-recommend in stripe/ai

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally actionable, well-validated workflow with excellent user-interaction scripting and genuine one-level-deep reference structure. The main cost is length: dense compatibility and guardrail blocks duplicate reference-file content inline, which inflates the SKILL.md well past overview weight.

Suggestions

Move the Step 4a compatibility rule enumeration (the dashboard/fees_collector/losses_collector combination checks) into references/compatibility-matrix.md and keep only the validation gate plus the BLOCKED/CAUTION output format in SKILL.md — the matrix file already exists for exactly this content.

Compress the Step 3 critical guardrails into short one-line pointers (e.g., 'hybrid flows → Step 3b in discovery-questions.md', 'account-type question → account-types.md') instead of multi-clause run-on paragraphs that restate reference-file logic.

Replace the four reprinted checklist blocks with a single 'update the checklist after each step' instruction and one canonical checklist definition, eliminating ~30 lines of repeated output.

DimensionReasoningScore

Conciseness

The body doesn't explain known concepts and enforces its own brevity rules, but it is noticeably over-long at ~340 lines with real tightening opportunities: the Step 4a compatibility rules ('If dashboard: "express" + fees_collector: "stripe"...' and the near-identical following bullet) repeat public-preview disclosure text verbatim and duplicate material that belongs in compatibility-matrix.md, the Step 3 guardrails are multi-clause run-on paragraphs duplicating discovery-questions.md content, and the four-line progress checklist is reprinted four times. It is above anchor 2 because nothing is concept padding — it is all operational instruction — but below anchor 4 because whole blocks (Step 3 guardrails, Step 4a checks 3) restate reference-file content inline.

3 / 5

Actionability

Fully executable for an instruction-only skill: exact question scripts ('Tell me about your business. Pick whichever is easiest:'), exact option sets with mapped outcomes, copy-paste warning text with links, concrete grep patterns ('connected_account', 'transfer_data', 'separate_charges'), and precise pre-fill rules keyed to HIGH/MEDIUM/LOW confidence. Every step tells the agent exactly what to do, read, and output.

5 / 5

Workflow Clarity

Steps 0-6 are clearly sequenced with a visible progress checklist, and validation is explicit throughout: Step 1f fee-economics validation 'ALWAYS runs, even on auto-filled values', the MANDATORY Step 4a compatibility validation before any recommendation is presented, the merchant-of-record consistency check, and the fee-structure checkpoint. Feedback loops are present — BLOCKED configs trigger 're-run the recommendation with the corrected configuration' and user corrections re-enter the relevant question.

5 / 5

Progressive Disclosure

Eight references (terminology-rules.md, company-researcher.md, decision-matrix.md, discovery-questions.md, account-types.md, charge-patterns.md, compatibility-matrix.md, recommendation-template.md) are all real files, clearly signaled with 'Read <references/...>' directives, and none nest further references — one level deep as required. It falls short of anchor 5 because substantial reference material is inlined in the main file (the Step 3 critical guardrails and the Step 4a compatibility rules largely restate discovery-questions.md and compatibility-matrix.md), making the SKILL.md heavier than an overview warrants.

4 / 5

Total

17

/

20

Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, trigger-dense description with excellent natural-language coverage and careful boundary carving, anchored to a clearly distinct Stripe Connect niche. Its only weakness is that the core capability ('recommends the right Connect integration configuration') is implied by the trigger list rather than stated explicitly up front.

DimensionReasoningScore

Specificity

The description names the domain concretely ('Stripe Connect configuration, charge patterns, Dashboard access') and enumerates specific concrete areas like 'onboarding or KYC for merchants, sellers, and vendors' and 'split payments, revenue sharing, multi-party payments'. It falls short of anchor 5 because the capability itself — recommending a Connect configuration — is only implied via 'provides a company URL or business description for a recommendation' rather than stated as a leading action; it stays above anchor 3 because many concrete, distinct capability areas are explicitly named.

4 / 5

Completeness

The 'when' is explicit and thorough ('Use this skill when the user asks about Stripe Connect configuration... or asks about payment flows'), and a 'what' is present but only weakly explicit — the action is inferable from 'Connect configuration' and 'for a recommendation' rather than stated as a capability sentence. It exceeds anchor 3 (which requires the 'when' to be missing or weak) but does not reach anchor 5's 'clearly and explicitly answers both what AND when'.

4 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms: 'marketplace, platform, multi-vendor store, gig platform, or subscription platform', 'pay out sellers, vendors, or providers', 'white-label payments, or embedded payments', plus business-shape hints like 'POS, booking, invoicing'. These are the phrases a user would naturally say; no common variation is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche — Stripe Connect configuration recommendation — with distinct triggers ('connected account Dashboard or responsibility configurations', 'split payments') and explicit boundary exclusion ('not operational SaaS without payment routing') that minimizes overlap with a general Stripe-integration skill.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

stripe/ai

Path

providers/codex/plugin/skills/connect-recommend/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.