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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill documenso-rate-limits90
Quality
88%
Does it follow best practices?
Impact
97%
2.36xAverage score across 3 eval scenarios
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 excels across all dimensions. It uses third person voice correctly, provides specific concrete actions, includes explicit 'Use when' and 'Trigger with' clauses with natural user phrases, and maintains clear distinctiveness through consistent Documenso-specific terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'rate limiting', 'backoff', 'request throttling patterns', 'retry logic', and 'optimizing API request throughput'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (implement rate limiting, backoff, throttling patterns) AND when (handling rate limit errors, implementing retry logic, optimizing 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'. These are terms users would naturally use when encountering these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the 'Documenso' qualifier throughout. The combination of Documenso-specific context with rate limiting/throttling patterns creates a clear niche unlikely to conflict with generic rate limiting skills or other API skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent executable code examples covering rate limiting comprehensively. The workflow is clear and builds logically from simple backoff to complex bulk operations. Main weakness is length - the detailed implementations could be split into reference files to improve progressive disclosure and reduce token usage.
Suggestions
Remove the Prerequisites section - Claude already understands async/await patterns and doesn't need this reminder
Consider moving the detailed implementations (Steps 4-6) to a separate RATE-LIMIT-ADVANCED.md file, keeping only Steps 1-3 in the main skill
Condense the fair use policy table by removing the Notes column and integrating key notes inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary elements like the Prerequisites section (Claude knows async/await) and verbose comments. The fair use policy table is useful but could be more compact. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with complete implementations for backoff, queuing, batching, monitoring, and idempotency. All examples are copy-paste ready with proper imports and type definitions. | 3 / 3 |
Workflow Clarity | Clear 6-step sequence building from basic backoff to complete bulk processing. Each step builds on previous ones, includes validation through the RateLimitMonitor, and the bulk processing example shows explicit batch-by-batch feedback with error handling. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is quite long (~300 lines) and could benefit from splitting detailed implementations into separate reference files. The inline code examples are comprehensive but make the main skill lengthy. | 2 / 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 | |
- 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.