From databricks-pack
Implement Databricks API rate limiting, backoff, and idempotency patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Databricks. Trigger with phrases like "databricks rate limit", "databricks throttling", "databricks 429", "databricks retry", "databricks backoff".
How this skill is triggered — by the user, by Claude, or both
Slash command
/databricks-pack:databricks-rate-limitsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Handle Databricks API rate limits gracefully with exponential backoff.
Handle Databricks API rate limits gracefully with exponential backoff.
For full implementation details and code examples, load:
references/implementation-guide.md
| Scenario | Behavior | Configuration |
|---|---|---|
| HTTP 429 | Exponential backoff | max_retries=5 |
| HTTP 503 | Retry with delay | base_delay=1.0 |
| Conflict (409) | Retry once | Check idempotency |
| Timeout | Retry with increased timeout | max_delay=60 |
For security configuration, see databricks-security-basics.
Basic usage: Apply databricks rate limits to a standard project setup with default configuration options.
Advanced scenario: Customize databricks rate limits for production environments with multiple constraints and team-specific requirements.
npx claudepluginhub aiminnovations/claude-code-plugins-plus --plugin databricks-packGuides reception of code review feedback: verify before implementing, avoid performative agreement, push back with technical reasoning when needed.
Design banners for social media, ads, website heroes, and print with multiple art direction options and AI-generated visuals.
4plugins reuse this skill
First indexed Jul 11, 2026