CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stripe-projects

Provision SaaS services + sync creds via Stripe Projects.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

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

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 lean, executable runbook: concrete commands at every step, a sensible procedure with verification, and a pitfalls section that captures real operational hazards (plaintext .env, orphaned resources, real charges). Its weaknesses are minor — a checkpoint gap after manage operations and a small amount of posture commentary that could be cut.

DimensionReasoningScore

Conciseness

Commands are terse and the Pitfalls section is dense with non-obvious, earned information ("two separate resources — and two bills", "never commit it"). Minor over-explanation could be trimmed — notably the platform-gating posture paragraph ("this gate is a posture for the cluster, not a hard limit") — keeping it at anchor 4 rather than 5.

4 / 5

Actionability

Every step gives copy-paste-ready commands ("brew install stripe/stripe-cli/stripe", "stripe projects add neon/postgres", "stripe projects --version && stripe projects list") and concrete examples cover the common cases (add examples for neon, twilio, runloop; catalog grep fallback). Not anchor 4 because there is no meaningful gap — the Linux install pointer to the docs URL is unavoidable, not missing guidance.

5 / 5

Workflow Clarity

A clear five-step sequence (init → catalog → add → verify → manage) with an explicit verification step ("Should show the newly added provider and its .env keys") and error-recovery guidance (grep the catalog "instead of failing the add call"). It falls short of anchor 5 because upgrade/rotate/remove lack their own checkpoints — validation is add-centric, with only a generic health check covering the rest.

4 / 5

Progressive Disclosure

Sections are well-organized and everything is appropriately inline for a thin CLI wrapper — the provider catalog is discovered at runtime rather than dumped, and no content clearly belongs in a separate file. The under-50-lines exception for scoring 5 does not apply to this ~105-line body, so it sits at anchor 4.

4 / 5

Total

17

/

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 terse and names a distinct tool niche, but it reads as a minimal capability label rather than a discovery description. It answers "what" adequately while omitting any "when to use" guidance and most natural trigger phrasing, leaving real dispatch coverage to the skill body.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to set up or provision a provider (Neon, Twilio, Vercel, Postgres, Redis), sync service credentials into .env, or manage/rotate provisioned services."

Include the natural terms users actually say — provider names (Neon, Twilio, Vercel), "set up", "create a database", "rotate this key", "API keys", ".env" — so the description triggers without the user naming Stripe.

Mention the management lifecycle (upgrade, remove, rotate, billing via Stripe) so the description's capability coverage matches what the body actually does.

DimensionReasoningScore

Specificity

"Provision SaaS services" and "sync creds" name the domain with two concrete actions, but coverage is not comprehensive — managing, upgrading, rotating, and billing coordination are absent. This matches anchor 3 (domain plus 1-2 concrete actions), not anchor 4, which requires several specific actions.

3 / 5

Completeness

The "what" is clear (provision SaaS services, sync credentials), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the "when" is entirely missing rather than merely imprecise.

3 / 5

Trigger Term Quality

"Stripe Projects" is a strong exact-name trigger and "provision" is natural, but the common phrases a user would actually say ("set up Neon", "create a database", "rotate this key", "add Twilio", "environment variables") are all missing. Keywords are relevant but variations and synonyms are absent, matching anchor 3 rather than anchor 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

"via Stripe Projects" carves a clear niche tied to a specific tool, making wrong-skill triggering unlikely. It is not a 5 because "Provision SaaS services" alone is broad and the metadata lists a closely related skill (stripe-link-cli) with minor overlap risk.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.