Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/documenso-performance-tuning
Optimize Documenso integration performance with caching, batching, and efficient patterns.
Passed 17 of 22 test cases with the skill, and 13 of 22 without it.
and 8 more in the full report
6 fixed11 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are experiencing high latency and occasional rate limits when fetching document status and creating signing requests at scale using the Documenso SDK. I want to implement concurrency queues and metadata caching to improve throughput. Can you optimize this integration and output both a measured performance change report bounded by document lifecycle, authorization, audit logging, and system reliability guardrails, as well as a reversible change log detailing aggregate metrics, ownership, trigger thresholds, and rollback decisions?
| Checked | Without skill | With skill |
|---|---|---|
| Applies node-cache for caching document metadata. | Missed | Passed |
| Sets a 1-hour TTL for completed documents. | Missed | Passed |
| Sets a 30-second TTL for in-progress documents. | Missed | Passed |
| Enforces a maximum concurrency cap on outbound API calls. | Passed | Passed |
The instructions your model reads when the skill loads.
Measure synthetic-document workflow latency, throughput, error rate, and callback completion in staging, change one approved capacity/cache/concurrency setting, and compare against baseline. Revert if signing state, authorization, audit, or error behavior regresses; do not use real documents or weaken controls to improve a benchmark.
Optimize Documenso integrations for speed and efficiency. Key strategies: reduce API round-trips with templates, cache document metadata, batch operations with concurrency control, and use async processing for bulk signing workflows.
documenso-sdk-patterns setupThe biggest performance win: templates reduce a multi-step document creation (create + upload + add recipients + add fields + send = 5+ calls) to just 2 calls (create from template + send).
// WITHOUT templates: 5+ API calls per document
async function createDocumentManual(signer: { email: string; name: string }) {
const doc = await client.documents.createV0({ title: "Contract" }); // 1
await client.documents.setFileV0(doc.documentId, { file: pdfBlob }); // 2
const recip = await client.documentsRecipients.createV0(doc.documentId, { // 3
email: signer.email, name: signer.name, role: "SIGNER",
});
await client.documentsFields.createV0(doc.documentId, { // 4
recipientId: recip.recipientId, type: "SIGNATURE",
pageNumber: 1, pageX: 10, pageY: 80, pageWidth: 30, pageHeight: 5,
});
await client.documents.sendV0(doc.documentId); // 5
test cases passed, vs 13 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.