Provision SaaS services + sync creds via Stripe Projects.
59
70%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./optional-skills/payments/stripe-projects/SKILL.mdSecurity
2 findings: 1 high severity, 1 medium severity. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill runs the Stripe Projects CLI which generates and syncs plaintext credentials into .env and expects the CLI to surface those `.env` keys (e.g., via `stripe projects list`), so the agent will likely receive and may need to emit secret values verbatim — an exfiltration risk.
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
The skill explicitly wraps the Stripe Projects CLI and requires a Stripe account, can provision services in the user's account, and includes commands that change billing (e.g., `stripe projects add` and `stripe projects upgrade`) with an explicit note that tier prompts are real charges on Stripe. Because it exposes concrete Stripe payment/billing operations (not just generic HTTP or browser automation), it grants direct financial execution authority.
d92bfa0
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.