Name: stripe-corporate-card
Rating: 60.8 (1 reviews)
Author: membranedev

stripe-corporate-card

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/stripe-corporate-card/SKILL.md

Quality

Content

82%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 body is a strong, action-oriented integration guide with executable commands, a clear connection-state workflow, and clean sectioning. Its main weaknesses are minor conciseness padding and a broken step-numbering reference ('Step 2') with no validation checkpoint for destructive proxy requests.

Suggestions

Fix the dangling step references: the body mentions 'Step 2' and '1b' but never labels a 'Step 1' or 'Step 2', so relabel the connecting section as a numbered sequence.

Add a validation/verification note before destructive proxy requests (POST/PUT/DELETE), e.g., confirm the endpoint and review the response status before mutating data.

Trim editorial padding such as 'so you can focus on the integration logic rather than auth plumbing' to keep the guide lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with executable commands and a compact options table, but includes a few editorial phrases ('so you can focus on the integration logic rather than auth plumbing') and product-context padding that could be trimmed, matching the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	It provides fully executable, copy-paste ready commands with clearly marked placeholders (<id>, CONNECTION_ID) covering auth, connection setup, action search/run, and proxy requests, plus a flags table, matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The connect workflow has a clear sequence with state-based checkpoints and polling feedback (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but it references an undefined 'Step 2' and '1b' without labelled steps, and lacks validation for potentially destructive proxy calls, matching the 'clear sequence with most checkpoints; minor validation gaps' anchor.	4 / 5
Progressive Disclosure	With no bundle files present, the content is organized into clear, well-signaled sections (Overview, Authentication, Connecting, Searching, Actions, Proxy, Best practices); the only gap is the thin 'Popular actions' section that mostly redirects to the list command, matching the 'good structure; minor organization gaps' anchor.	4 / 5
	Total	17 / 20 Passed

Description

61%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 names a distinct product and includes an explicit 'Use when' trigger, but its stated capabilities are generic ('manage data, records, automate workflows') and it omits natural synonyms a user might say. Stronger distinctiveness than specificity.

Suggestions

Replace generic verbs with concrete Stripe Corporate Card capabilities (e.g., 'list transactions, issue cards, manage authorizations, review expense records').

Add natural trigger synonyms users actually say, such as 'expense card', 'corporate spending', 'card authorizations', or 'transactions'.

Tighten the 'when' clause with concrete triggers, e.g., 'Use when the user wants to query transactions, manage card authorizations, or reconcile employee expenses.'

Dimension	Reasoning	Score
Specificity	Names the domain ('Stripe Corporate Card integration') and a few actions, but the actions are generic boilerplate ('Manage data, records, and automate workflows') rather than concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states a 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when...' trigger, but the 'when' is generic ('interact with Stripe Corporate Card data') and could be more specific, matching the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	The product name 'Stripe Corporate Card' is a strong specific keyword, but it lacks common variations or synonyms a user might say ('expense card', 'transactions', 'authorizations', 'spending'), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Stripe Corporate Card' creates a clear niche with distinct triggers and minimal conflict risk with other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 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-corporate-card/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.