New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Autumn Concepts

by usenotra in usenotra/notra

Understanding Autumn's billing objects before acting on them — what a plan version is and what active means, when a trial starts or ends billing, how entity- and seat-scoped subscriptions differ…

AGPL-3.0Auto-check passedMarketing & SEO

Install Autumn Concepts

skills CLI
$ npx skills add usenotra/notra --skill autumn-concepts -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install usenotra/notra autumn-concepts --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/usenotra/notra.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/autumn-concepts .claude/skills/autumn-concepts && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
autumn-concepts
GitHub stars
260
Token cost
~1.3k tokens
SKILL.md length
383 words
Files
9 (incl. references)
Skills in repo
15
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Understanding Autumn's billing objects before acting on them — what a plan version is and what active means, when a trial starts or ends billing, how entity- and seat-scoped subscriptions differ…

  • Marketing & SEO work in your project
  • SKILL.md covers Object graph and Definitions
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Autumn Concepts is an agent skill from usenotra/notra. Understanding Autumn's billing objects before acting on them — what a plan version is and what active means, when a trial starts or ends billing, how entity- and seat-scoped subscriptions differ from the customer's own, what a customize diff actually changes, and how caps, overage, and top-ups behave. Load before versioning, editing, or drafting a plan, or when a customer's state does not match the plain reading of their plan.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `references/billing-controls.md`, `references/customer-entity.md` and `references/customize.md`).

It sits in Marketing & SEO. It works with Stripe. The repository describes itself as: Notra is a modern GEO tool that asks ChatGPT, Claude and Gemini the questions your buyers ask. See if you show up, who shows up instead and how to fix it. The licence is AGPL-3.0.

When your agent uses it

  • Marketing & SEO work in your project

Example prompts

  • “/autumn-concepts”

What it can do on your machine

Read from SKILL.md and the folder at commit dceb2a7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Autumn Concepts loads about 1.3k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 112 tokens; SKILL.md has 383 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~112
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from usenotra/notra at commit dceb2a7, republished under its AGPL-3.0 licence (© usenotra). 383 words, ~1,253 tokens.

Download SKILL.mdSave it as .claude/skills/autumn-concepts/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
autumn-concepts
description
Understanding Autumn's billing objects before acting on them — what a plan version is and what active means, when a trial starts or ends billing, how entity- and seat-scoped subscriptions differ from the customer's own, what a customize diff actually changes, and how caps, overage, and top-ups behave. Load before versioning, editing, or drafting a plan, or when a customer's state does not match the plain reading of their plan.

Concepts

Autumn is a database for your application billing state: features, plans, customers, subscriptions, purchases, balances, flags, and billing controls. It helps you iterate on pricing, manage credit access and usage, control overage, and keep billing behavior connected to product access.

Autumn is a layer above Stripe; Stripe still handles subscription management, invoicing, and payment processing. Autumn provisions and updates Stripe subscriptions, schedules, invoices, and related billing objects for you.

Object graph

txt
Organization
- features[] -> Feature
- plans[] -> Plan
- customers[] -> Customer

Configuration model:
Feature
- referenced by -> Plan Item
- credit_system type: maps actions to credit costs (flat or tiered)

Plan
- items[] -> Plan Item
  - feature_id -> Feature
  - optional price -> usage_based or prepaid feature price
- price -> base recurring or one-off price
- versions[] -> parallel definitions of this plan; ONE is active
- variants[] -> Plan (a derived plan storing only its differences)
- licenses[] -> Plan (a seat plan this plan hands out per seat)
- aliases -> old plan ids that still resolve after a rename

Plan Item
- feature_id -> Feature
- optional price -> usage_based or prepaid feature price
- pooled? -> entity grants combine into one shared customer balance

Runtime model:
Customer
- subscriptions[] -> Subscription -> Plan (a specific version of it)
- purchases[] -> Purchase -> Plan
- balances[feature_id] -> Balance -> Feature
  - pooled balance: fed by entity grants, spent by any entity
  - rollover, expiry, usage windows live here
- licenses[] -> CustomerLicense -> seats granted / in use / remaining
- flags[feature_id] -> Flag -> Feature
- billing_controls -> customer-level usage controls
- entities[] -> Entity -> same runtime shape scoped under Customer

Entity
- belongs to -> Customer
- subscriptions[] -> Subscription -> Plan
- purchases[] -> Purchase -> Plan
- balances[feature_id] -> Balance -> Feature
- flags[feature_id] -> Flag -> Feature
- license assignment -> holds one seat from the customer's pool

