Developer Quota Credit Abuse Review

Use this skill to convert developer quota, API credit, free trial, promo credit, AI token abuse, compute/storage abuse, expensive endpoint throttling, multi-accounting, account linking, cost guardrail, and appeal questions into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

1. Identify credit sources, quota units, costly operations, developer identity, account linking signals, promo mechanics, trust tiers, abuse signals, support/appeal routes, cost exposure, and activation metrics.
2. Read references/developer-quota-credit-abuse-patterns.md.
3. Classify the situation as free trial program, promo-credit campaign, API quota launch, AI token credit, compute/storage sandbox, suspected multi-accounting, expensive endpoint abuse, or legitimate scale-up request.
4. Define quota ladder, credit ledger, trust-tier gating, fraud controls, throttling policy, reviewer queue, appeal path, cost monitoring, developer messaging, and upgrade/graduation path as public-safe policy bands, not invented numeric thresholds.
5. Define an explicit measurement matrix before final recommendations: cost, activation, conversion, abuse loss, false positives, support load, appeal outcomes, exception usage, and developer retention.
6. Produce quota and credit abuse review, state machine, decision table, event schema, control checklist, support policy, cost/activation monitoring plan, and threshold-disclosure note.

When not to use

• Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails