agentleFS
ParadevAIParadevAI/Paradev/.agents/skills/autumn/SKILL.md

autumn

Skill16k starsChanged 14 days agoMITView on GitHub

Change customer billing through Autumn (plans, seats, trials, free access, coupons, credits) without breaking Stripe MRR, churn, or invoices. Use for any billing write for a customer, and when asked to give someone free access, a free trial, a work trial, free months, a comped plan, or usage credits.

  • Reads credentials

5 other projects use a version of this; 1 new project in the last 4 weeks, against 0 the 4 before.

Adopted by

Surging: 1 new project took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 1 new projectWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 1 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about ParadevAI/Paradev

The biggest 5 of 53 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 53

Talked about on GitHub, Bluesky and YouTube (53 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write through Autumn,: not the Stripe Dashboard or the Stripe API.

    line 14
  2. Distinctive:

    Prefer a trial to a 100% coupon.

    line 26
  3. Distinctive:

    Create rewards in Autumn.

    line 79
  4. Very specific:

    When billing.update replaces a subscription item, Stripe MRR stops applying the subscription's discount to the new item.

    line 92

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Autumn

Autumn owns subscriptions, seats, and discounts. It writes to Stripe, and the app reads Autumn. A change made directly in Stripe leaves Autumn wrong, and Autumn's next invoice can then be wrong too.

Rules for every billing write

  1. Write through Autumn, not the Stripe Dashboard or the Stripe API.
  2. Preview first (billing.preview_attach or billing.preview_update). Show the user the amount due today, the date of the first charge, and its amount. Get a yes before you write.
  3. Read back after with customers.get: plan status, trial_ends_at, and seats.
  4. Test anything new in the sandbox (an am_sk_test_ key). The sandbox uses a different Stripe account from the workspace STRIPE_SECRET_KEY.

Seat plans: pro_v2 sells seats as the pro_seat license, team as team_seat, and ultra as ultra_seat. Legacy pro uses the seats feature. Check with plans.list for other plans.

Free access

Prefer a trial to a 100% coupon. Stripe Billing Analytics counts a trial as $0 MRR. A 100% coupon applied when the subscription is created (a promotion code at checkout) is also counted as $0, but only until a seat or plan change makes Autumn replace the subscription item. Stripe then counts the new item at full price. On 10 November 2026 this had happened to 10 subscriptions (about $2.2k MRR). Fixing them recorded the same amount as churn, and Stripe cannot remove churn from its history.

Promotion codes for Autumn rewards (the YC deal flow) are acceptable until Autumn stops replacing items; a trial is still the safer choice for anyone who will add seats.

WhoCardUse
Work trial, influencer, partner we pay, anyone we do not billNoNo-card trial
Company that should convert to paid, including YC deal companiesYesCard trial
Free usage on top of a plan (cloud GB-hours)—Usage credit

No-card trial

{
  "customer_id": "<organization id>",
  "plan_id": "team",
  "license_quantities": [{ "license_plan_id": "team_seat", "quantity": 3 }],
  "customize": {
    "free_trial": {
      "duration_length": 3,
      "duration_type": "month",
      "card_required": false,
      "on_end": "revert"
    }
  },
  "redirect_mode": "never"
}

Autumn runs this trial itself: no checkout link and no invoice, so MRR and churn do not change. Seat changes during the trial cost $0. on_end: "revert" takes them off the plan when the trial ends, and nothing is billed.

Card trial

The same request with "card_required": true, "on_end": "bill", and no redirect_mode. The response has a payment_url (Stripe Checkout). Send that link. They pay $0 today and the plan price when the trial ends.

Usage credit

Grant a balance with balances.create (feature box_gb_minutes). Do not discount the plan.

Do not

  • Do not create coupons or promotion codes in the Stripe Dashboard. Autumn does not know them, and its seat-change invoices then credit the customer at full price for seats that were free. Create rewards in Autumn.
  • Do not convert an existing paying subscription to a trial, and do not add a 100% coupon to one. Stripe records the MRR drop as churn. To give a paying customer free months, ask the user first; an invoice credit (credit note or customer balance) keeps MRR and churn true.
  • Do not add a coupon to a subscription that already exists. Stripe MRR does not recalculate, so the subscription stays counted at full price.

Known Autumn issues

Reported in #ext-autumn on 10 November 2026:

  • On subscriptions imported with billing.import, each seat change can credit earlier seat blocks again. Customers get credit they are not owed.
  • When billing.update replaces a subscription item, Stripe MRR stops applying the subscription's discount to the new item.

Not yet tested

  • Extending or shortening a trial that is already running.
  • Usage credits (balances.create) and how they show on invoices.
  • The YC deal flow still emails promotion codes for the yc-bookface-3mo-team reward (apps/api/src/app/api/integrations/yc-deals/webhook/). Moving it to a card trial is a code change in checkout.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.