What problem does it solve? When querying a unified company database that merges Stripe, HubSpot, and app data, it is hard to know which tool answers which question or what metrics like MRR and collection rate actually mean. This Skill provides the data map and definitions so every analytics question lands on the right tool with the right interpretation. ## Core Features & Use Cases - Tool-to-question mapping: A lookup table routes questions about revenue health, churn, contacts, identities, and freshness to the correct curated api.* view tool such as stripe_snapshot, identity_360, or mrr_trend. - Canonical metric definitions: Precise wording for MRR, paying subs, collection rate, MRR at risk, churn, and tagged tracks so answers stay consistent. - Revenue caveat enforcement: Always distinguishes booked MRR from collected revenue, surfacing the gap as the real revenue-health story. - Use Case: A founder asks "are we healthy this month?" — the Skill routes to revenue_health, leads with the tool's plain-English summary, and frames booked MRR against collected cash. ## Quick Start Ask what MRR means and which tool to use for checking whether revenue is healthy this month.
