palantir-rate-limits
Implement Palantir Foundry API rate limiting, backoff, and request queuing. Use when handling 429 errors, implementing retry logic, or optimizing API request throughput for Foundry. Trigger with phrases like "palantir rate limit", "foundry throttling", "palantir 429", "foundry retry", "palantir backoff". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill palantir-rate-limits --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Palantir Rate Limits ## Overview Handle Foundry API rate limits with exponential backoff, request queuing, and monitoring. Foundry rate limits vary by endpoint and enrollment tier. ## Prerequisites - `foundry-platform-sdk` installed - Understanding of HTTP 429 responses ## Instructions ### Step 1: Understand Foundry Rate Limits Foundry rate limits are per-user and per-endpoint. Key limits: | End
What does the palantir-rate-limits skill do?
Implement Palantir Foundry API rate limiting, backoff, and request queuing. Use when handling 429 errors, implementing retry logic, or optimizing API request throughput for Foundry. Trigger with phrases like "palantir rate limit", "foundry throttling", "palantir 429", "foundry retry", "palantir backoff". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill palantir-rate-limits --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.