billing-automation

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/billing-automation/SKILL.md

Quality

Content

63%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.

A well-organized, token-efficient overview with a sensible workflow shape and explicit sandbox validation, but its depth is hollow: the referenced playbook is missing and the instructions themselves contain no concrete patterns, examples, or commands. Restoring the referenced file and adding a few inline specifics would make the skill self-sufficient.

Suggestions

Create the missing 'resources/implementation-playbook.md' (or fix the path) — the body defers all templates, checklists, and examples to a file that does not exist in the bundle.

Inline a few concrete anchors, such as a minimal subscription-state model, a dunning retry schedule example, or a proration formula, so the skill is actionable even before opening the playbook.

Remove the intro line that duplicates the frontmatter description verbatim and tighten the generic Limitations boilerplate to reclaim tokens.

Dimension	Reasoning	Score
Conciseness	The body is lean bullet-based guidance with no explanation of concepts Claude already knows; the duplicated frontmatter description in the intro ('Master automated billing systems including...') and the generic Limitations boilerplate are minor instances that could be trimmed, keeping it just below the every-token-earns-its-place anchor.	4 / 5
Actionability	Instructions name concrete deliverables ('plans, pricing, billing intervals, and proration rules', 'reconcile ledger outputs') but provide no method, schema, example, or specific steps — all concrete detail is deferred to the playbook, matching the incomplete-guidance anchor rather than mostly-executable.	3 / 5
Workflow Clarity	The instructions form a clear define → map lifecycle → implement → model taxes → validate sequence with an explicit terminal validation checkpoint ('Validate with sandbox payments and reconcile ledger outputs') and a safety guard against charging real customers; it falls short of 5 because there is no error-recovery loop or per-step checkpoints, and it exceeds 3 because validation is explicit rather than missing.	4 / 5
Progressive Disclosure	The single reference to 'resources/implementation-playbook.md' is clearly signaled and one level deep, but that file does not exist anywhere in the bundle — the disclosure chain is broken, which is a real navigation failure beyond the minor organization gaps of the level-4 anchor, though the structure itself is sound.	3 / 5
	Total	14 / 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.

A specific, well-scoped description with strong domain vocabulary, but it omits any 'when to use' trigger guidance, which both caps completeness and weakens its retrieval value. Adding an explicit trigger clause with common synonyms would raise it to the top band.

Suggestions

Append an explicit trigger clause, e.g. 'Use when implementing SaaS subscription billing, setting up recurring charges, recovering failed payments, or handling proration and tax for plan changes.'

Add natural synonyms users would say, such as 'SaaS billing', 'subscriptions', 'failed payment recovery', and 'usage-based billing', to strengthen trigger term coverage.

Clarify the target environment (e.g. Stripe/Braintree-style billing systems vs. building one from scratch) to further reduce overlap with generic invoicing or tax skills.

Dimension	Reasoning	Score
Specificity	Lists five concrete, specific capabilities — 'recurring billing, invoice generation, dunning management, proration, and tax calculation' — matching the comprehensive-coverage anchor; it is not 4 because there are no meaningful gaps in the domain's action coverage.	5 / 5
Completeness	It clearly answers 'what' but contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines; it is not 2 because the 'what' is strong, and not 4 because 'when' is entirely absent rather than merely weakly implied.	3 / 5
Trigger Term Quality	Natural phrases like 'recurring billing', 'invoice', 'proration', and 'tax calculation' are terms users would actually say, but common synonyms such as 'SaaS subscriptions', 'failed payments', or 'usage-based billing' are missing, which fits the good-but-incomplete coverage anchor rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	Distinctive terms like 'dunning' and 'proration' carve a clear billing-automation niche, but 'invoice generation' and 'tax calculation' carry minor overlap risk with general invoicing or tax skills, matching the 'mostly distinct' 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: sickn33/agentic-awesome-skills
Path: skills/billing-automation/SKILL.md
Commit: 7b534bc

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