Skill: athola/nm-leyline-quota-management (version 1.0.2)

--- name: quota-management description: | 'Quota tracking, threshold monitoring, and graceful degradation for rate-limited API services. quota, rate limiting, usage limits, thresholds.' version: 1.9.5 triggers: - quota - rate-limiting - resource-management - cost-tracking - thresholds metadata: {"openclaw": {"homepage": "https://github.com/athola/claude-night-market/tree/master/plugins/leyline", "emoji": "\ud83e\udd9e"}} source: claude-night-market source_plugin: leyline --- > **Night Market Skill** — ported from [claude-night-market/leyline](https://github.com/athola/claude-night-market/tree/master/plugins/leyline). For the full experience with agents, hooks, and commands, install the Claude Code plugin. ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Core Concepts](#core-concepts) - [Quota Thresholds](#quota-thresholds) - [Quota Types](#quota-types) - [Quick Start](#quick-start) - [Check Quota Status](#check-quota-status) - [Record Usage](#record-usage) - [Estimate Before Execution](#estimate-before-execution) - [Integration Pattern](#integration-pattern) - [Detailed Resources](#detailed-resources) - [Exit Criteria](#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 ## When NOT To Use - Project doesn't use the leyline infrastructure patterns - Simple scripts without service architecture needs ## 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 ```python @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 ```python 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 ```python tracker.record_request( tokens=estimated_tokens, success=True, duration=elapsed_seconds ) ``` ### Estimate Before Execution ```python 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: ```yaml # 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


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)