From config to customer state:
Plan + Customer --billing.attach--> Subscription or Purchase
Plan + Customer + entity_id --billing.attach--> Entity-scoped Subscription or Purchase
Parent plan's licenses --licenses.attach--> seat assigned to an Entity
Subscription/Purchase -> Balance or Flag provisioning

Two relationships changed recently — worth stating plainly because older docs describe the old way:

Versions are groups of customers, not history. A plan's versions used to be numbered steps in time, and the newest was always live. Now each version is a definition that some group of customers lives on, and exactly one is active — the one attach uses when no version is named. Which changes are edits and which are new versions, drafts, and how customers move: the plan definition below.

Plans connect to other plans. A plan can have variants (an annual twin storing only its differences), and it can offer licenses (a small seat plan it hands out per seat). So plans form a graph, not a flat list.

Use these definitions as the mental model when designing or changing Autumn pricing. Reason in terms of features, plans, plan items, customers/entities, and billing controls before writing any config or calling the API — most modeling mistakes come from conflating a feature with a plan item, or a plan-level price with a per-feature price.

Show full SKILL.md (136 more words)Show less

Definitions

Load the matching definition when reasoning about that object.

For defining a feature — the atomic unit Autumn gates, tracks, or bills, and its types, read references/feature.md.

For defining a plan — the attachable package of items and pricing, read references/plan.md.

For modeling plan items, or when you need concrete API request-body examples (included usage, prepaid, usage-based, tiers), read references/plan-items.md.

For using customize, reading plan update previews, or representing a small diff from a base plan, read references/customize.md.

For reasoning about free trials and when billing begins, read references/trials.md.

For distinguishing a customer from an entity (seats, sub-accounts) and their runtime billing state, read references/customer-entity.md.

For reasoning about billing controls — runtime caps, alerts, overage, and top-ups, read references/billing-controls.md.

For reasoning about licenses — seat plans a parent plan hands out, seat pools, assigning and releasing seats, read references/licenses.md.

© usenotra, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (references) in .agents/skills/autumn-concepts of usenotra/notra.

  • SKILL.md
  • references/billing-controls.md
  • references/customer-entity.md
  • references/customize.md
  • references/feature.md
  • references/licenses.md
  • references/plan-items.md
  • references/plan.md
  • references/trials.md

Open the folder on GitHubat commit dceb2a7

Compare with similar skills

Autumn Concepts next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Autumn Concepts compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Autumn Concepts this skillusenotra/notra260—~1.3kAutomated safety check: PassAGPL-3.0
Rankupyan-labs/yan-skills213—~5.1kAutomated safety check: NotesMIT
Illustration One LineMengTo/Skills6.7k—~5kAutomated safety check: PassMIT
Afa Paymentsafadtc/afa-dtc-skills168—~1.2kAutomated safety check: PassCustom licence
Mvp Launchooiyeefei/ccc495—~1.1kAutomated safety check: PassMIT
Monetizationsickn33/agentic-awesome-skills47k2 repos~3kAutomated safety check: PassMIT

Similar skills

  • Rankup

    yan-labs/yan-skills

    独立开发者的项目全生命周期管理：需求验证、选词选品、建站或做原生 App、上线接入、SEO/GEO 获客、支付变现、监控迭代与跨会话接力。以下情况使用：用户提到 rankup 或 /rankup（check、review、init；doctor 仅指整理项目 .rankup 记录）；当前目录或工作区有…

    213 GitHub stars~5.1k tokensUpdated today
    Marketing & SEOAuto-check: notes

  • Illustration One Line

    MengTo/Skills

    Draws original hand-written SVG spot illustrations in the One-line style, joyful action figures doing design and coding work.

    6.7k GitHub stars~5k tokensUpdated 4 days ago
    Marketing & SEOAuto-check passed

  • Afa Payments

    afadtc/afa-dtc-skills

    DTC 支付风控与争议率——VAMP 自查、chargeback 反驳、Stripe/PayPal 冻结应对、支付组合、欺诈过滤。触发词: 争议率, chargeback, 拒付, VAMP, Stripe 冻结, PayPal 冻结, Rolling Reserve, 3DS, BNPL, dispute rate, frozen account, Stripe, PayPal。复杂问题先经…

    168 GitHub stars~1.2k tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed

  • Mvp Launch

    ooiyeefei/ccc

    Web app MVP launch checklist knowledge. An agent skill from ooiyeefei/ccc.

    495 GitHub stars~1.1k tokensUpdated 2 mo ago
    Marketing & SEOAuto-check passed

  • Monetization

    sickn33/agentic-awesome-skills

    Estrategia e implementacao de monetizacao para produtos digitais - Stripe, subscriptions, pricing experiments, freemium, upgrade flows, churn prevention, revenue optimization e modelos de negocio…

    47k GitHub starsUsed in 2 repos~3k tokens
    Sales & SupportAuto-check passed

  • Odoo Ecommerce Configurator

    sickn33/agentic-awesome-skills

    Expert guide for Odoo eCommerce and Website: product catalog, payment providers, shipping methods, SEO, and order-to-fulfillment workflow.

    47k GitHub starsUsed in 2 repos~1.3k tokens
    Sales & SupportAuto-check passed

