Name: stripe-treasury
Rating: 52.8 (1 reviews)
Author: membranedev

stripe-treasury

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

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/stripe-treasury/SKILL.md

Quality

Content

61%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 actionable and well-structured with executable CLI commands and a clear connection workflow, but it carries some conceptual padding and lacks validation checkpoints before destructive financial operations. Adding pre-execution validation and trimming the intro would raise the workflow and conciseness scores.

Suggestions

Add an explicit validation step before running destructive or financial actions (e.g. confirm the FinancialAccount, expected amount, and direction before OutboundPayment/OutboundTransfer, and dry-run or confirm before proxy POST/PUT/DELETE).

Trim the conceptual opening paragraph and phrases like "so you can focus on the integration logic rather than auth plumbing" to assume Claude's competence.

Flesh out the Popular actions section with one or two concrete Stripe Treasury action examples (real action ids and sample --input JSON) so the run/proxy guidance is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the conceptual intro paragraph ("Stripe Treasury is a banking-as-a-service product...") and padded lines like "so you can focus on the integration logic rather than auth plumbing" are unnecessary explanation that could be trimmed.	3 / 5
Actionability	It provides concrete, executable Membrane CLI commands for the common cases (login, connection ensure, action list/run, proxy with a flag table), with only minor gaps such as template placeholders (CONNECTION_ID, QUERY, /path/to/endpoint) and a thin Popular actions section.	4 / 5
Workflow Clarity	The install→authenticate→connect→poll→search→run sequence is clear with explicit connection-state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but destructive financial operations (OutboundPayment, proxy POST/DELETE) have no pre-execution validation, so the destructive-operation cap applies.	3 / 5
Progressive Disclosure	No bundle files exist and the skill is self-contained with well-organized section headers (Overview, Working with, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) giving clear navigation; it scores 4 rather than 5 because it exceeds 50 lines and has no external references to score the one-level-deep anchor.	4 / 5
	Total	14 / 20 Passed

Description

57%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 answers both what and when with a clear, third-person trigger tied to a specific product, but its capability phrasing is generic rather than concrete Treasury actions. Tightening the action list and adding natural synonyms would lift specificity and trigger quality.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with concrete Treasury actions such as hold funds, pay bills, manage cash flow, and manage financial accounts.

Add natural trigger synonyms users actually say, e.g. "banking-as-a-service", "funds", "bills", or "cash flow", not only "Stripe Treasury data".

Make the 'when' clause more specific by naming the triggering intent (e.g. "Use when the user wants to embed banking features or manage funds within Stripe Treasury").

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain but the actions are generic (manage/automate) rather than concrete Treasury actions like hold funds, pay bills, or manage cash flow, matching the minimal/generic anchor and falling below the concrete-actions anchor.	2 / 5
Completeness	Both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Stripe Treasury data") are present and explicit, but the what is somewhat generic rather than concrete, fitting the both-present-but-could-be-more-specific anchor.	4 / 5
Trigger Term Quality	The only genuine natural trigger term is "Stripe Treasury" (plus "Stripe Treasury data"); common user variations such as banking, funds, bills, or cash flow are absent, so it has some relevant keywords but is missing variations.	3 / 5
Distinctiveness Conflict Risk	"Stripe Treasury integration" names a specific product with a distinct trigger and minimal conflict risk, but the generic action phrasing (manage data, automate workflows) leaves minor overlap risk with other Stripe or data-management skills.	4 / 5
	Total	13 / 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-treasury/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.