TypingMindTypingMindThe best frontend for AI
Skill Stripe Integration logo

Skill Stripe Integration

Organization
IAPro-Community
skill-stripe-integration

Integrate Stripe Checkout, Billing, subscriptions, Customer Portal, invoices, trials, coupons, webhook handling, entitlement sync, and SaaS payment state management.

Overview

PublisherIAPro-Community
RepositoryOrquestrador-Maestro
Skill nameskill-stripe-integration
Stars
63
Forks
11
Bundled files
Instructions only
LicenseApache-2.0
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by IAPro-Community on GitHub. Read the source before you install it.

Installation

Install the Skill Stripe Integration AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/IAPro-Community/Orquestrador-Maestro/tree/v1/codex/skills/skill-stripe-integration
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/IAPro-Community/Orquestrador-Maestro.git /tmp/Orquestrador-Maestro
mkdir -p .claude/skills
cp -r /tmp/Orquestrador-Maestro/codex/skills/skill-stripe-integration .claude/skills/skill-stripe-integration
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Skill Stripe Integration in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Skill Stripe Integration on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Skill Stripe Integration is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

skill-stripe-integration

Workflow

  1. Inspect existing backend boundaries, env naming, Stripe SDK usage, price/product mapping, subscription tables, and entitlement tables.
  2. Keep Stripe secret keys and webhook secrets in server-only code. Browser code may only receive publishable keys and backend-created session/portal URLs.
  3. Create Checkout or Portal sessions on the backend with authenticated actor context and stable metadata.
  4. Verify webhook signatures with the raw request body before parsing business data.
  5. Deduplicate events by Stripe event ID and store relevant Stripe IDs for support: customer, checkout session, subscription, invoice, payment intent, price, and product.
  6. Sync product access from backend subscription/payment state and local entitlement policy, not from the success redirect alone.
  7. Validate with Stripe test mode, CLI/webhook events, and the project build/typecheck.

Guardrails

  1. Use official Stripe libraries for webhook signature verification.
  2. Configure the framework route so the webhook endpoint receives the raw body.
  3. Listen only to required event types.
  4. Return a 2xx quickly; move heavy processing to a queue/job when possible.
  5. Re-fetch critical Stripe objects when event ordering or stale local state matters.
  6. Keep plan and entitlement rules in local product tables; Stripe prices/products are billing evidence, not the whole access model.
  7. Never log secret keys, webhook secrets, complete card/payment details, or unnecessary PII.

API Versioning

  • Pin the Stripe API version in the server SDK/client or endpoint configuration instead of relying silently on the account default.
  • The current Stripe API version at verification time is 2026-02-25.clover; treat this as a maintenance reference, not a reason to upgrade production automatically.
  • Review the Stripe changelog and run a test-mode webhook migration before adopting a new breaking release. Monthly releases within a major release are designed to be backward-compatible, but twice-yearly major releases can require code changes.

Typical SaaS Events

  • checkout.session.completed: first checkout completion and customer/subscription linking.
  • invoice.paid: renewal succeeded; extend access.
  • invoice.payment_failed: mark past due or start grace policy.
  • customer.subscription.updated: sync status, period, cancellation flags, price changes.
  • customer.subscription.deleted: revoke or expire access according to policy.

Data Contract

  • Map internal plans to Stripe price IDs per environment.
  • Store Stripe IDs on server records, not as frontend-only state.
  • Track subscription status, current period, cancellation flags, trial dates, grace policy, and last sync timestamp.
  • Add audit logs for plan changes, portal cancellations, payment failures, refunds, and admin overrides.

Verification

  • Use Stripe test mode and CLI/webhook test events.
  • Confirm webhook route is HTTPS in production.
  • Confirm live mode uses live price IDs, live keys, and live webhook endpoint secret.
  • Check dashboard event deliveries before assuming frontend checkout failed.
  • Verify duplicate events do not duplicate payments, extend access twice, or create duplicate audit rows.
  • Verify the webhook endpoint's configured API version matches the SDK's event types and deserialization expectations.

Official References

Frequently asked questions

What does the Skill Stripe Integration AI skill do?

Integrate Stripe Checkout, Billing, subscriptions, Customer Portal, invoices, trials, coupons, webhook handling, entitlement sync, and SaaS payment state management.

Why use Skill Stripe Integration on TypingMind?

Because you install it once and use it with any model. Skill Stripe Integration is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Skill Stripe Integration in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/IAPro-Community/Orquestrador-Maestro/tree/v1/codex/skills/skill-stripe-integration. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Skill Stripe Integration?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Skill Stripe Integration?

As many as you like. As long as a model supports skills, you can use Skill Stripe Integration with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Skill Stripe Integration AI skill free?

Yes. It is published on GitHub by IAPro-Community under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
NousResearch logo

Evm

NousResearch
OrganizationPopular

Read-only EVM client: wallets, tokens, gas across 8 chains.

53.5K
250.4K
1 files
View
NousResearch logo

Excel Author

NousResearch
OrganizationPopular

Build auditable financial workbooks headless via openpyxl.

53.5K
250.4K
1 files
View
NousResearch logo

Merger Model

NousResearch
OrganizationPopular

Build M&A accretion/dilution workbooks in Excel.

53.5K
250.4K
Instructions
View
NousResearch logo

Polymarket

NousResearch
OrganizationPopular

Query Polymarket: markets, prices, orderbooks, history.

53.5K
250.4K
2 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