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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

65%Weight 40%Scale 1-3

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

The content is highly actionable with complete, executable code across languages, but workflow clarity is capped by missing validation checkpoints for batch operations and progressive disclosure is weakened by an unreferenced, overlapping bundle file. Tightening duplication and adding verification steps would raise quality.

Suggestions

Add explicit validation/verification checkpoints to the bulk document creation and queued-request workflows (e.g. verify created documents, retry/log on partial failures) to lift workflow_clarity above 2.

Link the existing references/implementation-guide.md from the body (e.g. an 'Advanced patterns' section pointing to it) and move the duplicated fair-use table and retry logic there to improve progressive disclosure and reduce duplication.

Remove or consolidate the inline fair-use model table content that repeats in the implementation guide to improve conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly code-forward and avoids explaining basic concepts, but it duplicates material present in the unreferenced references/implementation-guide.md (fair-use table, retry logic) that could be tightened or delegated.	2 / 3
Actionability	Provides fully executable TypeScript and Python code with concrete config values and usage examples (e.g. withRetry, PQueue, CircuitBreaker), matching the score-3 copy-paste-ready anchor.	3 / 3
Workflow Clarity	Steps are sequenced (Step 1-4), but batch operations (bulk document creation, queued requests) lack validation/verification checkpoints and feedback loops, which the rubric caps at 2 for batch operations.	2 / 3
Progressive Disclosure	A bundle file references/implementation-guide.md exists with substantial deeper content, but the body never signals or links it, so the overview-to-reference structure is present but not clearly navigated.	2 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, specific, and complete — it names concrete capabilities, provides explicit trigger phrases, and clearly states both what it does and when to use it. It is strongly distinct to the Documenso domain.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "rate limiting, backoff, and request throttling patterns" — matching the score-3 anchor for specific concrete actions.	3 / 3
Completeness	Clearly answers both what ("Implement Documenso rate limiting, backoff, and request throttling") and when ("Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput"), with explicit triggers.	3 / 3
Trigger Term Quality	Provides explicit natural trigger phrases ("documenso rate limit", "documenso throttling", "documenso 429", "documenso retry", "documenso backoff") giving good coverage of terms users would say.	3 / 3
Distinctiveness Conflict Risk	Narrowly scoped to Documenso with distinct triggers ("documenso 429", "documenso backoff"), making it unlikely to fire for unrelated skills.	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
Path: plugins/saas-packs/documenso-pack/skills/documenso-rate-limits/SKILL.md
Commit: 4c47e33

Reviewed: 2 days 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.