Revenue Dashboard

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

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.

Type: OpenClaw Skill Name: revenue-dashboard Version: 1.0.0 The revenue-dashboard skill is designed to aggregate financial data from Stripe accounts for reporting and anomaly detection. The Python scripts (revenue.py and mrr.py) interact with the official Stripe API (api.stripe.com) using curl via subprocess. While storing API keys in plaintext at ~/.config/stripe/api_key is a security risk, it is a common pattern for simple CLI tools and does not indicate malicious intent. The code logic is transparent, lacks obfuscation, and strictly adheres to the stated purpose of financial monitoring.