CtrlK
BlogDocsLog inGet started
Tessl Logo

billing-automation

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

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 concise and reasonably structured with a useful safety note, but it stays at a high-level directive level without concrete examples and references a playbook file that is not present in the bundle. Adding executable patterns or templates and either shipping or removing the referenced file would meaningfully improve it.

Suggestions

Provide at least one concrete, copy-paste-ready example (e.g., a plan/pricing data schema, a proration calculation, or a dunning retry schedule) to lift actionability.

Convert the Instructions bullets into a numbered workflow with an explicit validate→fix→retry checkpoint around sandbox payments and ledger reconciliation.

Either add the missing 'resources/implementation-playbook.md' to the bundle or remove the dangling reference so navigation actually resolves.

DimensionReasoningScore

Conciseness

The body is lean with tight bullet lists and no padding, but the opening line restates the frontmatter description verbatim, a minor redundancy that could be trimmed.

4 / 5

Actionability

Instructions name concrete deliverables ('Define plans, pricing, billing intervals, and proration rules', 'Model taxes and compliance requirements per region') but provide no examples, schemas, or specific steps to execute them.

3 / 5

Workflow Clarity

A rough sequence is implied (define → map lifecycle → implement → model taxes → validate), and a validation step ('Validate with sandbox payments and reconcile ledger outputs') is present, but it is a bulleted list rather than an ordered workflow with explicit checkpoints and a validate→fix→retry feedback loop.

3 / 5

Progressive Disclosure

Sections are well-organized and the playbook reference is clearly signaled one level deep, but the referenced 'resources/implementation-playbook.md' does not exist among the bundle files (references/, scripts/, assets/ are empty), so navigation does not actually resolve.

3 / 5

Total

13

/

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 covers the domain comprehensively, but it omits explicit 'when to use' trigger guidance, which limits its completeness and weakens discovery. Adding a 'Use when...' clause with more natural synonyms would raise the score.

Suggestions

Add a 'Use when...' clause naming natural trigger phrases (e.g., 'Use when building SaaS subscription billing, handling failed payments, or calculating proration and taxes').

Soften jargon or add synonyms alongside 'dunning management' and 'proration' so non-specialist users can discover the skill.

Include file extensions or concrete artifacts (e.g., invoices, ledger entries) to broaden natural-term coverage.

DimensionReasoningScore

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 trigger guidance in the description itself, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Contains natural terms like 'recurring billing', 'invoice generation', and 'tax calculation', but leans on jargon ('dunning management', 'proration') and misses common synonyms such as 'subscription billing', 'SaaS billing', or 'failed payments'.

4 / 5

Distinctiveness Conflict Risk

Billing automation is a clearly delineated niche with distinct triggers; minor overlap risk only with generic payment or finance skills.

4 / 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
administrakt0r/AI-Agents-Safe-Coding-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.