Unnamed Skill
Quota tracking, threshold monitoring, and graceful degradation for rate-limited API services.Triggers: quota, rate limiting, usage limits, thresholdsUse when: integrating rate-limited services or tracking API usage
$ 安裝
git clone https://github.com/athola/claude-night-market /tmp/claude-night-market && cp -r /tmp/claude-night-market/plugins/leyline/skills/quota-management ~/.claude/skills/claude-night-market// tip: Run this command in your terminal to install the skill
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
- Overview
- When to Use
- Core Concepts
- Quota Thresholds
- Quota Types
- Quick Start
- Check Quota Status
- Record Usage
- Estimate Before Execution
- Integration Pattern
- Detailed Resources
- Exit Criteria
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:
- Initialize tracker for your service
- Check quota before operations
- Record usage after operations
- Handle threshold warnings gracefully
Detailed Resources
- Threshold Strategies: See
modules/threshold-strategies.mdfor degradation patterns - Estimation Patterns: See
modules/estimation-patterns.mdfor 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
Repository
