Agent skill · software engineering · jeremylongshore
mindtickle-rate-limits
Discover and enforce a Mindtickle tenant''s documented capacity, retry, pagination, and concurrency contract. Use when planning bulk syncs or responding to throttling. Trigger with "handle Mindtickle limits".
Why this skill is useful
Provides specific implementation details for handling MindTickle API rate limits, including a custom rate limiter and retry strategy that the AI wouldn't generate on its own.
What it needs
Requires mindtickle account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Mindtickle Capacity and Retry Contract Overview Replace guessed quotas with an evidence-backed workload envelope and a conservative client policy that protects the tenant and downstream systems. Prerequisites Current tenant documentation or written vendor guidance for the operations in scope A workload profile with record counts, freshness target, windows, and priority Metrics for attempts, latency, responses, retries, backlog, and reconciliation Tool Discipline Use Read, Glob, and Grep for workload and adapter configuration, WebFetch for current authorized contracts, and Write or Edit for a versioned policy and synthetic test fixtures. Current Contract Mindtickle publicly states its integrations support high-volume transactions but does not publish universal endpoint quotas. Numeric limits, response headers, pagination, safe concurrency, and retry behavior must come from the customer's current contract or observed authorized responses. Authentication Use a non-production, least-privilege principal for any capacity probe. Never distribute load across extra credentials or tenants to evade a documented limit. Instructions 1. Inventory each operation's documented pagination, batch size, concurrency, timeout, retry, and idempotency behavior. 2. Mark every missing value unknown; do not fill gaps with generic numbers. 3. Model peak demand, allowable staleness, downstream limits, and replay volume after an outage. 4. Define a conservative token or concurrency policy, bounded exponential backoff with jitter, and a total retry budget. 5. Add backpressure, dead-letter or quarantine handling, and write reconciliation where the contract permits. 6. Validate locally with synthetic throttle, timeout, malformed-response, and recovery fixtures. 7. Obtain approval before a controlled tenant probe; stop at the first throttling or instability signal. 8. Version the resulting envelope with evidence, owner, expiry, dashboards, and escalation thresholds. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mindtickle-rate-limits