mcpField
A
api-rate-limit-quota-review

api-rate-limit-quota-review

github.com/sylphxaiDevelopment144 installsUpdated today
Repository

About api-rate-limit-quota-review

A skill for turning API rate-limit and quota questions into an implementation-oriented review, with decisions, owners, metrics, and recovery paths. It guides API teams through defining limits and the developer-facing contract.

Key features

  1. 01Classify limits, quotas, and gates
  2. 02Define units, headers, and errors
  3. 03Plan dashboards and alerts
  4. 04Generate decision tables and schemas
  5. 05Include migration and support paths

Use cases

  1. 01Design limits for a new API
  2. 02Review 429 responses and retry guidance
  3. 03Plan quota changes for existing developers

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill api-rate-limit-quota-review

After installing, type/api-rate-limit-quota-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/api-rate-limit-quota-patterns.md

Details

From the project README

API Rate Limit Quota Review

Use this skill to convert a API quotas, rate limits, fair use, developer experience, billing alignment, and abuse controls question into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify API consumer, authentication principal, endpoint cost, criticality, tenant blast radius, pricing tier, and abuse pattern.
  2. Read references/api-rate-limit-quota-patterns.md.
  3. Separate rate limit, quota, concurrency cap, payload cap, spend cap, fair-use review, and entitlement gate.
  4. Define limit units, headers, error shape, retry/backoff, dashboards, alerts, upgrade path, support override, and migration policy.
  5. Produce quota model, state machine, endpoint decision table, event schema, and developer communication checklist.

When not to use

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

Guardrails

  • Do not use a single global limit when endpoint cost, tenant size, and abuse risk differ materially.
  • Do not return vague 429s without stable headers, retry guidance, documentation, and observability.
  • Do not let quota bypass billing, entitlement, security, or tenant isolation controls.
  • Do not silently change limits for existing developers without migration notice and support path.

Output format

API context:
Principal / endpoint cost / tenant blast radius:

Limit and quota plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Developer contract:
- <item> -> <policy, metric, edge case, support note>

Override and migration policy:
- <trigger> -> <action, communication, owner>

Comments

Markdown supported