Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/documenso-observability
Implement monitoring, logging, and tracing for Documenso integrations.
Passed 21 of 22 test cases with the skill, and 8 of 22 without it.
and 16 more in the full report
13 fixed8 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our Prometheus alerting rule for Documenso health check failures is triggering false alarms on brief 10-second network blips. What specific parameter should be added to the alert rule YAML to prevent flapping?
| Checked | Without skill | With skill |
|---|---|---|
| The Prometheus alert rule includes 'for: 2m' to delay firing on brief failures. | Missed | Passed |
The instructions your model reads when the skill loads.
Emit aggregate counts by environment, document state, and status class while excluding document bodies, signer email, signing URLs, IP addresses, tokens, and audit payloads. Trigger a development signing-state alert with a synthetic document, verify the on-call route, then retain only the redacted receipt.
Implement monitoring, structured logging, and health checks for Documenso integrations. Since Documenso does not expose rate limit headers or usage metrics via API, observability is built around your API call patterns, latency, error rates, and webhook delivery.
// src/observability/documenso-metrics.ts
import { Documenso } from "@documenso/sdk-typescript";
interface Metrics {
requestCount: number;
errorCount: number;
totalLatencyMs: number;
errorsByStatus: Record<number, number>;
}
const metrics: Metrics = {
requestCount: 0,
errorCount: 0,
totalLatencyMs: 0,
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.