CtrlK
BlogDocsLog inGet started
Tessl Logo

billing-automation

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

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/billing-automation/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The content is concise and reasonably well-structured with appropriate validation guidance for a billing skill. It is held back by actionability that relies on a missing playbook reference and a broken progressive-disclosure path.

Suggestions

Add the missing 'resources/implementation-playbook.md' (or remove the reference) so the detailed-patterns pointer resolves; this is the single biggest defect.

Tighten actionability by inlining at least one concrete artifact the body currently only names abstractly, e.g. an example subscription lifecycle state list or a default dunning retry schedule.

Make the workflow sequence explicit (numbered steps) and add an explicit 'if validation fails, fix and re-validate' feedback loop around sandbox payment validation.

DimensionReasoningScore

Conciseness

The body is lean with concise bullets and no over-explanation of billing concepts, though the opening line repeats the frontmatter description verbatim and the Limitations section has some generic boilerplate.

4 / 5

Actionability

It names specific deliverables ('Define plans, pricing, billing intervals, and proration rules'; 'Map subscription lifecycle states') but provides no concrete schemas, state names, retry strategies, or examples, and the referenced playbook that would supply them does not exist.

3 / 5

Workflow Clarity

A logical sequence is present (define -> map -> implement -> model -> validate) with explicit validation ('Validate with sandbox payments and reconcile ledger outputs'; 'Verify tax handling...before production rollout'), though steps are bulleted rather than numbered and lack an explicit fix-and-revalidate feedback loop.

4 / 5

Progressive Disclosure

Sections are well-organized and the playbook reference is clearly signaled in two places, but the referenced 'resources/implementation-playbook.md' file is not present in the bundle, breaking the overview->detail navigation promise.

3 / 5

Total

14

/

20

Passed

Description

70%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 distinctive, listing five concrete billing capabilities in a clear niche. Its main weakness is the missing 'Use when...' trigger guidance, which limits completeness.

Suggestions

Append an explicit 'Use when...' clause naming trigger phrases such as 'Use when implementing SaaS subscription billing, recurring invoices, dunning, proration, or sales tax/VAT/GST handling'.

Add common synonyms/variants users would naturally say (subscriptions, SaaS billing, VAT, GST) to broaden trigger-term coverage.

Consider action verbs ('Generate invoices', 'Recover failed payments via dunning') instead of the generic 'Master...including' framing.

DimensionReasoningScore

Specificity

Names the billing domain plus five concrete sub-capabilities ('recurring billing, invoice generation, dunning management, proration, and tax calculation'), but the verb 'Master...including' frames them as domains rather than the action-verb style of the anchor-5 example.

4 / 5

Completeness

The 'what' is clearly stated ('Master automated billing systems including...'), but there is no 'when' / 'Use when...' clause at all, which the guideline caps at 3.

3 / 5

Trigger Term Quality

Natural billing keywords are present ('recurring billing', 'invoice', 'dunning', 'proration', 'tax calculation'), but common synonyms/variants a user might say ('subscriptions', 'SaaS billing', 'VAT', 'GST') are missing.

4 / 5

Distinctiveness Conflict Risk

A clear, distinct niche (automated billing) with specific sub-domains makes it unlikely to trigger for the wrong skill.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/antigravity-awesome-skills
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.