CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

metronome

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 customers, contracts, or rate cards, designing billable metric group keys, managing credits and commits, configuring invoicing, syncing invoices with Stripe Billing, billing AI applications for token usage, setting up self-serve (PLG) pricing, reviewing customer health, commit burn, portfolios, or renewals, or migrating from Stripe Billing Meters to Metronome.

77

Quality

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is metronome in stripe/ai

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong router-style skill body: token-efficient, dense with non-obvious Metronome-specific rules (idempotency, cents-denominated USD, grace periods, Stripe line-item limits), and well-structured for progressive disclosure to per-task docs and skills. The only gap is that error-recovery/verification loops live in the referenced skills rather than being summarized here.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it never explains what usage-based billing or Stripe is, and every line carries Metronome-specific facts Claude cannot know ("USD credit type is denominated in cents (1000 is 10.00 USD)", "24 hours after billing_period_end_date by default", "1 to 100 event objects"). Rationale sentences (e.g., why a regenerated transaction_id defeats idempotency) are domain judgment calls, not padding, so every token earns its place.

5 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact endpoints ("POST /v1/ingest with a bare JSON array of 1 to 100 event objects", "POST /v2/contracts/edit"), exact field names ("usage_filter", "rollover_fraction", "ending_before", "applicable_product_ids"), hard limits ("Never exceed 250 line items per Stripe invoice"), and a fallback ("use the documentation index... append .md to the page URL"). As the scoring notes allow, absence of code is not penalized when guidance is this specific.

5 / 5

Workflow Clarity

The routing sequence is clear (route via the table → "Read the linked page before answering" → "Read the linked skill in full before starting the task") and validation checkpoints are present for risky operations: "confirm which environment that token targets... and get the user's explicit confirmation before any write", plus separate confirmation for Stripe writes. It falls short of 5 because feedback loops (validate → fix → retry) and post-execution verification steps are delegated to the linked skills rather than present here, and the ingestion path's "a 200 means the events were accepted, not rated" warning lacks a follow-up check for unmatched event types.

4 / 5

Progressive Disclosure

The SKILL.md is a well-organized overview with one-level-deep, clearly signaled references: two routing tables mapping each task to its specific doc page or skill, a "Key documentation" section for ambiguous requests, and the instruction to fetch pages as Markdown. Detail is appropriately split — critical rules stay inline (correctly, as always-load material) while procedures and API shapes live in the linked pages and skills, making navigation easy.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: third-person, explicit what-and-when, dense with concrete domain-specific capabilities and natural trigger phrases, with the Metronome scope clearly governing all listed use cases. No fluff despite its length — every clause names a real capability or trigger.

DimensionReasoningScore

Specificity

The description enumerates concrete actions across the whole domain: "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)". Coverage is comprehensive with no vague filler, matching the anchor for multiple specific concrete actions. It does not fall to 4 because there are no minor gaps — every sub-capability of the domain is named.

5 / 5

Completeness

It explicitly answers both parts: the "what" is the opening capability list, and the "when" is the explicit clause "Use when building, modifying, or reviewing any Metronome integration — including ingesting usage events, creating customers, contracts, or rate cards...". Both are concrete and explicit, matching the anchor-5 example structure; nothing is merely implied.

5 / 5

Trigger Term Quality

Natural user phrasing is comprehensively covered with synonyms: "usage-based billing", "ingesting usage events", "creating customers, contracts, or rate cards", "syncing invoices with Stripe Billing", "billing AI applications for token usage", "self-serve (PLG) pricing", "commit burn", "renewals", and "migrating from Stripe Billing Meters". These match the phrases a user would actually say, satisfying the top anchor including synonyms and product-specific terminology.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (Metronome usage-based billing) with distinct triggers such as "migrating from Stripe Billing Meters to Metronome" and "designing billable metric group keys" that no generic skill would claim. Generic-sounding phrases like "billing AI applications for token usage" are governed by "any Metronome integration", keeping conflict risk minimal; it clearly beats the anchor-4 "minor overlap risk with closely related skills".

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

stripe/ai

Path

providers/cursor/plugin/skills/metronome/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.