Documenso Debug BundleCAUTION
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-08Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: documenso-debug-bundle description: 'Comprehensive debugging toolkit for Documenso integrations. Use when troubleshooting complex issues, gathering diagnostic information, or creating support tickets for Documenso problems. Trigger with phrases like "debug documenso", "documenso diagnostics", "troubleshoot documenso", "documenso support ticket". ' allowed-tools: Read, Write, Edit, Bash(curl:*), Bash(node:*), Grep version: 1.14.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - documenso - debugging compatibility: Designed for Claude Code --- # Documenso Debug Bundle ## Output - A minimal redacted diagnostic bundle with correlation IDs, lifecycle state, environment, version, and status evidence. - A safe escalation/recovery record that preserves document/signature confidentiality and audit integrity. ## Examples For a signing failure, collect opaque document/correlation IDs, template version, environment, state transition, callback result, and timestamp. Review the bundle for document content, signer PII, signing links, tokens, and audit payloads before sharing; reproduce only with synthetic documents through the approved incident/support route. ## Current State !`node --version 2>/dev/null || echo 'N/A'` !`python3 --version 2>/dev/null || echo 'N/A'` !`uname -a` ## Overview Comprehensive debugging tools for Documenso integration issues. Includes diagnostic scripts, curl debug commands, environment verification, and support ticket templates. ## Prerequisites - Documenso SDK installed - Access to logs and configuration - `curl` and `jq` available ## Instructions ### Step 1: Quick Connectivity Test ```bash #!/bin/bash set -euo pipefail echo "=== Documenso Connectivity Test ===" # 1. Check API key is set if [ -z "${DOCUMENSO_API_KEY:-}" ]; then echo "FAIL: DOCUMENSO_API_KEY not set" exit 1 fi echo "OK: API key set (${#DOCUMENSO_API_KEY} chars)" # 2. Test authentication BASE="${DOCUMENSO_BASE_URL:-https://app.documenso.com/api/v1}" STATUS=$(curl -s -o /dev/null -w "%{http_code}" \ -H "Authorization: Bearer $DOCUMENSO_API_KEY" \ "$BASE/documents?page=1&perPage=1") if [ "$STATUS" = "200" ]; then echo "OK: API authentication successful" elif [ "$STATUS" = "401" ]; then echo "FAIL: Invalid API key (401)" exit 1 elif [ "$STATUS" = "403" ]; then echo "FAIL: Insufficient permissions (403) — try a team API key" exit 1 else echo "WARN: Unexpected status $STATUS" fi # 3. Check latency LATENCY=$(curl -s -o /dev/null -w "%{time_total}" \ -H "Authorization: Bearer $DOCUMENSO_API_KEY" \ "$BASE/documents?page=1&perPage=1") echo "Latency: ${LATENCY}s" # 4. List recent documents echo "=== Recent Documents ===" curl -s -H "Authorization: Bearer $DOCUMENSO_API_KEY" \ "$BASE/documents?page=1&perPage=5" | jq '.documents[] | {id, title, status, createdAt}' ``` ### Step 2: TypeScript Diagnostic Script ```typescript // scripts/documenso-diagnose.ts import { Documenso } from "@documenso/sdk-typescript"; async function diagnose() { const results: Array<{ test: string; status: "PASS" | "FAIL"; detail: string }> = []; // Test 1: API key const apiKey = process.env.DOCUMENSO_API_KEY; if (!apiKey) { results.push({ test: "API Key", status: "FAIL", detail: "DOCUMENSO_API_KEY not set" }); return results; } results.push({ test: "API Key", status: "PASS", detail: `Set (${apiKey.length} chars)` }); // Test 2: Connection const client = new Documenso({ apiKey, ...(process.env.DOCUMENSO_BASE_URL && { serverURL: process.env.DOCUMENSO_BASE_URL }), }); try { const start = Date.now(); const { documents } = await client.documents.findV0({ page: 1, perPage: 1 }); const latency = Date.now() - start; results.push({ test: "Connection", status: "PASS", detail: `${latency}ms, ${documents.length} documents returned`, }); } catch (err: any) { results.push({ test: "Connection", status: "FAIL", detail: `${err.statusCode ?? "unknown"}: ${err.message}`, }); } // Test 3: Create + Delete (write access) try { const doc = await client.documents.createV0({ title: "[DIAG] Test Document" }); await client.documents.deleteV0(doc.documentId); results.push({ test: "Write Access", status: "PASS", detail: "Create+delete OK" }); } catch (err: any) { results.push({ test: "Write Access", status: "FAIL", detail: err.message, }); } // Print report console.log("\n=== Documenso Diagnostic Report ==="); for (const r of results) { console.log(` [${r.status}] ${r.test}: ${r.detail}`); } const failures = results.filter((r) => r.status === "FAIL").length; console.log(`\n${results.length} tests, ${failures} failures\n`); return results; } diagnose(); ``` Run: `npx tsx scripts/documenso-diagnose.ts` ### Step 3: Debug Logging Wrapper ```typescript // src/documenso/debug-client.ts import { Documenso } from "@documenso/sdk-typescript"; export function createDebugClient(): Documenso { const client = new Documenso({ apiKey: process.env.DOCUMENSO_API_KEY! }); // Proxy to log all method calls return new Proxy(client, { get(target, prop) { const value = (target as any)[prop]; if (typeof value === "object" && value !== null) { return new Proxy(value, { get(innerTarget, innerProp) { const method = (innerTarget as any)[innerProp]; if (typeof method === "function") { return async (...args: any[]) => { const start = Date.now(); console.log(`[DOCUMENSO] ${String(prop)}.${String(innerProp)}(`, JSON.stringify(args).slice(0, 200), ")"); try { const result = await method.apply(innerTarget, args); console.log(`[DOCUMENSO] OK in ${Date.now() - start}ms`); return result; } catch (err: any) { console.error
Trust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | FAIL |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (1)
| Write test fails | Read-only key or no team access | Use team API key with write permissions |
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__documenso-debug-bundle.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 4f83675ca38a | CAUTION | B | 89 | first audit |
Questions
What does the Documenso Debug Bundle skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Documenso Debug Bundle safe to install?
With care. The audit graded it B (89/100) and found 1 thing worth knowing before you trust this skill, listed below with the exact line each was found on.
What can Documenso Debug Bundle access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Documenso Debug Bundle work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-08. The repository is watched, and a new audit runs when it changes — this is the first audit.