Connect Required Verification Information
Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required for a particular platform country, account country, business type, dashboard, service agreement, or capability.
Install
/plugin marketplace add stripe/aiThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add stripe/ai --skill connect-required-verification-informationgit clone --depth 1 https://github.com/stripe/ai.git /tmp/ai
mkdir -p ~/.claude/skills
cp -r /tmp/ai/providers/agent-plugins/plugin/skills/connect-required-verification-information ~/.claude/skills/connect-required-verification-informationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
## Instructions The human-accessible version of this documentation allows the user to select connected account fields and regions using a form, and then makes API requests to fetch and display the requirements a connected account with the selected configuration and region must provide. Follow these instructions to fetch the same information. ### Interaction contract Terminology used in this document: - `field`: a setup input such as `platformCountry`, `accountCountry`, or `capabilities` - `option`: a presented selectable option for a field - `value`: the option the user selects, or the free-response value the user provides for a field Every time you ask the user to provide a value for a field: - use a multiple-choice question; never stop at a plain free-form prompt or wait for raw chat input - if you need free user input, instruct the user to use the question’s free-response field - for long option lists, explicitly say that any value from the full validated list is still accepted through the free-response field - if the user already provided a valid answer in an earlier message, use that instead of asking again ### Hard rules You must follow these rules: - Ask for a field *only* after all of its prerequisite fields are satisfied. - Collect setup fields progressively as the flow advances. - Ask for one field at a time, or one group of fields only when they’re dependency-free at that point in the flow.
Details
- Skill name
connect-required-verification-information- Repository
- stripe/ai
- Path
providers/agent-plugins/plugin/skills/connect-required-verification-information/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Connect Required Verification Information skill do?
Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required for a particular platform country, account country, business type, dashboard, service agreement, or capability.
How do I install the Connect Required Verification Information skill?
Claude Code plugin: /plugin marketplace add stripe/ai. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Connect Required Verification Information popular?
It lives in stripe/ai, which has 2,072 GitHub stars and 385 forks, and is included in 1 curated skill list.
Related skills
Connect Recommend
2.1kstripe/ai
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
Metronome
2.1kstripe/ai
Guides Metronome usage-based billing integration decisions — event ingestion (single and batch, idempotency, billable metrics), contract design (rate cards, overrides, dimensional pricing, products), invoicing lifecycle (grace periods, finalization, Stripe sync), credit and commit management (prepaid, postpaid, thresholds, auto-recharge), and Stripe integration (arrears invoicing, tax providers, line item limits). Use when building, modifying, or reviewing any Metronome integration — including ingesting usage events, creating customers, contracts, or rate cards, designing billable metric group
Stripe Apps
2.1kstripe/ai
Build, modify, or review Stripe Apps and extensions using the relevant documentation and reference guides. Use for custom Stripe Dashboard UI, stripe-app.yaml, @stripe/ui-extension-sdk, @stripe/extensibility-sdk, script extensions, extension interfaces, custom workflow actions, and apps that authenticate to Stripe or react to events. Also use when deciding whether a Stripe extension can support the user's billing or workflow requirements.
Release
2.1kShpigford/chops
Determine the next version, update the marketing site, and run the full release pipeline.
Risky Changes
4.3kdavidondrej/skills
Verify assumptions before implementing large or risky changes to APIs, provider data, billing, pricing, quotas, or defaults. Use when a mistake could affect customers or the user asks if a change is safe to ship. Checks real-world impact beyond passing tests.
Blue Ocean Strategy
2.7kwondelai/skills
Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.