quota-management

athola 的头像作者 athola

速率限制服务的通用配额跟踪和执行模式。提供阈值监控、估计和优雅降级策略。触发条件:配额跟踪、速率限制、使用限制、成本跟踪、阈值、资源管理、API配额、使用监控。使用场景:集成速率限制服务、跟踪API使用成本、实现优雅降级、监控资源消耗。不要使用:服务没有速率限制或配额问题。管理外部服务集成配额时咨询此技能。

📖 中文导读:速率限制服务的通用配额跟踪和执行模式。提供阈值监控、估计和优雅降级策略。触发条件:配额跟踪、速率限制、使用限制、成本跟踪、阈值、资源管理、API配额、使用监控。使用场景:集成速率限制服务、跟踪API使用成本、实现优雅降级、监控资源消耗。不要使用:服务没有速率限制或配额问题。管理外部服务集成配额时咨询此技能。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。

name: quota-management description: |

Triggers: quota, management, rate-limiting, thresholds, cost-tracking Quota tracking, threshold monitoring, and graceful degradation for rate-limited API services.

Triggers: quota, rate limiting, usage limits, thresholds Use when: integrating rate-limited services or tracking API usage category: infrastructure tags: [quota, rate-limiting, resource-management, cost-tracking, thresholds] dependencies: [] tools: [quota-tracker] provides: infrastructure: [quota-tracking, threshold-monitoring, usage-estimation] patterns: [graceful-degradation, quota-enforcement, cost-optimization] usage_patterns: - service-integration - rate-limit-management - cost-tracking - resource-monitoring complexity: intermediate estimated_tokens: 500 progressive_loading: true modules: - modules/threshold-strategies.md - modules/estimation-patterns.md

Table of Contents

Quota Management

Overview

Patterns for tracking and enforcing resource quotas across rate-limited services. This skill provides the infrastructure that other plugins use for consistent quota handling.

When to Use

  • Building integrations with rate-limited APIs
  • Need to track usage across sessions
  • Want graceful degradation when limits approached
  • Require cost estimation before operations

Core Concepts

Quota Thresholds

Three-tier threshold system for proactive management:

Level Usage Action
Healthy <80% Proceed normally
Warning 80-95% Alert, consider batching
Critical >95% Defer non-urgent, use secondary services

Quota Types

@dataclass
class QuotaConfig:
    requests_per_minute: int = 60
    requests_per_day: int = 1000
    tokens_per_minute: int = 100000
    tokens_per_day: int = 1000000

Quick Start

Check Quota Status

from leyline.quota_tracker import QuotaTracker

tracker = QuotaTracker(service="my-service")
status, warnings = tracker.get_quota_status()

if status == "CRITICAL":
    # Defer or use secondary service
    pass

Record Usage

tracker.record_request(
    tokens=estimated_tokens,
    success=True,
    duration=elapsed_seconds
)

Estimate Before Execution

can_proceed, issues = tracker.can_handle_task(estimated_tokens)
if not can_proceed:
    print(f"Quota issues: {issues}")

Integration Pattern

Other plugins reference this skill:

# In your skill's frontmatter
dependencies: [leyline:quota-management]

Then use the shared patterns:

  1. Initialize tracker for your service
  2. Check quota before operations
  3. Record usage after operations
  4. Handle threshold warnings gracefully

Detailed Resources

  • Threshold Strategies: See modules/threshold-strategies.md for degradation patterns
  • Estimation Patterns: See modules/estimation-patterns.md for token/cost estimation

Exit Criteria

  • Quota status checked before operation
  • Usage recorded after operation
  • Threshold warnings handled appropriately

Troubleshooting

Common Issues

Command not found Ensure all dependencies are installed and in PATH

Permission errors Check file permissions and run with appropriate privileges

Unexpected behavior Enable verbose logging with --verbose flag