autumn-add-usage-tracking

Implement Autumn check-then-track flows for backend feature gating and usage metering.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MichaelFrieze/riffatlas --skill autumn-add-usage-tracking-michaelfrieze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autumn-add-usage-tracking
Source: https://github.com/MichaelFrieze/riffatlas/tree/main/.agents/skills/autumn-add-usage-tracking
Command: npx skills add https://github.com/MichaelFrieze/riffatlas --skill autumn-add-usage-tracking-michaelfrieze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you enforce plan-based limits and accurately measure feature consumption so customers can access capabilities only when allowed.

Core Features & Use Cases

  • Feature gating with security checks: Performs an Autumn check to determine whether a customer is allowed, along with balance, included_usage, and unlimited status.
  • Deterministic usage tracking: Records consumption using Autumn track after successful work so billing/limits reflect real usage.
  • Support for multiple feature types: Handles boolean, metered, and credit_system behaviors correctly.
  • Credit system correctness: Ensures you track the underlying metered feature (e.g., image_gen) rather than the credit pool (e.g., credits).

Quick Start

Implement a backend flow that calls Autumn check before the action, runs the protected work only when allowed is true, and then calls Autumn track after success using the correct customer_id, feature_id, and value.

Frequently Asked Questions about autumn-add-usage-tracking

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

FAQPage Schema
How do I implement feature gating and usage tracking with Autumn?

Feature gating with Autumn requires a backend flow that calls the Autumn `check` API before a protected action, executes the work only if `allowed` is true, and then calls Autumn `track` after successful completion to record usage.

What's the best way to track credit system usage without overbilling?

To track credit system usage correctly, you must call Autumn `track` on the underlying metered feature, such as `image_gen`, rather than tracking the credit pool itself to ensure billing limits reflect real consumption.

When should I use server-side usage metering instead of frontend checks?

Server-side usage metering is necessary for backend-protected actions where the frontend cannot be trusted, ensuring usage is recorded only after the successful completion of the protected work.

Does Autumn usage tracking support boolean, metered, and credit features?

Autumn usage tracking supports multiple feature types, correctly handling `boolean`, `metered`, and `credit_system` behaviors to gate features and measure consumption based on customer plans.

Why does my Autumn track call fail idempotency checks?

Idempotency in Autumn usage tracking requires calling `check` before the action and `track` after success using the correct `customer_id`, `feature_id`, and `value` to ensure deterministic usage recording.