Skills billing-automation
💳

billing-automation

Safe 🌐 Network access⚙️ External commands

Automate subscription billing workflows

Recurring billing systems are complex to design and maintain. This skill provides clear patterns for subscriptions, invoicing, dunning, proration, and taxes.

Supports: Claude Codex Code(CC)
📊 69 Adequate
1

Download the skill ZIP

2

Upload in Claude

Go to Settings → Capabilities → Skills → Upload skill

3

Toggle on and start using

Test it

Using "billing-automation". Create a billing cycle workflow for monthly subscriptions with dunning.

Expected outcome:

  • Check if billing period ended and generate invoice
  • Attempt payment and mark invoice paid on success
  • On failure, mark past due and start retry schedule
  • Send notifications and cancel after final retry

Using "billing-automation". How do I calculate proration when a customer upgrades mid-month?

Expected outcome:

  • Calculate days used on current plan
  • Calculate remaining days in billing period
  • Credit unused portion of old plan
  • Charge prorated amount for new plan
  • Apply net difference to next invoice

Using "billing-automation". What tax rates apply to EU customers versus US customers?

Expected outcome:

  • EU: VAT rates by country (GB 20%, DE 19%, FR 20%)
  • US: State-level sales tax (CA 7.25%, NY 4%)
  • AU: GST at 10%
  • Non-listed regions: No tax calculation

Security Audit

Safe
v4 • 1/17/2026

Pure documentation skill containing only SKILL.md with billing patterns and sample code. No executable scripts, file system access, environment variable reading, or actual network calls. All 47 static findings are false positives: markdown code block backticks misidentified as Ruby execution, basic arithmetic misidentified as weak crypto, placeholder URLs in templates, and billing state management misidentified as reconnaissance.

2
Files scanned
737
Lines analyzed
2
findings
4
Total audits

Risk Factors

🌐 Network access (2)
skill-report.json:6 SKILL.md:271
⚙️ External commands (17)
SKILL.md:31-34 SKILL.md:34-51 SKILL.md:51-67 SKILL.md:67-71 SKILL.md:71-127 SKILL.md:127-131 SKILL.md:131-206 SKILL.md:206-210 SKILL.md:210-279 SKILL.md:279-283 SKILL.md:283-329 SKILL.md:329-333 SKILL.md:333-398 SKILL.md:398-402 SKILL.md:402-477 SKILL.md:477-481 SKILL.md:481-530
Audited by: claude View Audit History →

Quality Score

38
Architecture
100
Maintainability
85
Content
22
Community
100
Security
87
Spec Compliance

What You Can Build

Launch subscriptions

Set up basic subscription billing, trials, and renewals for a new product.

Improve dunning

Design a retry schedule and notifications for failed payments.

Model proration

Estimate credits and charges for mid-cycle plan changes.

Try These Prompts

Start subscription flow 
Design a subscription lifecycle with trial, active, past due, and canceled states. Include key transitions and required data fields.
Invoice generation plan 
Outline invoice generation steps with line items, tax, and totals. Include data inputs and validation checks.
Dunning retry schedule 
Propose a dunning schedule with retries and email notifications. Explain how to handle recovery and cancellation.
Usage based billing 
Describe how to track usage events and calculate tiered pricing charges for a billing period.

Best Practices

  • Keep an audit trail of billing events
  • Notify customers at each billing change
  • Validate tax rules by jurisdiction

Avoid

  • Hardcoding billing dates and intervals
  • Canceling after a single failed payment
  • Skipping proration when plans change mid-cycle

Frequently Asked Questions

Is this compatible with Claude, Codex, and Claude Code?
Yes, the guidance is platform neutral and works in Claude, Codex, and Claude Code.
What are the limits of the provided code?
It is sample logic and does not include storage, job scheduling, or full production error handling.
Can I integrate it with Stripe or other processors?
Yes, the examples show where processor calls fit, but you must add real SDK calls and auth.
Does it access or store sensitive data?
No, the skill is documentation and code patterns only. It does not read local files.
What if my billing cycle is custom?
Adjust the billing cycle calculation and proration logic to match your custom schedule.
How does it compare to a full billing platform?
It provides architecture and logic patterns, not a hosted billing service or turnkey UI.

Developer Details

Author

wshobson

License

MIT

Repository

https://github.com/wshobson/agents/tree/main/plugins/payment-processing/skills/billing-automation

Ref

main

File structure

📄 SKILL.md