Skip to content
TrustedSkillsbeta
Back to all skills

Stripe Payments

Checked
eyadsibai·vlatest·backend

Helps with Stripe, payments as part of agent workflows 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 eyadsibai/ltk --skill stripe-payments -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

eyadsibai

Taken from the source listing. We haven't verified who controls this account.

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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • 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.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

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

  • Pinned to a commit: passed

    Scanned eyadsibai/ltk at f8e85697b9.

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

Commit
f8e85697b9
Manifest
plugins/ltk-product/skills/stripe-payments/SKILL.md
Scanned
1 file, 145 lines
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

The stripe-payments skill enables AI agents to interact directly with the Stripe payment processing platform. It allows agents to create invoices, manage subscriptions, and handle customer billing details securely within a workflow.

When to use it

  • Automating recurring billing cycles for SaaS products without manual intervention.
  • Generating and sending custom invoices to clients based on specific service tiers.
  • Retrieving real-time payment status or transaction history for customer support queries.
  • Processing one-time payments for digital goods or event registrations.

Key capabilities

  • Creating and managing Stripe invoices programmatically.
  • Setting up and modifying subscription plans.
  • Accessing customer billing information securely.
  • Handling payment intents and verifying successful transactions.

Example prompts

"Create a recurring monthly invoice for client 'Acme Corp' under the Pro plan." "Check the current payment status for order #12345 and notify me if it failed." "Generate a one-time invoice for $500 for the Q3 consulting services rendered last week."

Tips & gotchas

Ensure your AI agent has valid API keys with appropriate permissions before attempting to process live transactions. Always verify customer details against stored records to prevent billing errors or security risks.