billing-automation

Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recurring payment systems.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

57%

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

The body is well-structured and uses progressive disclosure effectively, but leans on concept re-explanation and a non-executable code example, and lacks validation checkpoints for its financially-sensitive workflow. Tightening Core Concepts and grounding the Quick Start in a real library with verification steps would lift the weaker dimensions.

Suggestions

Trim or remove the Core Concepts section (billing intervals, subscription states, proration) since Claude already knows these; keep only billing-specific nuances it would not infer.

Make the Quick Start executable: reference a real library (or justify the placeholder), add the missing 'datetime' import, and show a verifiable call such as checking the returned subscription state.

Add a validation checkpoint after processing a billing cycle (e.g., assert invoice status / confirm charge succeeded) to support the destructive/batch financial workflow.

Dimension	Reasoning	Score
Conciseness	The body is reasonably lean, but the Core Concepts section re-explains concepts Claude already knows (billing intervals, subscription states, proration), which is unnecessary padding. Not a 1 because the prose itself is tight, not a 3 because the concept re-explanation does not earn its tokens.	2 / 3
Actionability	Quick Start provides concrete Python with a clear API sequence, but it imports a fictional 'billing' module and omits the 'datetime' import, so it is not copy-paste executable against a real library. Matches the score-2 anchor of concrete guidance with missing key details.	2 / 3
Workflow Clarity	Quick Start lists a sequence (initialize, create subscription, process cycle) but includes no validation or verification checkpoints for financially-sensitive batch billing operations, which the rubric caps at 2. Not a 1 since a sequence is present.	2 / 3
Progressive Disclosure	A concise overview points via a clearly-signaled, one-level-deep reference to the real 'references/details.md' file (verified present), splitting detail appropriately — matching the score-3 anchor.	3 / 3
	Total	9 / 12 Passed

Description

100%

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 concise, specific, and complete: it names concrete billing capabilities and gives explicit 'Use when' triggers in third person. It is distinctive and would reliably activate for the right requests.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'recurring payments, invoicing, subscription lifecycle, and dunning management' — matching the score-3 anchor that enumerates specific capabilities rather than vague language.	3 / 3
Completeness	Explicitly answers both 'what' (build automated billing systems for the listed capabilities) and 'when' ('Use when implementing subscription billing, automating invoicing, or managing recurring payment systems').	3 / 3
Trigger Term Quality	Natural user-facing terms like 'subscription billing', 'automating invoicing', and 'recurring payment systems' give good coverage of what a user would actually say; 'dunning' is domain jargon but the rest are common.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear billing-automation niche with distinct triggers unlikely to collide with other skills, rather than generic 'helps with' phrasing.	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: wshobson/agents
Commit: 5cc2549

Reviewed: 8 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.