Name: stripe-identity
Rating: 55.2 (1 reviews)
Author: membranedev

stripe-identity

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

Quality

63%

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-identity/SKILL.md

Quality

Content

68%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 well-structured, actionable guide to driving Stripe Identity through the Membrane CLI, with strong command coverage and a clear connection state machine. Its main weakness is the proxy workflow, which permits destructive HTTP methods without any validation guidance.

Suggestions

Add a validation/verification checkpoint to the proxy section for destructive methods (POST/PUT/PATCH/DELETE) — e.g. GET-then-confirm before a DELETE, or a note to confirm the resource id with the user.

Include at least one Stripe-Identity-specific action example (e.g. creating a VerificationSession or fetching a VerificationReport) rather than only generic <actionId> placeholders.

Trim soft commentary like 'so you can focus on the integration logic rather than auth plumbing' to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, focusing on Membrane-specific steps Claude would not know (auth, connection state machine, action discovery). Minor padding remains ('focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection'). Not a 5 because a few sentences could be trimmed; not a 3 because it does not pad with general concepts Claude already knows.	4 / 5
Actionability	Provides copy-paste-ready commands across install, login, connection, action search/run, and proxy, each with concrete flags. Not a 5 because the 'Running actions' and proxy examples use generic placeholders (<actionId>, /path/to/endpoint) with no Stripe-Identity-specific example (e.g. creating a VerificationSession).	4 / 5
Workflow Clarity	The connection flow is well sequenced with a polling feedback loop and state-based error handling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR). Capped at 3 because the proxy section enables destructive operations (DELETE, PUT) with no validation or verification checkpoint, triggering the destructive-operations cap.	3 / 5
Progressive Disclosure	No bundle files exist, and the single SKILL.md is well organized into clearly labeled sections (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with content appropriately kept inline. Not a 5 because the file exceeds 50 lines and offers no one-level-deep references for the longer reference-style material (e.g. the proxy flag table).	4 / 5
	Total	15 / 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 is structurally complete — it names the domain and includes an explicit 'Use when' trigger — but the capability list ('Manage data, records, and automate workflows') is generic and lacks concrete actions and natural synonyms like KYC or verification.

Suggestions

Replace generic verbs with concrete Stripe Identity capabilities, e.g. 'Create and monitor VerificationSessions, retrieve VerificationReports, and manage identity verification workflows.'

Add natural trigger synonyms users actually say, such as 'identity verification', 'KYC', or 'VerificationSession', alongside 'Stripe Identity data'.

Tighten the 'Use when' clause to reference concrete intents (e.g. 'Use when the user needs to verify a customer's identity or retrieve a verification report').

Dimension	Reasoning	Score
Specificity	Names the domain ('Stripe Identity integration') but the actions — 'Manage data, records, and automate workflows' — are generic and non-concrete, matching the anchor 'Names the domain but actions are minimal or generic'. Not a 3 because it lists no concrete capability (e.g. create verification sessions, retrieve reports).	2 / 5
Completeness	Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Stripe Identity data'). Not a 5 because the 'what' is generic rather than concrete trigger phrases; not a 3 because the 'Use when' clause is present and explicit, so the missing-trigger cap does not apply.	4 / 5
Trigger Term Quality	Includes the natural term 'Stripe Identity' and the trigger phrase 'interact with Stripe Identity data', but misses common synonyms a user would actually say — identity verification, KYC, VerificationSession, VerificationReport. Not a 4 because several natural terms are absent.	3 / 5
Distinctiveness Conflict Risk	'Stripe Identity' carves out a clear niche with low conflict risk against unrelated skills. Not a 5 because the generic 'data, records, workflows' wording could overlap with a broader Stripe or records-management skill.	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-identity/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.