Community skillDraft — source instructions not independently live-testedCommerce & finance

Stripe for Meta Muse

Community draft proposes: Read-only Stripe visibility: balance, recent charges, customers. No write commands ship: expanding to writes is a deliberate v2.

Guide description: Read-only visibility into the user's Stripe account: current balance, recent charges, and customers. Use when the user asks about revenue, payments, or their Stripe balance.

Community-authored Draft; OpenTools has not independently installed or live-tested this skill. Use a restricted, read-only Stripe API key. This draft cannot charge, refund, or mutate customers; distinguish it from Link by Stripe inside Muse.

View original source ↗

How to set it up

Paste a prompt

Draft — these instructions come from the linked source and have not been independently live-tested by OpenTools.

Source maturity: 🧪 Draft: written from Stripe's public API docs; not yet live-tested end-to-end.

Before you start

  • Stripe restricted API key (per-user, Dashboard → Developers → API keys; read-only permissions suffice)

Steps

  1. Review the pinned connectors/stripe/SKILL.md and its listed files (SKILL.md, bin/stripe.py). This community draft has not been live-tested end to end.
  2. Before setup: Use a restricted, read-only Stripe API key. This draft cannot charge, refund, or mutate customers; distinguish it from Link by Stripe inside Muse.
  3. Only if the Muse runtime supports pinned repository installs and the source-declared credential and host flow, try `bin/stripe.py balance`. Report the actual response and verify one safe read before any writes.

Prompt to paste into Muse

Inspect this community skill: https://raw.githubusercontent.com/bluman1/muse-connectors/6e31fd44a71f9f28377a1460e64cd7483c3cce22/connectors/stripe/SKILL.md
Read its Files manifest. If this Muse account supports custom skill installation and secure credentials, install exactly those files; otherwise report that the setup is unavailable. Collect credentials through Muse's secure credential flow; never ask me for raw keys in chat. Run the skill's status check and report the actual result.

Account access: API key via the secure credential flow (`credentials.request_api_access`): a Stripe **restricted** API key (Stripe Dashboard → Developers → API keys), pasted once into the hosted form

Allowed hosts: api.stripe.com

Source status check: Source-proposed status check (not live-tested by OpenTools): `bin/stripe.py balance`

A successful source status check may verify only configuration or credentials; it is not proof of a working end-to-end integration.

Services it connects with

These are the services the connector uses.

← Browse all Muse connectors