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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is highly actionable with executable TypeScript and Python examples and a useful error-handling matrix, but it loses points for duplicated retry logic, a missing validate/verify feedback loop on the bulk-operation path, and an orphaned bundle file that is never referenced from the body.

Suggestions

Remove the duplicated retry logic between Step 1 (TypeScript) and Step 4 (Python); keep one canonical implementation and, if both languages matter, link the second from a reference rather than restating it inline.

Add a validation/verification checkpoint to the bulk-create workflow — e.g., retry or surface the rejected items from Promise.allSettled rather than only logging succeeded/failed counts.

Link the existing references/implementation-guide.md from the body (e.g., a '## Implementation guide' section with a markdown link) so the bundle is discoverable and the body stays a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete code and a compact fair-use table, but the retry logic is duplicated across TypeScript (Step 1) and Python (Step 4), and the 'Documenso explicitly does not price API usage' line restates the preceding table.	2 / 3
Actionability	Fully executable TypeScript and Python code with specific concurrency values ('concurrency: 5, interval: 1000, intervalCap: 10'), concrete circuit-breaker thresholds, and an error-handling table mapping scenarios to actions — copy-paste ready.	3 / 3
Workflow Clarity	Steps 1–4 are sequenced and an error-handling table exists, but the bulk-operation path (createBulkDocuments) lacks a validation/verify feedback loop, which the rubric requires to cap workflow clarity at 2 for batch operations.	2 / 3
Progressive Disclosure	The body has clear sections and a real references/implementation-guide.md bundle exists, but the body never links to or signals that guide, keeping all content inline rather than splitting it out one level deep.	2 / 3
	Total	9 / 12 Passed

Description

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.

A strong description: it states concrete capabilities, gives an explicit 'Use when' trigger clause, and supplies natural trigger phrases scoped to the Documenso brand. The only minor weakness is somewhat padded multi-line formatting, but the content itself is concise and on-target.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'rate limiting, backoff, and request throttling patterns' and 'handling rate limit errors, implementing retry logic, or optimizing API request throughput' — rather than vague language.	3 / 3
Completeness	Explicitly answers both 'what' (rate limiting, backoff, throttling) and 'when' ('Use when handling rate limit errors, implementing retry logic...'), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Provides good coverage of natural trigger phrases a user would say: 'documenso rate limit', 'documenso throttling', 'documenso 429', 'documenso retry', 'documenso backoff'.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to the Documenso domain with brand-prefixed triggers, making it clearly distinguishable and unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: about 3 hours ago

Table of Contents

Discovery Implementation Validation

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.