revenue-check

Solid

Pull product revenue per app from Firestore (or fixtures) and produce a cash-flow report

AI & Automation 3 stars 1 forks Updated yesterday Apache-2.0

Install

View on GitHub

Quality Score: 82/100

Stars 20%
20
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# revenue-check ## Purpose Aggregate product revenue per app and write `dashboard/state/revenue.json` so cost-model can compute net cash-flow positions. Source-aware: each app declares an adapter (`glam` reads Firestore `creatorEarningsLedger`; `spindine` is deferred to a follow-up — see D001 in the parent plan). Stub mode reads fixtures so fresh-clone tests need zero credentials. ## Arguments | Argument | Required | Description | |---|---|---| | `--stub` | no | Use the FixtureAdapter for every app instead of live Firestore. Fresh-clone tests use this. | | `--live` | no | Explicitly opt in to live adapters that may require ADC. Mutually exclusive with `--stub` / `--fixtures`. | | `--apps` | no | Comma-separated list of apps to query (default: `Styln`). SpinDine is intentionally not in the default list — see D001. | | `--out` | no | Path for revenue.json output (default: `dashboard/state/revenue.json`) | | `--evidence-dir` | no | Where to write the cash-flow report (default: `evidence/revenue-check/`) | | `--costs` | no | Path to costs.json for the cash-flow report (default: `dashboard/state/costs.json`) | | `--as-of` | no | ISO-8601 timestamp to override "now" (deterministic tests) | | `--fixtures` | no | Directory containing per-app fixture subdirectories. Implies `--stub`. | If no mode is supplied: refuses to run live (avoids surprising network calls). Use `--stub` for fresh-clone testing or `--live` for operator-approved Firestore/deferred adapters. ## Prerequisites ...

Details

Author
Silex-Research
Repository
Silex-Research/DontPanic
Created
4 months ago
Last Updated
yesterday
Language
Python
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

app-verify

Drive a running or deployed web app end-to-end as a real user to catch bugs that automated tests and typechecks miss: pages that return HTTP 200 but render wrong, forms that POST 200 yet never save, stat cards that are hardcoded fakes, reports fed by dead database columns, and silent data-layer failures (access rules hiding rows, swallowed query errors, wrong DB identity or connection) — for any framework and any datastore. Also verifies deployments against the live server: build gate, push, deploy, health check, commit match. Use whenever the user wants to verify prod, smoke test the app, QA the app, test every page or tab, check the app as a user, confirm a deploy shipped, ask if production is healthy, or sweep the whole app for what's broken — even if they never say the word "test", and right after any deploy. Do NOT use for: running an existing unit/integration test suite, fixing a typecheck or build error, scoring code quality (that's a "health" check), reviewing a PR diff, setting up CI, debugging one k

0 Updated 1 weeks ago
nikhilkyn-png
AI & Automation Solid

cost-model

Project month-end and next-month spend per app and per LLM provider from existing cost state

3 Updated yesterday
Silex-Research
AI & Automation Solid

revenue-truth

Fetch live ThumbGate revenue, paid orders, and funnel telemetry from production billing endpoints. Use BEFORE answering any question about money, conversion, traffic, or "why we didn't make X." Never quote planning documents as actuals.

24 Updated today
IgorGanapolsky