CData Connect AI — Stripe Skill

⚠️ Prerequisites — load these first

• connect-ai-base skill

Before proceeding, locate and read the connect-ai-base skill. If it is not available in the current environment (not loaded, not enabled, or not installed), stop immediately. Do not proceed with the task. Tell the user that the connect-ai-base skill is required and ask them to install and enable it before continuing.

This skill provides Stripe-specific guidance for querying Stripe data through CData Connect AI. It composes on top of the connect-ai-base skill, which handles the discovery workflow, error recovery, SQL dialect, and three-part query naming convention.

Precedence

This skill replaces getInstructions for the Stripe driver. Do not call getInstructions for Stripe — the guidance it provides is already incorporated here and in the per-surface references. Proceed directly to getSchemas (to identify the surface — see below) and then schema discovery (getTables / getColumns) after identifying the Stripe connection via getCatalogs.

Stripe exposes two API surfaces

A Stripe connection presents one of two surfaces, determined by the CData Schema connection property. A connection exposes only the surface it is configured for, so getSchemas returns a single schema. The surface cannot be inferred from the connection name, so the first move on any Stripe connection is to identify it with getSchemas.

Always run getSchemas as the FIRST tool call against any Stripe connection — before any queryData, getTables, or getColumns call. Do not infer the surface from the connection name. The schema returned by getSchemas is the only authoritative signal: Stripe → classic surface, StripeV2 → V2 surface.