{"id":70263,"plugin_id":"plugin_asdk_app_6abdd3dbb8808191bb92f7ef6bfdc2af","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-29T12:06:41.836Z","digest":"e25eec86ae6fcc03f6d9b747b363f7ab100f98e64d4db129247d67c36f565f87","against":null,"payload":{"description":"Use this skill when the user wants a quick health and revenue check of their RevenueDot project. It covers store connections, failed webhooks, billing problems and the key revenue numbers, summarised in a few lines. It needs the RevenueDot MCP server connected.","included_files":[],"name":"weekly-revenue-check","skill_md_contents":"---\nname: weekly-revenue-check\ndescription: Use this skill when the user wants a quick health and revenue check of their RevenueDot project. It covers store connections, failed webhooks, billing problems and the key revenue numbers, summarised in a few lines. It needs the RevenueDot MCP server connected.\nlicense: MIT\n---\n\n# Weekly revenue check\n\nRevenueDot is an open-source backend for in-app purchases that speaks RevenueCat's API. This skill reads a project with the RevenueDot MCP tools and reports in plain words. It changes nothing unless the user asks.\n\nRevenueDot is not affiliated with RevenueCat, Inc.\n\n## Steps\n\n1. `get-project-health`. For each app in `apps`, note `credentials_configured` and the notification health fields. In `webhooks`, note `delivered_percent_24h` and every entry of `failing` (name, url, `last_error`).\n2. `get-metrics` with no `metric` for the overview (MRR, revenue, active subscriptions, active trials, new customers, active customers, last 28 days, USD). Then `get-metrics` with `metric: \"mrr\"` and `days: 28`, and again with `metric: \"new_customers\"`, to see the direction.\n3. `list-events` with `types: [\"BILLING_ISSUE\"]` and a small `limit` to count recent billing problems, and `types: [\"CANCELLATION\"]` for cancellations.\n4. If a webhook is failing: `list-webhook-deliveries` with `webhook_id` and `status: \"failed\"`. Quote the last error and HTTP status. Offer `send-test-webhook` once the user says the endpoint is fixed, and `retry-webhook-delivery` for the failed ones. Do not retry without the user's yes.\n\n## Report\n\nWrite at most five lines. Line 1 is the headline itself, with the MRR number: no greeting or summary line before it, and no notes after line 5 unless the user asks.\n\n1. The headline: MRR now, and whether it rose or fell over 28 days.\n2. New customers and active subscriptions.\n3. Billing issues and cancellations this week.\n4. Problems: a store connection that is not configured or a failing webhook, with its error. Say \"none\" if there are none.\n5. The one thing the user should do next, or \"nothing needed\".\n\nSandbox numbers are not revenue: use the production overview (the default) and mention sandbox only if the user asks.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}