Stripe

WarnAudited by ClawScan on May 10, 2026.

Overview

This looks like a real Stripe/Membrane integration, but it gives an agent broad access to change sensitive Stripe account data without clear approval, scope, or rollback safeguards.

Install only if you trust Membrane and need an agent to work with Stripe. Before connecting, verify the permissions granted, prefer read-only or least-privilege access, and require explicit confirmation for any action that changes prices, products, subscriptions, payouts, transfers, refunds, or customer data.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

An agent using this skill could change subscriptions, prices, products, or other Stripe account records if invoked with sufficient permissions.

Why it was flagged

The skill gives broad instructions for running Stripe actions and lists mutation/destructive actions, but the artifact does not require user confirmation, scoping, dry-run, or rollback for high-impact Stripe changes.

Skill content
Use action names and parameters as needed... Update Subscription... Update Price... Delete Product
Recommendation

Require explicit user approval before any create, update, delete, payout, transfer, refund, or subscription-changing action; prefer read-only access unless the user specifically requests a mutation.

What this means

Connecting this skill may grant ongoing access to sensitive Stripe account data and administrative actions.

Why it was flagged

This indicates persistent delegated credential handling for Stripe through Membrane. For a payments account, the artifact does not clearly state OAuth scopes, permission limits, credential storage boundaries, or revocation steps.

Skill content
Membrane handles authentication and credentials refresh automatically
Recommendation

Use the least-privileged Stripe/Membrane connection available, review granted scopes, monitor activity, and revoke the connection when it is no longer needed.

What this means

The user must trust the Membrane CLI package and whatever version npm resolves at install time.

Why it was flagged

The skill relies on a globally installed npm CLI using the latest version. This is central to the stated purpose, but it means the executed tool version is not pinned or reviewed in the supplied artifact.

Skill content
npm install -g @membranehq/cli@latest
Recommendation

Install the CLI only from the official source, consider pinning a known-good version, and keep it updated intentionally.