autumn-catalog

Designs and updates Autumn pricing catalogs with features, plans, plan items, and billing models.

2.7k|244|Updated Jan 21, 2025
One-click install
npx skills add https://github.com/useautumn/autumn --skill autumn-catalog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autumn-catalog
Source: https://github.com/useautumn/autumn/tree/main/packages/agent-docs/generated/skills/autumn-catalog
Command: npx skills add https://github.com/useautumn/autumn --skill autumn-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Translating a pricing idea into Autumn's data model of features, plans, and plan items is error-prone: choosing between prepaid and usage-based billing, handling plan versioning, variant propagation, and customer migrations all require careful decisions. This Skill guides an AI agent through modeling and safely updating an Autumn pricing catalog via autumn.config.ts, the atmn CLI, or MCP/API tools.

Core Features & Use Cases

  • Pricing Model Design: Translate pricing intent into features, plans, and plan items covering subscriptions, credits, seats, overage, prepaid, volume tiers, free plans, one-off purchases, and trials.
  • Safe Catalog Updates: Follow a preview-decision-apply loop using catalog.preview_update or atmn headless push, surfacing versioning choices, variant propagation, and migration drafts before any write.
  • atmn CLI Workflows: Manage code-defined catalogs in autumn.config.ts with headless push/pull flows and explicit decision flags for plan intents and migrations.
  • Use Case: A startup wants to charge $20/month plus $1 per 1,000 API calls over a 10,000 included allowance. The Skill models a metered consumable feature with a usage-based plan item, previews the catalog change, and applies it after confirmation.

Quick Start

Ask the agent to design an Autumn pricing plan with a monthly base fee and usage-based overage for your API product.

Frequently Asked Questions about autumn-catalog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I model usage-based pricing in Autumn?

Create a metered consumable feature and add it to a plan item with a usage_based billing method, an amount per billing unit, and an optional included allowance. Usage beyond the included amount is billed as overage at the end of the billing period.

How do I update an Autumn plan that already has customers?

Run catalog.preview_update or atmn --headless push first, then choose a versioning strategy: create a new version to grandfather customers, update the current version with disable_version, or update all versions. Optionally create a migration draft to move existing customers.

What is the difference between prepaid and usage-based billing in Autumn?

Prepaid charges upfront for a quantity the customer selects at purchase via feature_quantities, decrementing the balance as usage occurs. Usage-based tracks consumption during the cycle and bills actual usage at period end.

When should I use atmn versus the Autumn API for catalog changes?

Use atmn when the project has or should have an autumn.config.ts source of truth for code-managed catalogs. Use MCP/API tools directly for dashboard-first workflows or when no local config exists.

Can a free plan in Autumn have paid prices?

No. A default or auto-enabled plan must have a null base price and its items must not contain paid prepaid or usage-based prices. Free plans use autoEnable to grant every new customer access automatically.