More from usenotra/notra

All 15 skills in this repo

  • Ponytail Help

    usenotra/notra

    Quick-reference card for all ponytail modes, skills, and commands.

    260 GitHub starsUsed in 3 repos~697 tokens
    Auto-check passed

  • Neon Postgres

    usenotra/notra

    Guides and best practices for working with Lakebase Postgres, the database behind Neon.

    260 GitHub stars~4.1k tokensUpdated today
    Auto-check: notes

  • Satori

    usenotra/notra

    Expert guidance for Satori, the library that converts JSX/HTML and CSS into SVG (the engine behind dynamic Open Graph images and social cards).

    260 GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Workos Widgets

    usenotra/notra

    A skill your agent uses when the user is implementing, embedding, or debugging a WorkOS Widget — specifically the User Management, User Profile, Admin Portal SSO Connection, or Admin Portal Domain…

    260 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Autumn Catalog

    usenotra/notra

    Modeling a user's pricing into an Autumn catalog — deciding the structure (plans, variants, add-ons, licenses, credit systems, pooled balances) before writing config, then filling in the numbers.

    260 GitHub stars~6.1k tokensUpdated today
    Auto-check passed

  • Code Organization

    usenotra/notra

    Repo file-organization convention for TypeScript projects. An agent skill from usenotra/notra.

    260 GitHub stars~893 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Autumn Concepts

What does Autumn Concepts do?

Understanding Autumn's billing objects before acting on them — what a plan version is and what active means, when a trial starts or ends billing, how entity- and seat-scoped subscriptions differ…. Autumn Concepts is an agent skill from usenotra/notra. Understanding Autumn's billing objects before acting on them — what a plan version is and what active means, when a trial starts or ends billing, how entity- and seat-scoped subscriptions differ from the customer's own, what a customize diff actually changes, and how caps, overage, and top-ups behave.

When should I use Autumn Concepts?

Autumn Concepts fits situations like: marketing & SEO work in your project.

How do I install Autumn Concepts in Claude Code?

Run `npx skills add usenotra/notra --skill autumn-concepts -a claude-code`. Or copy the skill folder (.agents/skills/autumn-concepts in usenotra/notra) into .claude/skills/autumn-concepts in your project. Claude Code loads it when a task matches its description.

How do I install Autumn Concepts in Codex?

Run `npx skills add usenotra/notra --skill autumn-concepts -a codex`. Or copy the skill folder (.agents/skills/autumn-concepts in usenotra/notra) into .agents/skills/autumn-concepts in your project. Codex loads it when a task matches its description.

Can I use Autumn Concepts in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add usenotra/notra --skill autumn-concepts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/autumn-concepts, .gemini/skills/autumn-concepts, .github/skills/autumn-concepts and .opencode/skills/autumn-concepts in your project.

What does Autumn Concepts need to run?

SKILL.md names no scripts, command-line tools or credentials: Autumn Concepts is instructions for the agent only.

Does Autumn Concepts access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Autumn Concepts safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Autumn Concepts use?

Autumn Concepts is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Autumn Concepts use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 10k tokens, read only when the agent opens those files.

What are the alternatives to Autumn Concepts?

Skills that share tags, products or a category with Autumn Concepts: Rankup (yan-labs/yan-skills, 213 stars), Illustration One Line (MengTo/Skills, 6.7k stars), Afa Payments (afadtc/afa-dtc-skills, 168 stars) and Mvp Launch (ooiyeefei/ccc, 495 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Autumn Concepts?

usenotra (a GitHub organization) maintains it in usenotra/notra, which has 260 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 11, 2026.

Source: usenotra/notra on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.