← Back to Skills Marketplace
Stripe Analytics
by
Tomas Mikula
· GitHub ↗
· v1.0.2
· MIT-0
381
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install stripe-analytics
Description
Complete Stripe analytics dashboard for SaaS founders (READ-ONLY). CORE METRICS: MRR, churn (revenue/customer), NRR, LTV/CAC CUSTOMER: Top LTV, segments (pla...
Usage Guidance
This skill appears internally consistent for read-only Stripe analytics. Before installing: 1) Provide only a Stripe restricted read-only key (scopes: read:customers, read:subscriptions, read:invoices, read:payment_intents). Do NOT supply a full secret key with write/refund permissions. 2) Confirm you trust the skill owner/source (source is unknown in registry). 3) Note the minor version mismatch (registry 1.0.2 vs package.json 1.0.3) — consider reviewing the included skill/skill.js yourself or running it in a sandboxed environment first. 4) Rotate the restricted key if you later remove the skill. If you need higher assurance, request the full, untruncated skill.js and verify there are no outbound calls beyond api.stripe.com or any hidden persistence.
Capability Analysis
Type: OpenClaw Skill
Name: stripe-analytics
Version: 1.0.2
The skill is a legitimate Stripe analytics tool designed to calculate SaaS metrics like MRR and churn. The implementation in `skill/skill.js` uses the official Stripe API (api.stripe.com) with proper pagination and error handling, and the documentation in `SKILL.md` correctly advises users to use restricted, read-only API keys. No evidence of data exfiltration, unauthorized execution, or malicious prompt injection was found.
Capability Assessment
Purpose & Capability
Name/description (Stripe analytics) align with requested STRIPE_READ_KEY and node runtime. package.json, SKILL.md, and skill.js all reference Stripe API endpoints and analytics functions consistent with the stated purpose. Minor version string mismatch between registry (1.0.2) and package.json/SKILL.md (1.0.3) and an unknown upstream source are noted but do not change functional coherence.
Instruction Scope
SKILL.md explicitly limits actions to read-only Stripe scopes and the code only fetches from api.stripe.com endpoints and computes metrics. Instructions do not ask the agent to read unrelated files, system credentials, or post data to third-party endpoints. The SKILL.md mentions no persistence and the code does not write files or log secrets.
Install Mechanism
No install spec provided (instruction-only plus shippped JS), so nothing is downloaded from arbitrary URLs. package.json indicates node as required runtime. No high-risk install steps (no external archive downloads or unknown package registries).
Credentials
Only STRIPE_READ_KEY is required (primaryEnv). The key is used only to call Stripe API (Authorization header). No unrelated environment variables, secret-scanning triggers, or config paths are requested. SKILL.md recommends restricted read-only scopes which is appropriate and proportional.
Persistence & Privilege
always is false and the skill does not request persistent system privileges or modify other skills. The skill does not store credentials or persist data on disk according to SKILL.md and code. Autonomous invocation is allowed (platform default) but not combined with other red flags.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install stripe-analytics - After installation, invoke the skill by name or use
/stripe-analytics - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
- Added standard `install` and `env` fields for improved deployment clarity.
- Introduced `metadata` for OpenClaw integration (emoji, docs link, required environment variables).
- Updated footer and tag formatting, incremented version in the footer.
- No user-facing logic or feature changes.
v1.0.1
- Stripe permissions updated: now requires read:payment_intents (in addition to previous scopes) for improved failed payment recovery analytics.
- Clarified key setup instructions: "read: Payment Intent" scope is now required and must be set as read-only.
- Environment config note updated: caching is recommended caller-side only, not built-in.
- Error gating messages and troubleshooting sections updated to reflect new permissions.
- No changes to endpoints, output schema, or core workflows.
v1.0.0
stripe-analytics 1.0.0 – Initial Release
- Offers a comprehensive, read-only Stripe analytics dashboard for SaaS founders.
- Tracks key metrics: MRR, churn (revenue/customer), NRR, LTV/CAC.
- Provides insights on top customers, customer segments, health scores, revenue trends, and failed payment recovery.
- Includes actionable alerts, 1-12 month MRR forecasting, and detailed segment breakdowns.
- Requires a Restricted Stripe Read Key; supports several parallel API calls with rate limiting and caching.
- Exposes user-invocable slash commands: /stripe-metrics, /stripe-churn, /stripe-top-customers.
Metadata
Frequently Asked Questions
What is Stripe Analytics?
Complete Stripe analytics dashboard for SaaS founders (READ-ONLY). CORE METRICS: MRR, churn (revenue/customer), NRR, LTV/CAC CUSTOMER: Top LTV, segments (pla... It is an AI Agent Skill for Claude Code / OpenClaw, with 381 downloads so far.
How do I install Stripe Analytics?
Run "/install stripe-analytics" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Stripe Analytics free?
Yes, Stripe Analytics is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Stripe Analytics support?
Stripe Analytics is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Stripe Analytics?
It is built and maintained by Tomas Mikula (@tomas-mikula); the current version is v1.0.2.
More Skills