billing-automation

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

50%

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

The skill body is well-structured and concise but stays at a high level: guidance is actionable as a checklist rather than executable, the workflow lacks an error-feedback loop, and the single external reference points to a file that is not present in the bundle.

Suggestions

Bundle the referenced resources/implementation-playbook.md (or remove the reference) so the promised detailed patterns, checklists, and examples are actually reachable.

Add an explicit feedback loop for the validation step (e.g., "If sandbox validation or ledger reconciliation fails, fix the config and re-validate before proceeding") to satisfy workflow clarity for payment operations.

Tighten the body by dropping the verbatim repeat of the frontmatter description and consolidating the single playbook mention into one clearly signaled reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean bullet points with no concept explanation, but it repeats the frontmatter description verbatim as the opening line and re-states the playbook reference in both Instructions and Resources, so it could be tightened.	2 / 3
Actionability	Instructions give concrete task directives ("Define plans...", "Map subscription lifecycle states...", "Validate with sandbox payments") but stay high-level with no specific commands, code, or copy-paste-ready detail.	2 / 3
Workflow Clarity	Steps are listed and a validation step is mentioned, but there is no validate→fix→retry feedback loop for payment/batch operations, which per the feedback_loops note caps workflow clarity at 2.	2 / 3
Progressive Disclosure	Sections are well organized and the playbook reference is clearly signaled and one level deep, but the referenced resources/implementation-playbook.md is not bundled, so the promised detailed content is unreachable and navigation is incomplete.	2 / 3
	Total	8 / 12 Passed

Description

67%

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 specific and carves a clear niche, but it lacks an explicit "when to use" trigger and mixes natural terms with billing jargon, leaving trigger quality and completeness at the mid level.

Suggestions

Add an explicit trigger clause such as "Use when implementing SaaS subscription billing, invoicing, dunning, or tax handling" to satisfy the completeness 'when' requirement.

Soften jargon by adding user-natural variants alongside technical terms (e.g., "dunning (failed-payment recovery)", "subscription/SaaS billing") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete capabilities — "recurring billing, invoice generation, dunning management, proration, and tax calculation" — matching the multi-action anchor rather than the vague or partial anchors.	3 / 3
Completeness	Clearly states what the skill does but has no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms ("billing", "invoice", "recurring billing", "tax calculation") but also jargon users rarely say ("dunning", "proration") and misses common variations like "subscription", "SaaS", or "failed payments".	2 / 3
Distinctiveness Conflict Risk	The scoped niche of automated billing systems with named sub-capabilities is clearly distinguishable and unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 9fc5f98

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