billing-automation

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

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/billing-automation/SKILL.md

The canonical home for this skill is billing-automation in rmyndharis/antigravity-skills

Quality

Content

67%Weight 40%Scale 1-5

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

The body is well-structured, concise, and lays out a sensible sequenced workflow with validation, but its instructions stay at a high-level deliverable checklist with no executable detail, and the single referenced deep-dive file is missing. Adding concrete examples or ensuring the playbook file exists would materially strengthen it.

Suggestions

Provide at least one concrete, executable artifact inline (e.g. a sample plan/pricing schema, a dunning-state transition snippet, or a tax-calculation command) rather than deferring entirely to the playbook.

Create the referenced 'resources/implementation-playbook.md' (or fix the path to match the actual bundle location) so the progressive-disclosure pointer resolves.

Add an explicit validation feedback loop — 'If reconciliation fails, fix the discrepancy and re-run' — to turn the validation mention into a true checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, but the opening line duplicates the frontmatter description verbatim and the playbook reference is stated twice (Instructions and Resources), minor padding that could be trimmed.	4 / 5
Actionability	Instructions name concrete deliverables (plans, lifecycle states, dunning workflows, tax models) but give no executable code, commands, schemas, or specific steps — all detail is deferred to the referenced playbook.	3 / 5
Workflow Clarity	The six instructions form a clear sequence that ends with validation ('Validate with sandbox payments and reconcile ledger outputs'), satisfying the validation requirement for batch/financial operations, though an explicit fix-and-retry feedback loop is absent.	4 / 5
Progressive Disclosure	Sections are well-organized and the detailed material is signaled as a one-level-deep reference, but the referenced 'resources/implementation-playbook.md' does not exist in the bundle, leaving a broken navigation pointer.	4 / 5
	Total	15 / 20 Passed

Description

71%Weight 40%Scale 1-5

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 well-targeted to a distinct billing-automation niche, but it states only what the skill does without any explicit 'when to use it' trigger guidance. Adding a 'Use when…' clause with natural trigger phrases would raise both completeness and trigger-term quality.

Suggestions

Append a 'Use when…' clause naming concrete triggers, e.g. 'Use when implementing SaaS subscription billing, dunning, proration, or tax/VAT/GST handling.'

Add user-natural synonyms currently missing — 'subscription', 'SaaS', 'payments', 'renewals' — to broaden trigger coverage.

Consider dropping the imperative 'Master' for a third-person verb form ('Automates…', 'Handles…') to match the rubric's voice guidance.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'recurring billing, invoice generation, dunning management, proration, and tax calculation' — giving comprehensive coverage of the billing-automation domain.	5 / 5
Completeness	Has a clear 'what' but no 'Use when…' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('recurring billing', 'invoice', 'tax calculation') but omits common synonyms such as 'subscription', 'SaaS', 'payment', and file/format cues.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (automated billing with dunning/proration) with low overlap risk, though the absence of explicit trigger phrases keeps it just short of the top anchor.	4 / 5
	Total	16 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/billing-automation/SKILL.md
Commit: 57c135b

Reviewed: 24 hours 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.