Name: stripe-financial-connections
Rating: 60 (1 reviews)
Author: membranedev

stripe-financial-connections

Stripe Financial Connections integration. Manage data, records, and automate workflows. Use when the user wants to interact with Stripe Financial Connections data.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/stripe-financial-connections/SKILL.md

Quality

Content

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

The content is highly actionable with copy-paste CLI commands and a sensible workflow including state polling, and it is concise for the most part. Its weaknesses are minor verbosity in the intro and the absence of progressive disclosure — all reference material is inlined with no bundle files or external references.

Suggestions

Trim the introductory paragraph that explains what businesses use Financial Connections for, since Claude already knows the domain.

Consider moving the proxy options table and action schema details into a separate reference file to improve progressive disclosure.

Tighten the connection-readiness section with consistent step numbering so the install-to-action sequence is fully explicit.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with command-first sections and minimal concept explanation, though the introductory paragraph and a few explanatory sentences (e.g. 'This allows businesses using Stripe to...') add light padding Claude doesn't need.	4 / 5
Actionability	Nearly every step gives copy-paste-ready membrane CLI commands with flags and example inputs, plus a clear options table for the proxy; guidance is concrete and executable across install, auth, connection, search, and action-run flows.	5 / 5
Workflow Clarity	There is a clear sequence (install -> login -> connection ensure -> wait/poll -> search actions -> run/proxy) with explicit state handling and polling feedback, but the connection-readiness flow has only one 'Step 2' reference and no fully labeled multi-step numbering, leaving minor sequencing gaps.	4 / 5
Progressive Disclosure	No bundle files exist and all content lives inline in SKILL.md with reasonable section headers, but the skill has no external references to split off the bulkier reference material (proxy options table, action schemas) despite that content being sizable.	3 / 5
	Total	16 / 20 Passed

Description

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

The description correctly follows the 'what + Use when' pattern with a clear explicit trigger, and its niche is specific. Its main weakness is generic action language ('manage data, records, and automate workflows') and thin trigger-term coverage that could name concrete capabilities and synonyms.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions such as listing accounts, retrieving transactions, and creating sessions.

Broaden trigger terms with natural synonyms a user would say, e.g. 'bank accounts, financial data, account ownership, or linking a bank'.

Keep the explicit 'Use when' clause but make the trigger condition more specific than 'interact with ... data'.

Dimension	Reasoning	Score
Specificity	Names the domain (Stripe Financial Connections) but the only actions are the generic 'Manage data, records, and automate workflows' — no concrete operations like listing accounts, creating sessions, or retrieving transactions are named.	3 / 5
Completeness	It has a clear 'what' (Stripe Financial Connections integration managing data/records/workflows) and an explicit 'when' clause ('Use when the user wants to interact with Stripe Financial Connections data'), though the 'when' is fairly generic.	4 / 5
Trigger Term Quality	It repeats 'Stripe Financial Connections' and 'data' but offers no natural synonyms or variations a user would say (e.g. bank accounts, linking banks, financial data, account ownership); keyword coverage is shallow.	3 / 5
Distinctiveness Conflict Risk	The Stripe Financial Connections niche is specific and clearly distinguishable from sibling Stripe skills, though the generic 'data, records, and automate workflows' phrasing could create minor overlap with other integration skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/stripe-financial-connections/SKILL.md
Commit: f484c82

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.