Agent skill · Backend & API

documenso-rate-limits

Implement Documenso rate limiting, backoff, and request throttling patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Documenso. Trigger with phrases like "documenso rate limit", "documenso throttling", "documenso 429", "documenso retry", "documenso backoff".

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill documenso-rate-limits --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 10 KB
Bundled scripts: none
Version: 1.0.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEdit
Path: skills/api/documenso-rate-limits/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Documenso Rate Limits ## Overview Handle Documenso API rate limits gracefully with exponential backoff, request queuing, and fair use compliance. ## Prerequisites - Documenso SDK installed - Understanding of async/await patterns - Queue library (optional but recommended) ## Documenso Fair Use Policy Documenso implements fair use rate limiting. While specific limits are not publicly documented, follow these guidelines: | Recommendation | Limit | Notes | |----------------|-------|-------| | Requests per second | 5-10 | Stay well under burst | | Requests per minute | 100-200 | Sustained rate | | Bulk operations | Use batching | Batch create recipients/fields | | File uploads | 1 at a time | Sequential uploads | | Polling | 5-10 second intervals | Don't poll aggressively | ## Instructions ### Step 1: Implement Exponential Backoff with Jitter ```typescript interface BackoffConfig { maxRetries: number; baseDelayMs: number; maxDelayMs: number; jitterMs: number; } const DEFAULT_BACKOFF: BackoffConfig = { maxRetries: 5, baseDelayMs: 1000, maxDelayMs: 32000, jitterMs: 500, }; async function withExponentialBackoff<T>( operation: () => Promise<T>, config: Partial<BackoffConfig> = {} ): Promi

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Documenso Fair Use Policy
  4. Instructions
  5. Step 1: Implement Exponential Backoff with Jitter
  6. Step 2: Request Queue for Controlled Throughput
  7. Step 3: Batch Operations
  8. Step 4: Rate Limit Monitor
  9. Step 5: Idempotent Requests
  10. Step 6: Bulk Document Processing with Rate Control
  11. Output
  12. Error Handling
  13. Resources
  14. Next Steps
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the documenso-rate-limits skill do?

Implement Documenso rate limiting, backoff, and request throttling patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Documenso. Trigger with phrases like "documenso rate limit", "documenso throttling", "documenso 429", "documenso retry", "documenso backoff".

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill documenso-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 majiayu000/claude-skill-registry, a repository with 534 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.

Keep going