credits-handler

Allocate, purchase, and track user credits with idempotent transactions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/alisonbessa/bluemoon --skill credits-handler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: credits-handler
Source: https://github.com/alisonbessa/bluemoon/tree/main/.claude/skills/credits-handler
Command: npx skills add https://github.com/alisonbessa/bluemoon --skill credits-handler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill centralizes and automates the management of a flexible credit system, enabling teams to configure, allocate, purchase, and track credits across users and plans.

Core Features & Use Cases

  • Backend configuration for credit types and pricing
  • Frontend UI hooks to display balances and enable purchases
  • Safe, idempotent balance mutations with auditable transactions
  • Real-world scenario: a user upgrades to a higher plan and automatically gains allocated credits

Quick Start

Configure a new credit type in the config, then wire the UI and backend flows to support allocation, purchase, and usage.

Frequently Asked Questions about credits-handler

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

FAQPage Schema
How do I allocate and track user credits across different pricing plans?

You can allocate and track user credits by configuring credit types in the backend, wiring frontend UI hooks to display balances, and enforcing safe, idempotent balance mutations with auditable transactions for plan-based allocations.

How do I implement safe credit purchases and balance mutations in a web application?

Safe credit purchases and balance mutations are implemented through idempotent transaction logic and type-safe backend configurations, ensuring balance changes are auditable and preventing duplicate or unsafe modifications to user credit balances.

What is the best way to display user credit balances and enable purchases on the frontend?

Displaying user credit balances and enabling purchases on the frontend is handled via dedicated UI hooks integrated with backend pricing configurations, supporting real-time balance updates and seamless plan-based credit allocation transactions.

Can I configure custom credit types and pricing rules for different subscription plans?

Yes, you can configure custom credit types and pricing rules by defining type-safe backend configurations, allowing flexible allocation and transaction logic tailored to specific subscription plan requirements and credit purchases.

Why do I need idempotent transactions for credit allocation and usage tracking?

Idempotent transactions are required for credit allocation to prevent duplicate balance mutations during retries or errors, ensuring safe, auditable tracking of user credit usage and purchases across the application.

Does this credits-handler skill support automated credit allocation when a user upgrades their plan?

Yes, it supports automated credit allocation when a user upgrades by applying backend configuration and pricing rules, automatically granting allocated credits and recording the transaction through safe, auditable helper utilities.