Agent skill · stripe
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.
What it needs
About 10k tokens when loaded.
What this skill does
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 are dependency-free at that point in the flow. For example, ask for platformCountry and accountCountry separately: the platform country determines which account countries are valid, so asking both together can produce invalid combinations. But you may ask for dashboardType, tosType, and legalEntityType together in one group because their valid options are already known from the same response. If there is ever a conflict between the user’s request and the validated setup, inform the user of the conflict and ask them to revise their setup choices using the Interaction contract. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills stripe/connect-required-verification-information--8080a9