alchemy-rate-limits
Implement Alchemy Compute Unit (CU) rate limiting and request throttling. Use when handling 429 errors, optimizing CU usage, or managing concurrent blockchain queries within plan limits. "alchemy throttling", "alchemy CU budget". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill alchemy-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.
# Alchemy Rate Limits ## Overview Alchemy uses Compute Units (CU) to measure API usage. Different methods cost different CU amounts. Rate limits are per-second, and exceeding them returns 429 errors. ## Compute Unit Costs | Method | CU Cost | Category | |--------|---------|----------| | `eth_blockNumber` | 10 | Core | | `eth_getBalance` | 19 | Core | | `eth_call` | 26 | Core | | `eth_getTransactio
What does the alchemy-rate-limits skill do?
Implement Alchemy Compute Unit (CU) rate limiting and request throttling. Use when handling 429 errors, optimizing CU usage, or managing concurrent blockchain queries within plan limits. "alchemy throttling", "alchemy CU budget". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill alchemy-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.