Skills billing-automation

📦

billing-automation

Name: billing-automation
Author: sickn33

Content revision r2 Safe 🌐 Network access⚙️ External commands

Automate Subscription Billing Workflows

Subscription billing requires coordinated lifecycle, payment, invoice, tax, and recovery rules. This skill provides practical patterns for designing and validating those workflows.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "billing-automation" from https://skillstore.io/skills/sickn33-billing-automation.md and its manifest at https://skillstore.io/api/skills/sickn33-billing-automation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-billing-automation.md Signed manifest GET /api/skills/sickn33-billing-automation/manifest Signed lockfile GET /api/skills/sickn33-billing-automation/lockfile

Test it

Using "billing-automation". Design failed-payment recovery for a monthly team plan.

Expected outcome:

Day 0: Mark the invoice past due and notify the billing contact.
Day 3: Retry payment and provide a secure payment-update link.
Day 7: Retry again and warn about upcoming account restrictions.
Day 14: Make the final attempt, then apply the documented cancellation policy.

Using "billing-automation". Explain an upgrade from a monthly basic plan to a pro plan halfway through the cycle.

Expected outcome:

Credit the unused basic-plan period, charge the remaining pro-plan period, and show both adjustments on the invoice. Test rounding and timezone boundaries.

Using "billing-automation". Review a usage-based billing rollout.

Expected outcome:

Define each billable metric and its source of truth.
Prevent duplicate usage events with stable identifiers.
Close metering periods before invoice finalization.
Reconcile aggregated usage against source events before charging customers.

Security Audit

Safe

v5 • 8/14/2026 Open versioned report

All eight static findings are false positives in documentation and illustrative code. No prompt injection, malicious intent, command execution, reconnaissance, or unsafe network destination was found.

Files scanned

596

Lines analyzed

Review items

False positives ignored

Risk Factors

🌐 Network access (1)

resources/implementation-playbook.md:256

⚙️ External commands (2)

SKILL.md:36 SKILL.md:45

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-billing-automation/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-billing-automation/security.svg)](https://skillstore.io/skills/sickn33-billing-automation?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-billing-automation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-billing-automation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-billing-automation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). billing-automation security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-billing-automation/audits/5

BibTeX citation

@techreport{sickn33-sickn33-billing-automation-2026,
  author = {sickn33},
  title = {billing-automation security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/sickn33-billing-automation/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "billing-automation security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-08-14"
url: "https://skillstore.io/skills/sickn33-billing-automation/audits/5"
identifiers:
  - type: other
    value: "skillstore:sickn33-billing-automation:audit:5"
    description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

sickn33 Recommended Current

sickn33-billing-automation

Skillstore Score 78

Evidence Confidence High

Skillstore usage 11

Updated

2026-08-21

wshobson

wshobson-billing-automation

Skillstore Score 77

Evidence Confidence High

Skillstore usage 14

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Launch SaaS Subscriptions

Define plans, lifecycle states, invoices, renewals, and payment behavior for a new subscription product.

Improve Payment Recovery

Create balanced retry schedules, notices, grace periods, and account restrictions for failed payments.

Review Billing Architecture

Assess proration, usage metering, taxes, audit trails, and reconciliation before production rollout.

Try These Prompts

Define a Basic Billing Plan

Design a monthly subscription plan for [product]. Include price, trial length, renewal timing, cancellation behavior, and invoice timing.

Map the Subscription Lifecycle

Map lifecycle states for [product]. Define allowed transitions, triggers, customer notifications, payment effects, and recovery actions for each state.

Design Dunning and Proration

Create dunning and proration rules for [plans]. Include retry timing, grace periods, upgrades, downgrades, seat changes, credits, and test cases.

Audit a Billing Architecture

Review this billing design: [design]. Identify lifecycle gaps, duplicate-charge risks, tax assumptions, reconciliation needs, failure modes, and sandbox validation steps.

Best Practices

Use idempotency controls and durable audit records for every charge, invoice, retry, and subscription transition.
Validate payment flows with sandbox data and reconcile invoices against ledger outputs before release.
Confirm tax, privacy, and notification obligations for every supported region.

Avoid

Do not test billing logic by charging real customers.
Do not hardcode tax rates, billing dates, or retry rules without controlled configuration and review.
Do not finalize invoices before validating usage, proration, discounts, tax, and payment state.

Frequently Asked Questions

Does this skill connect to a payment provider?

No. It provides design patterns and examples that you must adapt to your selected provider.

Can it calculate proration?

It provides formulas and examples for plan and seat changes. You must validate rounding, credits, dates, and provider behavior.

Does it support usage-based billing?

Yes. It covers usage tracking and tiered, per-unit, and volume pricing at an implementation-pattern level.

Can I rely on the included tax rates?

No. The rates are examples and are not complete or current tax advice.

How should failed payments be handled?

Define retry timing, notices, grace periods, restrictions, recovery actions, and cancellation rules that match your customer policy.

What validation is required before production?

Test lifecycle transitions, duplicate prevention, rounding, timezones, retries, taxes, invoice delivery, and ledger reconciliation in a sandbox.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/billing-automation

Ref

5a26d1d61d694db29af9b138c661c1981076d9df

Maintenance freshness

8/15/2026

Usage

10 downloads · 112 views

File structure

📁 resources/

📄 implementation-playbook.md

📄 SKILL.md