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".
87
86%
Does it follow best practices?
Impact
Pending
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 status 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 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'documenso rate limit', 'documenso throttling', 'documenso 429', 'documenso retry', 'documenso backoff'. The inclusion of HTTP status code '429' is particularly good as users would naturally mention this. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the combination of 'Documenso' as a specific product and the narrow focus on rate limiting/throttling patterns. Unlikely to conflict with general API skills or other Documenso skills focused on different concerns. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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 some unnecessary verbosity around the Documenso pricing/fair-use model and a lack of explicit validation checkpoints for the bulk operation workflow and circuit breaker testing.
Suggestions
Trim or remove the pricing table and fair-use commentary — Claude doesn't need marketing context to implement retry logic. A single sentence noting that 429s are the primary rate limit signal would suffice.
Add a verification step after bulk operations (Step 2) explaining how to handle/retry the failed items from Promise.allSettled results, not just log counts.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The plan pricing table and fair-use model explanation add context Claude doesn't strictly need to implement retry logic. The code examples themselves are lean, but the surrounding prose (e.g., 'Documenso explicitly does not price API usage -- they want developers to build on the platform without API cost concerns') is unnecessary filler. | 2 / 3 |
Actionability | All code examples are fully executable, copy-paste ready TypeScript and Python with complete implementations of retry, queue, and circuit breaker patterns. Usage examples are included for each pattern. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, and the error handling table provides good guidance. However, there's no explicit validation or verification step — e.g., how to confirm the retry/queue is working correctly, or a feedback loop for testing the circuit breaker threshold. For bulk operations (Step 2), there's no guidance on what to do with failed items beyond logging counts. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, a summary error handling table, external resource links, and a pointer to the next skill (documenso-security-basics). The skill is self-contained at an appropriate length without needing to split into sub-files. | 3 / 3 |
Total | 10 / 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
c8a915c
- 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.