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.
76
Quality
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/skills/billing-automation/SKILL.mdQuality
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 an explicit 'Use when...' clause with natural trigger terms, and carves out a distinct domain (subscription/recurring billing) that minimizes conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'recurring payments, invoicing, subscription lifecycle, and dunning management' - these are distinct, actionable capabilities rather than vague abstractions. | 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 practitioners actually use when discussing billing systems. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on billing/subscription domain with specific 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
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-scoped and concise but lacks actionable content. The instructions read as a high-level checklist rather than executable guidance, with no code examples, schemas, or concrete patterns. For a complex domain like billing automation involving financial transactions, the absence of validation checkpoints and concrete implementation details significantly limits its utility.
Suggestions
Add concrete code examples for at least one core workflow (e.g., subscription creation, invoice generation, or dunning retry logic) with specific data structures or API patterns
Include explicit validation checkpoints in the workflow, especially for payment processing and tax calculation steps (e.g., 'Validate in sandbox -> verify ledger entries -> only then enable production')
Provide a concrete schema or example for subscription state machine, proration calculation, or invoice structure rather than just describing these abstractly
Either inline more actionable content from the implementation playbook or ensure the skill provides enough standalone guidance to be useful without requiring the external file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using bullet points to convey scope without explaining what billing, subscriptions, or invoicing are. Every section serves a purpose without padding. | 3 / 3 |
Actionability | The instructions are entirely abstract and vague - 'Define plans', 'Map subscription lifecycle', 'Implement invoicing' provide no concrete code, commands, schemas, or executable examples. This describes rather than instructs. | 1 / 3 |
Workflow Clarity | There is an implicit sequence (define -> map -> implement -> model -> validate), but no explicit validation checkpoints, error recovery steps, or feedback loops for what are inherently risky financial operations. | 2 / 3 |
Progressive Disclosure | References the implementation playbook appropriately, but the main content is too thin - it's essentially just a pointer to another file without providing enough actionable overview content to stand alone. | 2 / 3 |
Total | 8 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- duclm1x1/Dive-Ai
- Commit
20ba150
- 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.