← Browse

@christophacham/billing-automation

A

Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recu...

skillclaude

Install

agr install @christophacham/billing-automation --target claude

Writes 1 file into .claude/skills/, pinned to git-fea77c5a.

  • .claude/skills/billing-automation/SKILL.md

Document


name: billing-automation description: "Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recu..." risk: unknown source: community date_added: "2026-02-27"

Billing Automation

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

Use this skill when

  • Implementing SaaS subscription billing
  • Automating invoice generation and delivery
  • Managing failed payment recovery (dunning)
  • Calculating prorated charges for plan changes
  • Handling sales tax, VAT, and GST
  • Processing usage-based billing
  • Managing billing cycles and renewals

Do not use this skill when

  • You only need a one-off invoice or manual billing
  • The task is unrelated to billing or subscriptions
  • You cannot change pricing, plans, or billing flows

Instructions

  • Define plans, pricing, billing intervals, and proration rules.
  • Map subscription lifecycle states and renewal/cancellation behavior.
  • Implement invoicing, payments, retries, and dunning workflows.
  • Model taxes and compliance requirements per region.
  • Validate with sandbox payments and reconcile ledger outputs.
  • If detailed templates are required, open resources/implementation-playbook.md.

Safety

  • Do not charge real customers in testing environments.
  • Verify tax handling and compliance obligations before production rollout.

Resources

  • resources/implementation-playbook.md for detailed patterns, checklists, and examples.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-fea77c5aeb892026-07-31