{"skills":[{"name":"metronome-best-practices","description":"Guides Metronome usage-based billing integration decisions — event ingestion (single and batch, idempotency, billable metrics), contract design (rate cards, overrides, dimensional pricing, products), invoicing lifecycle (grace periods, finalization, Stripe sync), credit and commit management (prepaid, postpaid, thresholds, auto-recharge), and Stripe integration (arrears invoicing, tax providers, line item limits). Use when building, modifying, or reviewing any Metronome integration — including ingesting usage events, creating contracts or rate cards, managing credits and commits, configuring invoicing, or syncing invoices with Stripe Billing.","files":["SKILL.md"]},{"name":"metronome-create-contract","description":"Creates a Metronome contract for an existing customer from signed order form terms — commits, credits, and rate overrides. Use when asked to create a contract, set up a contract, add a commit or credit, configure pricing, or start a new contract.","files":["SKILL.md"]},{"name":"metronome-create-customer","description":"Creates a new customer record representing one of the merchant's own end customers in Metronome, with name, ingest alias, Salesforce ID, and Slack channel. Use when asked to create a customer, add a customer, onboard a new account, or set up a customer's account in Metronome.","files":["SKILL.md"]},{"name":"metronome-csm-reviews","description":"Customer health reviews for CSMs — anomaly detection (MoM spend variance, stuck DRAFT invoices, commit burn spikes), commit health (burn rate, overrun and breakage risk for a single customer), portfolio briefing (monthly all-customer report with exec summary and action items), and renewal prep (contract terms, trailing consumption, TCV scenarios). Use when asked which customers need attention, how a customer is tracking against their commit, for a monthly report or portfolio briefing, or to prep for a renewal.","files":["SKILL.md"]},{"name":"metronome-group-keys","description":"Designs group_keys for a billable metric across pricing, invoice presentation, spend breakdowns, seat-based credits, and usage alerts — and flags cardinality risk (a combined key's cost is the product of every dimension's cardinality, not the sum) before it gets baked into an immutable metric. Use when a billable metric needs more than one flat pricing dimension, when deciding pricing_group_key vs. presentation_group_key, or when an existing setup has slow invoices or unexpectedly costly spend breakdowns.","files":["SKILL.md"]},{"name":"metronome-plg-billing","description":"Guides PLG founders through billing setup, pricing changes, and customer diagnostics on Metronome. Three modes: start billing (pricing intent through verified draft invoice), change pricing (blast radius enumeration and before/after diff), and customer story (single-customer diagnostic narrative with actionable next step). Use when a founder or technical decision-maker asks to bill their first customer, set up pricing, modify rates or tiers, investigate a customer account, or translate a pricing page into Metronome objects. Targets users who think in business terms (dollars, invoices, customers) rather than API objects.","files":["SKILL.md"]},{"name":"metronome-setup-catalog","description":"End-to-end Metronome setup from pricing intent to a verified live contract — billable metrics, products, rate card, customer, and contract in order. Use when asked to set up Metronome from scratch, bill a first customer, build a pricing model, create a billable metric or product, configure a rate card, or complete any compound billing setup task end-to-end.","files":["SKILL.md"]},{"name":"metronome-token-billing","description":"Set up and verify Metronome Token Billing for an AI application through public APIs. Use when an agent needs to model one or more AI plans, including fixed fees, postpaid token usage, included or prepaid credits, top-ups, custom pricing units, usage dimensions, selected models and markup; create or update the managed rate card and packages; provision a customer; integrate usage reporting; or validate the Stripe and Metronome billing flow. Do not use for unrelated Metronome pricing models.","files":["SKILL.md"]},{"name":"stripe-to-metronome-migration","description":"Guides migration from Stripe Usage-Based Billing (Billing Meters and Subscriptions) to Metronome. Covers scoping and discovery (metering, pricing models, credit grants, dashboards), design (concept mapping, billable metrics, group keys, rate cards, integration pattern selection), implementation (product catalog setup, event ingestion, customer creation, contracts, credit grant migration, alerting), testing (parallel run parity checks, sandbox validation), and production cutover (legacy customer migration, rollback planning). Use when planning, executing, or troubleshooting a migration from Stripe UBBv1 to Metronome — including scoping the effort, mapping Stripe objects to Metronome equivalents, designing billable metrics and group keys, running parallel validation, migrating credit grants, or cutting over production customers.","files":["SKILL.md"]}]}