Conciseness

Every line carries non-obvious Metronome facts Claude cannot know — "24 hours after billing_period_end_date by default", "250 line items per Stripe invoice", "1000 is 10.00 USD", "a bare JSON array of 1 to 100 event objects" — with zero generic concept explanation. It assumes competence and every token earns its place, matching the lean level-5 anchor.

Actionability

Guidance is fully executable: exact endpoints ("POST /v1/ingest", "POST /v2/contracts/edit", "POST /v1/credits/migrateToContracts"), exact field names (transaction_id, usage_filter, rollover_fraction, applicable_product_ids), exact body shapes, and hard numeric limits. As an instruction-only skill its concrete, specific guidance satisfies the actionability bar without code.

Workflow Clarity

The route → read-linked-page → confirm → execute sequence is clear, with explicit pre-write validation gates ("get the user's explicit confirmation before any write", "identify the Stripe account and mode behind the Stripe key… and confirm those writes separately"). However, explicit validate/retry feedback loops for error recovery are delegated to the linked sub-skills rather than present in the body itself, so it fits "most checkpoints present; minor validation gaps" rather than the level-5 anchor requiring feedback loops and checklists.

Progressive Disclosure

The body is a clean overview router: two well-organized tables map each task to a one-level-deep linked doc or hosted skill, with a clearly signaled fallback (the llms.txt index and "append .md to the page URL"). No local bundle files exist, and content is appropriately split out — the inline Critical rules are exactly the high-frequency safety/correctness facts that belong in the main file.

Specificity

Lists multiple concrete capability areas each with specific sub-features: "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)". Coverage is comprehensive with no discernible gaps, so it matches the top anchor rather than the "minor gaps" level 4.

Completeness

Explicitly answers both questions: the "what" is "Guides Metronome usage-based billing integration decisions" across the five named areas, and the "when" is "Use when building, modifying, or reviewing any Metronome integration — including…" followed by concrete trigger phrases. Both are present and explicit, matching the level-5 anchor.

Trigger Term Quality

The "Use when…" clause enumerates natural phrases users would actually say: "ingesting usage events", "creating customers, contracts, or rate cards", "managing credits and commits", "syncing invoices with Stripe Billing", "billing AI applications for token usage", "setting up self-serve (PLG) pricing", and "migrating from Stripe Billing Meters to Metronome". Synonyms and adjacent phrasings (customer health, commit burn, portfolios, renewals) are covered; nothing common is missing.

Distinctiveness Conflict Risk

Every trigger and capability is anchored to the specific vendor ("Metronome", "Stripe Billing Meters to Metronome"), giving it a clear niche with minimal overlap risk against generic billing or Stripe-only skills. It is well above the "minor overlap risk with closely related skills" level-4 anchor.