billing-automation

Master automated billing systems including recurring billing, invoice generation, dunning management, proration, and tax calculation.

Quality

32%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/billing-automation/SKILL.md

Quality

Discovery

42%

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 lists specific billing-related capabilities which is a strength, but it reads more like a topic header ('Master automated billing systems') than an actionable skill description. It critically lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill. The imperative 'Master' framing is also unusual and doesn't follow the recommended third-person voice pattern.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about setting up recurring payments, generating invoices, handling failed payment retries, or calculating prorated charges.'

Rewrite in third-person declarative voice: 'Implements automated billing systems including...' instead of 'Master automated billing systems...'

Include common user-facing trigger terms like 'subscription', 'payment retry', 'failed payment', 'billing cycle', 'charge', and 'SaaS billing' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: recurring billing, invoice generation, dunning management, proration, and tax calculation. These are clearly defined capabilities.	3 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' is framed more as a topic mastery statement than a clear action description, pushing it to 1.	1 / 3
Trigger Term Quality	Includes relevant domain terms like 'billing', 'invoice', 'dunning', 'proration', and 'tax calculation', but misses common user variations like 'subscription billing', 'payment retry', 'failed payments', 'billing cycle', or 'charges'. The word 'Master' is also not a natural trigger term.	2 / 3
Distinctiveness Conflict Risk	The billing domain is fairly specific, but terms like 'invoice generation' and 'tax calculation' could overlap with general accounting, invoicing, or tax-specific skills. Without explicit trigger boundaries, there's moderate conflict risk.	2 / 3
	Total	8 / 12 Passed

Implementation

22%

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

This skill is essentially a table of contents with vague bullet points that defer all substantive content to a resource file. It lacks any concrete code, schemas, examples, or specific workflows that would make it actionable. The billing domain involves complex multi-step processes and financial risk, yet the skill provides no validation checkpoints, error handling patterns, or executable guidance.

Suggestions

Add at least one concrete, executable code example (e.g., a subscription lifecycle state machine, an invoice generation snippet, or a dunning retry workflow) directly in the SKILL.md body.

Include an explicit multi-step workflow with validation checkpoints for a core billing operation like 'processing a plan change with proration' — including verification steps before charging.

Provide a concrete data model or schema example (e.g., subscription states, invoice line items) so Claude has specific structures to work with rather than abstract directives.

Replace vague instructions like 'Model taxes and compliance requirements per region' with specific guidance such as tax calculation patterns, supported tax types, or integration examples with tax APIs.

Dimension	Reasoning	Score
Conciseness	The skill is relatively brief but includes some unnecessary sections like 'Use this skill when' and 'Do not use this skill when' that are somewhat obvious and don't add much value. The instructions themselves are high-level bullet points without padding, but the overall structure has some bloat.	2 / 3
Actionability	The instructions are entirely abstract and vague — 'Define plans, pricing, billing intervals' and 'Implement invoicing, payments, retries' provide no concrete code, commands, schemas, or specific examples. Everything describes rather than instructs, with the real content deferred to a resource file.	1 / 3
Workflow Clarity	The instructions list high-level activities but lack clear sequencing, validation checkpoints, or feedback loops. For a domain involving financial transactions and destructive operations (charging customers), there are no explicit verification steps or error recovery patterns in the main skill body.	1 / 3
Progressive Disclosure	There is a reference to a resource file for detailed patterns, which is good. However, the main skill body is so thin on actionable content that it feels like the entire skill is deferred to the resource file, making the SKILL.md itself nearly empty of useful guidance.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 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: sickn33/antigravity-awesome-skills
Commit: 43280f9

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