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.
79
Quality
78%
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 ./.agent/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
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, with good progressive disclosure to detailed resources. However, it severely lacks actionability—there are no concrete code examples, specific commands, or executable guidance. The instructions read as a high-level checklist rather than actionable steps Claude can follow.
Suggestions
Add concrete code examples for at least one billing scenario (e.g., Stripe subscription creation, invoice generation snippet)
Include specific validation commands or checks for testing billing flows in sandbox environments
Provide an example input/output for proration calculation or dunning workflow to make guidance executable
Add explicit verification steps before production rollout (e.g., 'Run reconciliation script X, verify output matches expected ledger state')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, avoiding unnecessary explanations of what billing or subscriptions are. Every section serves a purpose and assumes Claude understands the domain. | 3 / 3 |
Actionability | The instructions are vague and abstract ('Define plans, pricing...', 'Implement invoicing...') with no concrete code, commands, or executable examples. It describes what to do rather than showing how. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence but lack explicit validation checkpoints. For billing systems involving payments and tax compliance, there should be clearer feedback loops and verification steps before production. | 2 / 3 |
Progressive Disclosure | Clear overview structure with well-signaled one-level-deep references to implementation-playbook.md for detailed patterns. Navigation is straightforward and content is appropriately split. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- Dokhacgiakhoa/antigravity-ide
- Commit
3395991
- 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.