stripe-projects

Provision SaaS services + sync creds via Stripe Projects.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/payments/stripe-projects/SKILL.md

Quality

Content

88%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 tight, fully executable runbook: concrete commands with examples, an explicit verify step in the workflow, and unusually good operational pitfalls (credential-leak vectors, billing reality, orphaned resources). The only gaps are minor: a trimmable posture paragraph and no use of progressive disclosure despite a moderately long body.

Dimension	Reasoning	Score
Conciseness	The body is lean: every section adds tool-specific facts Claude would not know (vault path, .env behavior, catalog command), with no padding about what Stripe or SaaS is. Not 5 because the 'Gated [linux, macos]...' paragraph is meta-commentary about skill posture that earns little operational value and could be trimmed.	4 / 5
Actionability	Every step is a copy-paste-ready command (stripe projects init/catalog/add neon/postgres/list), with concrete service examples, exact file paths (.projects/vault/vault.json, .env), and install commands for both platforms. Specific examples cover the common cases fully.	5 / 5
Workflow Clarity	The procedure is a clearly sequenced init → catalog → add → verify workflow with an explicit validation step (step 4 'Verify' via stripe projects list) and a separate health-check Verification section. Error-recovery guidance is present in Pitfalls (grep the catalog before failing an add, check .gitignore before writes, check provider dashboard after remove), satisfying the feedback-loop requirement for the destructive remove/upgrade operations, so the cap does not apply.	5 / 5
Progressive Disclosure	Sections are well-organized and appropriately sized with no buried references and no content that clearly belongs in a separate file. Not 5 because the skill ships no bundle files at all and keeps everything inline (install instructions, pitfalls, procedure) in a ~107-line body; at that size a references/ split for install/pitfalls detail would reach the 'clear overview with one-level-deep references' anchor.	4 / 5
	Total	18 / 20 Passed

Description

53%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 concise and names a specific tool and two real capabilities, but it entirely lacks a 'Use when' trigger clause and omits natural user phrasings and provider keywords. It is a terse capability label rather than a complete, trigger-rich description.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user says set up Neon/Twilio/Vercel, create a database, rotate a key, or manage stack credentials.'

Include natural user vocabulary and provider names (e.g. 'set up', 'provision', 'Neon', 'Twilio', 'Vercel', '.env', 'API keys') so the description matches how users actually phrase these requests.

Briefly enumerate the fuller capability set (add, rotate, upgrade, remove services; sync credentials into .env) to raise specificity beyond two actions.

Dimension	Reasoning	Score
Specificity	The description names the domain ("SaaS services") and two concrete actions ("Provision", "sync creds") via a specific tool ("Stripe Projects"), matching the 'names domain and 1-2 concrete actions' anchor. It is not the 4-5 level because the skill's other demonstrated capabilities (manage/rotate/upgrade services, billing, .env writes) are absent, and '+'/'creds' shorthand slightly under-specifies.	3 / 5
Completeness	The 'what' is stated (provision services, sync credentials), but there is no 'Use when...' clause or any equivalent trigger guidance, capping completeness at 3 per the rubric guideline. Not 2 because the 'what' is concrete, not vague.	3 / 5
Trigger Term Quality	"Provision" and "SaaS services" are relevant keywords, but natural user phrasings like "set up", "create a database", "API key", or concrete provider names (Neon, Twilio, Vercel) are missing. Some relevant keywords without common variations places this at 3, not 4, since users would rarely say "sync creds" unprompted.	3 / 5
Distinctiveness Conflict Risk	"via Stripe Projects" carves out a clear niche tied to a specific CLI, so it is mostly distinct with only minor overlap risk against generic provisioning/cloud-CLI skills. Not 5 because 'SaaS services' and 'creds' are broad enough that other infrastructure-provisioning skills could contend for the same triggers.	4 / 5
	Total	13 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: optional-skills/payments/stripe-projects/SKILL.md
Commit: 68fa7e9

Reviewed: 3 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.