Skip to content
TrustedSkillsbeta
Back to all skills

Stripe Best Practices

Official
stripe·vlatest·backend·MIT

Official stripe skill covering Stripe, best practices for agent workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add stripe/ai --skill stripe-best-practices -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

stripe

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No pipe-to-shell installers: failed

    Runs code fetched at install time in 3 places.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

    What it found

    • providers/codex/plugin/skills/stripe-best-practices/SKILL.md:35tells the user to run: npm install straight from a URL(in the instructions, not code)
      If you don’t have a Stripe account, you can use the CLI to generate a sandbox test account with no registration required. Install the Stripe CLI (`npm i -g @st…
    • providers/grok/plugin/skills/stripe-best-practices/SKILL.md:35tells the user to run: npm install straight from a URL(in the instructions, not code)
      If you don’t have a Stripe account, you can use the CLI to generate a sandbox test account with no registration required. Install the Stripe CLI (`npm i -g @st…
    • skills/stripe-best-practices/SKILL.md:35tells the user to run: npm install straight from a URL(in the instructions, not code)
      If you don’t have a Stripe account, you can use the CLI to generate a sandbox test account with no registration required. Install the Stripe CLI (`npm i -g @st…

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • Pinned to a commit: passed

    Scanned stripe/ai at 79ccee2edc.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
79ccee2edc
Manifest
skills/stripe-best-practices/SKILL.md
Scanned
21 files, 2,196 lines
Copies in repo
3 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Stripe Best Practices skill provides guidance on implementing secure, efficient, and compliant payment processing workflows using Stripe's API. It includes recommendations on handling sensitive data, managing subscriptions, and ensuring compliance with financial regulations.

When to use it

  • When integrating Stripe into a new application for the first time
  • When optimizing existing payment flows for performance or security
  • When preparing for PCI DSS compliance audits
  • When setting up recurring billing systems

Key capabilities

  • Secure handling of payment data and tokens
  • Best practices for subscription management
  • Compliance with financial regulations (e.g., PCI DSS)
  • Optimization of API calls for performance
  • Handling webhooks securely and efficiently

Example prompts

  • "How should I handle customer payment information securely using Stripe?"
  • "What are the best practices for setting up recurring payments with Stripe?"
  • "Can you guide me through optimizing my Stripe integration for compliance?"

Tips & gotchas

  • Always use Stripe's recommended libraries and follow their security guidelines to avoid vulnerabilities.
  • Ensure that webhooks are properly configured and validated to prevent fraud or data breaches.