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.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill billing-automationOverall
score
78%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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.
This is a well-crafted skill description that follows best practices. It uses third person voice, lists specific capabilities, includes natural trigger terms, and explicitly states both what the skill does and when to use it. The domain-specific terminology (dunning, subscription lifecycle) makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'recurring payments, invoicing, subscription lifecycle, and dunning management' - these are distinct, actionable capabilities within the billing domain. | 3 / 3 |
Completeness | Clearly answers both what ('Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management') and when ('Use when implementing subscription billing, automating invoicing, or managing recurring payment systems'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'subscription billing', 'invoicing', 'recurring payments', 'dunning management'. These are terms developers and product managers commonly use when discussing billing systems. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on billing/subscription systems with distinct triggers like 'dunning', 'subscription lifecycle', 'recurring payments' that are unlikely to conflict with general payment or e-commerce skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and concise, appropriately deferring detailed implementation to a referenced playbook. However, the main content lacks any concrete, actionable guidance - it reads as a high-level checklist rather than executable instructions. For a complex domain like billing automation involving financial transactions, the absence of specific code examples, validation steps, and error handling patterns significantly limits its utility.
Suggestions
Add at least one concrete code example showing a basic billing workflow (e.g., subscription creation, invoice generation, or payment retry logic)
Include explicit validation checkpoints in the instructions, especially for testing payments and verifying tax calculations before production
Provide a specific example of dunning workflow with retry intervals and failure handling rather than just mentioning 'dunning workflows'
Add a minimal working example or pseudocode for proration calculation since this is a common pain point
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using bullet points without unnecessary explanation. It assumes Claude understands billing concepts and doesn't waste tokens explaining what subscriptions or invoices are. | 3 / 3 |
Actionability | The instructions are entirely abstract and vague - 'Define plans', 'Map subscription lifecycle', 'Implement invoicing' provide no concrete code, commands, or specific examples. There's nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | There's a rough sequence implied (define plans → map lifecycle → implement workflows → model taxes → validate), but no explicit validation checkpoints, error recovery steps, or feedback loops for what are clearly risky financial operations. | 2 / 3 |
Progressive Disclosure | Clear structure with appropriate sections, and correctly references external resource (implementation-playbook.md) for detailed patterns. One-level-deep reference is well-signaled and the overview stays concise. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
- 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.