subscriptionsync

Work with the subscription sync bridge in `openmeter/billing/worker/subscriptionsync/...`. Use when modifying how subscription target state is reconciled into billing artifacts such as invoice lines, split-line groups, or charges; when changing persisted-state loading, reconciler patch routing, or subscription sync tests; and when reasoning about the bridge between subscription views and billing state.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

92%Weight 40%Scale 1-3

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

The body is a tight, highly actionable architectural map of the package with concrete names, routing rules, and verification commands. Its only real weakness is progressive disclosure: it is a single dense file with no offloaded references despite its length.

Suggestions

Move the detailed charge-backed mutation notes and test-suite hierarchy into a reference file (e.g. references/charge-sync.md, references/testing.md) and link to them from the body, keeping SKILL.md as a concise overview.

Extract the reconciler routing rules table into a separate reference so the main body stays a high-level map and details are one level deep.

Consider pulling the package-layout tree into references/layout.md or a diagram asset so the SKILL.md overview stays lean while preserving navigability.

Dimension	Reasoning	Score
Conciseness	Lean, dense architectural guidance that assumes Claude knows Go and billing basics; no padding or explanations of concepts Claude already knows. Every section conveys package-specific knowledge (boundaries, routing rules, invariants) that earns its tokens.	3 / 3
Actionability	Provides concrete file paths, type/function names, explicit routing rules (e.g. 'credit_only + flat price -> flatFeeChargeCollection'), and runnable verification commands. The guidance is specific and copy-paste-ready despite being an architecture/navigation skill with no code samples.	3 / 3
Workflow Clarity	The 'Core Flow' gives a clear six-step sequence with named bridge boundaries, the verification section lists concrete commands, and deleted-subscription cleanup carries explicit guidance. The destructive/batch cases (sync, periodic reconcile) include gating rules and validation commands.	3 / 3
Progressive Disclosure	Content is well-sectioned with a directory tree and clear per-topic navigation, but it is a monolithic single file with no bundle references (references/, scripts/, assets/ are absent). For a body well over 50 lines, some material (e.g. charge-backed mutation notes, test-suite details) could be offloaded to reference files to better earn the top anchor.	2 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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

The description is specific, third-person, and explicitly answers both what the skill does and when to use it with concrete trigger clauses. It is well-scoped to a single package, minimizing conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across three trigger clauses: reconciling target state into 'invoice lines, split-line groups, or charges', changing 'persisted-state loading, reconciler patch routing', and reasoning about the subscription/billing bridge. This matches the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both 'what' (the subscription sync bridge that reconciles target state into billing artifacts) and 'when' via an explicit 'Use when...' clause with three concrete trigger scenarios. Matches the top completeness anchor.	3 / 3
Trigger Term Quality	Uses natural developer-facing terms a user of this codebase would actually say: 'subscription sync', 'invoice lines', 'charges', 'persisted-state loading', 'reconciler patch routing'. Coverage of the relevant vocabulary is good rather than generic jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped to a single package path 'openmeter/billing/worker/subscriptionsync/...' with highly specific triggers, giving it a clear niche that is unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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: openmeterio/openmeter
Path: .agents/skills/subscriptionsync/SKILL.md
Commit: 1cdc2cb

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.