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".
84
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly defines its scope around Documenso rate limiting and throttling patterns. It excels in all dimensions by providing specific actions, natural trigger terms (including the HTTP 429 code), explicit 'Use when' and 'Trigger with' clauses, and a narrow enough niche to avoid conflicts with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: rate limiting, backoff, request throttling patterns, retry logic, and optimizing API request throughput. These are distinct, concrete technical capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement rate limiting, backoff, and request throttling patterns) and 'when' (handling rate limit errors, implementing retry logic, optimizing API request throughput) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'documenso rate limit', 'documenso throttling', 'documenso 429', 'documenso retry', 'documenso backoff'. These are terms users would naturally use when encountering these issues, including the HTTP status code 429. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of 'Documenso' platform and rate limiting/throttling domain. The explicit trigger phrases with the 'documenso' prefix make it very unlikely to conflict with generic rate limiting skills or other Documenso skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with complete, executable code examples in both TypeScript and Python covering retry, queuing, and circuit breaker patterns. Its main weaknesses are moderate verbosity (plan pricing details, explanatory prose about Documenso's philosophy) and missing validation/feedback loops for bulk operations. The content would benefit from trimming non-essential context and adding explicit error recovery steps for batch failures.
Suggestions
Add a feedback loop in Step 2 for retrying failed items from bulk operations (e.g., collect rejected results and re-queue them through the retry mechanism).
Remove or condense the pricing table and fair-use philosophy explanation — a single sentence noting 'no published rate limits; 429s only occur under abusive traffic patterns' would suffice.
Consider splitting the circuit breaker and Python retry into separate referenced files to improve progressive disclosure for this code-heavy skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The fair-use model table and explanation are useful context since Documenso's rate limiting differs from typical APIs, but the plan pricing details ($30/mo) and some explanatory prose ('they want developers to build on the platform without API cost concerns') are unnecessary padding. The code examples are reasonably lean but the overall document could be tightened. | 2 / 3 |
Actionability | All code examples are fully executable with proper TypeScript and Python implementations. The retry logic, queue, and circuit breaker patterns include complete, copy-paste-ready implementations with usage examples and sensible defaults. | 3 / 3 |
Workflow Clarity | The steps are clearly sequenced and the error handling table provides good guidance on when to retry vs. not. However, there are no explicit validation checkpoints — for bulk operations (Step 2), there's no feedback loop for handling the failed results beyond logging counts, and no guidance on retrying failed items from the batch. | 2 / 3 |
Progressive Disclosure | The document is well-structured with clear sections and a logical flow from simple retry to queue to circuit breaker. However, at ~150 lines of code-heavy content, the circuit breaker and Python retry sections could reasonably be split into separate referenced files. The references to other skills ('documenso-install-auth', 'documenso-security-basics') are good but the inline content is heavy for a single SKILL.md. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.