CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

Highly actionable and workflow-clear instruction skill with executable curl examples and explicit validation feedback loops. Its main weakness is progressive disclosure: it is a monolithic file with dense inlined reference material and no bundle files to offload it.

Suggestions

Move the row-definition regex families (account/entity/person) and the detailed table-construction rules into a references/ file (e.g. TABLE_RENDERING.md) and link to it from a concise 'Construct the result' overview, so SKILL.md stays a navigable overview.

Consolidate the 'Naive user' and 'Smart user' curl walkthroughs into a single example set, or move the longer walkthrough into a references/ file, to reduce overlap with the Agent flow section and improve conciseness.

Add a short 'Quick start' section near the top that summarizes the minimal fetch-then-query flow, deferring the capability-resolution and supplemental-endpoint details to later sections or reference files.

DimensionReasoningScore

Conciseness

Nearly every token is operational spec (hard rules, dependency chain, row-definition regexes) rather than concepts Claude already knows; the only slack is that the 'curl examples' section re-walks parts of the Agent flow, which could be trimmed. It is efficient but not perfectly lean, so it sits above the midpoint rather than at the top anchor.

4 / 5

Actionability

Fully executable guidance: exact endpoint URLs, copy-paste curl commands with precise query-string parameter names, an explicit 12-step agent flow, and concrete table-construction and JSON-summary algorithms.

5 / 5

Workflow Clarity

A clear 12-step sequenced flow, a mermaid dependency-chain diagram, and explicit validation checkpoints with feedback loops (validation_errors → ask user to correct via the Interaction contract; build_errors → retry; empty capability list → ask user to revise).

5 / 5

Progressive Disclosure

The skill is a single ~410-line file with no bundle files or external references, and dense reference material (row-definition regex families, long curl walkthroughs, table-construction rules) is inlined that would navigate better in separate reference files. Section headers and anchor links give some structure, but content that should be split is inline.

3 / 5

Total

17

/

20

Passed

Description

100%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 model description: third-person voice, explicit 'Use when' trigger clause, concrete actions, and rich synonym coverage all present. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

The description names the domain (Stripe Connect connected accounts) and lists multiple concrete actions: identifying required verification info, comparing requirements between setups, and pinpointing required fields/documents/business details per configuration.

5 / 5

Completeness

It explicitly states both what the skill does ('what information a Stripe Connect connected account must provide') and when to use it ('Use this skill when the user asks...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms (verification, onboarding, KYC, account requirements) and concrete discriminator terms (platform country, account country, business type, dashboard, service agreement, capability).

5 / 5

Distinctiveness Conflict Risk

The niche is sharply defined (Stripe Connect connected-account verification requirements) with distinct, domain-specific triggers that would not fire for unrelated skills.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
stripe/ai
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.