Revenue Dashboard

Track revenue across multiple Stripe accounts with automated daily reports, goal tracking, and anomaly alerts. Use when checking revenue, running nightly rev...

Security Scan

The skill appears to do what it claims (pull Stripe data and produce reports) but the package metadata does not declare the required Stripe credential and there are a few operational risks (local secret file + curl via subprocess) you should understand before installing.

Purpose & Capability

The skill's purpose is a Stripe revenue dashboard and the runtime instructions and Python scripts clearly require a Stripe secret key and a configuration file under ~/.config/revenue-dashboard. However, the registry metadata declares no required credentials or primaryEnv. That mismatch (code and SKILL.md need a Stripe key but metadata lists none) is an incoherence you should treat as suspicious.

Instruction Scope

SKILL.md stays on-topic: it tells you to store a Stripe secret at ~/.config/stripe/api_key, create ~/.config/revenue-dashboard/config.json, and run the included scripts or an example nightly cron. Instructions do not ask for unrelated files or secrets. Note: the cron example would enable scheduled/automated runs (if you install such a job or the agent acts on that payload).

Install Mechanism

There is no install spec (instruction-only + included scripts). No external downloads or installers are invoked by the skill itself. That reduces supply-chain risk.

Credentials

The skill requires access to a Stripe secret key (it expects it in ~/.config/stripe/api_key), which is proportionate to the stated function. But the published metadata does not declare this credential or primaryEnv, which is inconsistent and risky because automated systems may not surface the need for the secret. Also note the scripts pass the key to curl with -u, which can expose the key to other local users via process arguments on some systems.

Persistence & Privilege

The skill is not marked always:true and does not include an install step that forces permanent presence. However, SKILL.md includes an example nightly cron payload that, if used, will run the skill automatically. The skill being invocable by the agent (disable-model-invocation=false) is normal but combined with an undeclared secret is something to be cautious about.

What to consider before installing

This skill's code and README expect a Stripe secret saved at ~/.config/stripe/api_key and a config at ~/.config/revenue-dashboard/config.json, but the registry metadata didn't declare any required credential — that's a red flag. Before installing or running: (1) confirm the skill's source and trustworthiness; (2) store your Stripe key securely (file perms 600) and consider using a short-lived key or restricted scoped key if Stripe supports it; (3) be aware the scripts call curl with -u <key>: which can expose the key in process listings on some systems — consider modifying the code to use an Authorization header (Bearer token) or environment variables passed securely; (4) avoid blindly enabling the example nightly cron unless you want automated access to your Stripe account; (5) if you plan to use this skill in a multi-user environment, ensure other users cannot read the key file. Finally, ask the publisher to update registry metadata to explicitly declare the required Stripe credential (primaryEnv or requires.env) so automation and reviewers can see the requirement up-front.

Consolidated revenue intelligence across your Stripe accounts. Pulls charges, refunds, subscriptions, and MRR in a single command with period-over-period comparison, goal tracking, and anomaly detection.

Quick Start

1. Store your Stripe secret key at ~/.config/stripe/api_key
2. Copy the config template and edit it:

   cp {baseDir}/references/config-template.json ~/.config/revenue-dashboard/config.json
   

3. Edit ~/.config/revenue-dashboard/config.json with your Stripe account IDs and revenue goals
4. Run your first report:

   python3 {baseDir}/scripts/revenue.py --period today
   

Commands

Revenue Report

python3 {baseDir}/scripts/revenue.py --period <period> [--format <format>]

Periods: today, yesterday, week, month, quarter, year, all Formats: json (default), markdown, summary

Goal Tracking

python3 {baseDir}/scripts/revenue.py --period month --goals

Shows progress toward your monthly and annual revenue targets defined in config.

MRR & Subscription Metrics

python3 {baseDir}/scripts/mrr.py [--breakdown]

Pulls active subscriptions across all accounts. With --breakdown, groups by plan/price.

Anomaly Detection

python3 {baseDir}/scripts/revenue.py --period today --anomalies

Flags unusual activity: revenue spikes/drops >2x vs 7-day average, refund rate >10%, or zero-revenue days.

Nightly Review Workflow

Run this sequence for a complete daily close:

# 1. Yesterday's final numbers
python3 {baseDir}/scripts/revenue.py --period yesterday --format markdown --goals --anomalies

# 2. Monthly trend context
python3 {baseDir}/scripts/revenue.py --period month --format summary

# 3. Current MRR snapshot
python3 {baseDir}/scripts/mrr.py --breakdown

Write findings to your daily notes. Propose next-day actions based on what the numbers show.

Automated Nightly Cron

{
  "name": "nightly-revenue",
  "schedule": {"kind": "cron", "expr": "0 3 * * *", "tz": "America/Los_Angeles"},
  "sessionTarget": "main",
  "payload": {
    "kind": "systemEvent",
    "text": "Run the nightly revenue review using the revenue-dashboard skill. Pull yesterday's revenue, check goals, flag anomalies, and propose tomorrow's plan."
  }
}

Configuration

See references/config-template.json for the full config schema. Key fields:

{
  "accounts": {
    "my_saas": "acct_XXXXXXXXXXXX",
    "my_shop": "acct_YYYYYYYYYYYY"
  },
  "goals": {
    "monthly": 10000,
    "annual": 120000
  },
  "currency": "usd",
  "anomaly_threshold": 2.0
}

Key Metrics Tracked

• Gross / Net Revenue per account and consolidated
• Refund rate as percentage of gross
• Transaction count and average ticket size
• Period-over-period growth % with directional indicator
• MRR / ARR from active subscriptions
• Goal progress as percentage with projected monthly/annual totals
• Anomaly flags for unusual patterns

Interpreting Output

• Growth > 0%: Revenue accelerating vs prior period
• Refund rate > 5%: Investigate product or fulfillment issues
• MRR trend: The most important metric for subscription businesses
• Goal pace: "On pace" means current run rate meets the target; "Behind" means action needed

Multi-Account Strategy

Add as many Stripe accounts as you operate. The dashboard consolidates everything but preserves per-account detail so you can see which products drive growth. Common setups:

• SaaS + info products: Track subscription MRR alongside one-time course/template sales
• Multiple brands: See consolidated revenue while monitoring each brand independently
• Marketplace + services: Separate platform fees from direct service revenue