Agent skill

Documenso Deploy Integration

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Deploy Documenso integrations across different platforms and environments.

MITAuto-check passedDevOps & Cloud

Install Documenso Deploy Integration

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill documenso-deploy-integration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace documenso-deploy-integration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/documenso-deploy-integration .claude/skills/documenso-deploy-integration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
documenso-deploy-integration
GitHub stars
2.8k
Token cost
~1.9k tokens
SKILL.md length
317 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Deploy Documenso integrations across different platforms and environments.

  • Works in 5 steps: Dockerize Your Documenso Integration → Self-Hosted Documenso (Docker Compose) → AWS Lambda (API Integration) → …
  • Deploying to cloud platforms
  • SKILL.md covers Output, Examples, Overview and Prerequisites, plus 5 more sections
  • Calls gcloud and openssl; needs DOCUMENSO_API_KEY and NEXTAUTH_SECRET

What it does

Documenso Deploy Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Deploy Documenso integrations across different platforms and environments. Use when deploying to cloud platforms, containerizing applications, or setting up infrastructure for Documenso integrations. Trigger with phrases like "deploy documenso", "documenso docker", "documenso kubernetes", "documenso cloud deployment".

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/implementation-guide.md`). Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering Deployment, Containers and Container orchestration. It works with Docker and Kubernetes. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Deploying to cloud platforms
  • Containerizing applications
  • Setting up infrastructure for Documenso integrations
  • With phrases like deploy documenso

Example prompts

  • “deploy documenso”
  • “documenso docker”
  • “documenso kubernetes”
  • “/documenso-deploy-integration”

Requirements

  • Docker
  • A credential in DOCUMENSO_API_KEY
  • A credential in NEXTAUTH_SECRET
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(docker:*), Bash(kubectl:*)

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Dockerize Your Documenso Integration
  2. Self-Hosted Documenso (Docker Compose)
  3. AWS Lambda (API Integration)
  4. Google Cloud Run
  5. Health Check Endpoint

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(docker:*)
    • Bash(kubectl:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gcloud
    • openssl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.documenso.com
    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • DOCUMENSO_API_KEY
    • NEXTAUTH_SECRET
    • NEXT_PRIVATE_ENCRYPTION_KEY
    • ENCRYPTION_KEY
    • NEXT_PRIVATE_ENCRYPTION_SECONDARY_KEY
    • ENCRYPTION_SECONDARY_KEY
    • NEXT_PRIVATE_SMTP_PASSWORD
    • POSTGRES_PASSWORD

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Documenso Deploy Integration loads about 1.9k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 317 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 317 words, ~1,866 tokens.

Download SKILL.mdSave it as .claude/skills/documenso-deploy-integration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
documenso-deploy-integration
description
Deploy Documenso integrations across different platforms and environments. Use when deploying to cloud platforms, containerizing applications, or setting up infrastructure for Documenso integrations. Trigger with phrases like "deploy documenso", "documenso docker", "documenso kubernetes", "documenso cloud deployment".
allowed-tools
Read, Write, Edit, Bash(docker:*), Bash(kubectl:*)
compatibility
Designed for Claude Code
version
1.14.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, documenso, deployment, docker, kubernetes

Documenso Deploy Integration

Output

  • A versioned, staged document/signing deployment with owner approval, validation evidence, and rollback reference.
  • A protected promotion path that prevents unreviewed configurations from affecting production documents or signers.

Examples

Deploy a synthetic document workflow to staging with scoped credentials, verify authorization, signing lifecycle, webhook verification, and redacted alerts, then use an approved production canary. Stop and roll back if audience, access, or lifecycle behavior differs; do not place document data or signing links in deployment logs.

Overview

Deploy Documenso-integrated applications and self-hosted Documenso instances to Docker, Kubernetes, serverless, and cloud platforms. Covers both app deployment (your code that uses the Documenso API) and self-hosted Documenso deployment.

Prerequisites

  • Application ready for deployment
  • Cloud platform account (AWS, GCP, Azure)
  • Docker installed locally
  • Completed documenso-multi-env-setup

Instructions

Step 1: Dockerize Your Documenso Integration
dockerfile
# Dockerfile
FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build

FROM node:20-alpine AS runtime
WORKDIR /app
RUN addgroup -S app && adduser -S app -G app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json .
USER app
EXPOSE 3000
CMD ["node", "dist/server.js"]
# Note: DOCUMENSO_API_KEY injected at runtime, never baked into image
Step 2: Self-Hosted Documenso (Docker Compose)
yaml
# docker-compose.prod.yml
services:
  documenso:
    image: documenso/documenso:latest
    ports:
      - "3000:3000"
    environment:
      - NEXTAUTH_URL=https://sign.yourcompany.com
      - NEXTAUTH_SECRET=${NEXTAUTH_SECRET}   # openssl rand -hex 32
      - NEXT_PRIVATE_ENCRYPTION_KEY=${ENCRYPTION_KEY}
      - NEXT_PRIVATE_ENCRYPTION_SECONDARY_KEY=${ENCRYPTION_SECONDARY_KEY}
      - NEXT_PUBLIC_WEBAPP_URL=https://sign.yourcompany.com
      - NEXT_PRIVATE_DATABASE_URL=postgresql://documenso:${DB_PASS}@db:5432/documenso
      - NEXT_PRIVATE_DIRECT_DATABASE_URL=postgresql://documenso:${DB_PASS}@db:5432/documenso
      # SMTP
      - NEXT_PRIVATE_SMTP_TRANSPORT=smtp-auth
      - NEXT_PRIVATE_SMTP_HOST=${SMTP_HOST}
      - NEXT_PRIVATE_SMTP_PORT=587
      - NEXT_PRIVATE_SMTP_USERNAME=${SMTP_USER}
      - NEXT_PRIVATE_SMTP_PASSWORD=${SMTP_PASS}
      - NEXT_PRIVATE_SMTP_FROM_ADDRESS=signing@yourcompany.com
      - NEXT_PRIVATE_SMTP_FROM_NAME=YourCompany Signing
      # Signing certificate
      - NEXT_PRIVATE_SIGNING_PASSPHRASE=${CERT_PASSPHRASE}
    volumes:
      - ./certs/signing-cert.p12:/opt/documenso/cert.p12:ro
    depends_on:
      db:
        condition: service_healthy
    restart: unless-stopped

  db:
    image: postgres:16-alpine
    environment:
      POSTGRES_USER: documenso
      POSTGRES_PASSWORD: ${DB_PASS}
      POSTGRES_DB: documenso
    volumes:
      - pgdata:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U documenso"]
      interval: 5s
      retries: 5

volumes:
  pgdata:

Important notes:

  • Documenso container runs as non-root (UID 1001) -- ensure mounted files are readable
  • Prisma migrations run automatically on container start
  • Documents are stored in PostgreSQL by default (fine for small-to-medium deployments)
  • Use a reverse proxy (nginx, Caddy, Traefik) for SSL termination
Step 3: AWS Lambda (API Integration)
typescript
// lambda/signing-handler.ts
import { Documenso } from "@documenso/sdk-typescript";
import { SecretsManager } from "@aws-sdk/client-secrets-manager";

const sm = new SecretsManager({ region: "us-east-1" });
let client: Documenso;

async function getClient(): Promise<Documenso> {
  if (!client) {
    const secret = await sm.getSecretValue({ SecretId: "documenso/api-key" });
    client = new Documenso({ apiKey: JSON.parse(secret.SecretString!).apiKey });
  }
  return client;
}

export async function handler(event: any) {
  const documenso = await getClient();
  const { title, signerEmail, signerName } = JSON.parse(event.body);

  const doc = await documenso.documents.createV0({ title });
  await documenso.documentsRecipients.createV0(doc.documentId, {
    email: signerEmail,
    name: signerName,
    role: "SIGNER",
  });
  await documenso.documents.sendV0(doc.documentId);

  return {
    statusCode: 200,
    body: JSON.stringify({ documentId: doc.documentId }),
  };
}
Step 4: Google Cloud Run
bash
# Store secret
echo -n "$DOCUMENSO_API_KEY" | gcloud secrets create documenso-api-key --data-file=-

# Deploy
gcloud run deploy signing-service \
  --image gcr.io/$PROJECT_ID/signing-service \
  --platform managed \
  --region us-central1 \
  --set-secrets DOCUMENSO_API_KEY=documenso-api-key:latest \
  --memory 256Mi \
  --timeout 30s
Step 5: Health Check Endpoint
typescript
// src/health.ts — include in every deployment
app.get("/health", async (req, res) => {
  try {
    const client = new Documenso({ apiKey: process.env.DOCUMENSO_API_KEY! });
    await client.documents.findV0({ page: 1, perPage: 1 });
    res.json({ status: "healthy", service: "documenso" });
  } catch (err: any) {
    res.status(503).json({
      status: "unhealthy",
      service: "documenso",
      error: err.message,
    });
  }
});

Deployment Checklist

  • API keys stored in secret manager (not env files)
  • Health check endpoint configured
  • HTTPS enforced (required for webhooks)
  • Self-hosted: signing certificate mounted
  • Self-hosted: secrets generated with openssl rand -hex 32
  • Reverse proxy handles SSL termination
  • Container runs as non-root user
  • Monitoring and alerting configured

Error Handling

Deployment IssueCauseSolution
Container crash on startMissing env varsCheck all required env vars are set
Health check failsAPI key invalidVerify secret manager value
Database connection refusedWrong connection stringCheck NEXT_PRIVATE_DATABASE_URL
Signing certificate errorWrong passphrase or pathVerify mount path and SIGNING_PASSPHRASE
Emails not sendingSMTP misconfiguredCheck host/port/credentials

Resources

Next Steps

For webhook configuration, see documenso-webhooks-events.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/documenso-deploy-integration of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/implementation-guide.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Documenso Deploy Integration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Documenso Deploy Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Documenso Deploy Integration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.9kAutomated safety check: PassMIT
LangBot Deployment Guidelangbot-app/LangBot18k—~1.2kAutomated safety check: NotesApache-2.0
Debug Openshell ClusterNVIDIA/OpenShell16k—~20kAutomated safety check: NotesApache-2.0
Deploymentmatrixorigin/memoria610—~1.6kAutomated safety check: NotesApache-2.0
Onboarding Validationopen-edge-platform/edge-ai-suites140—~3.3kAutomated safety check: PassApache-2.0
Agenticx DeployerDemonDamon/AgenticX340—~866Automated safety check: PassApache-2.0

Similar skills

  • LangBot Deployment Guide

    langbot-app/LangBot

    Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.

    18k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Debug Openshell Cluster

    NVIDIA/OpenShell

    Official

    Debug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes.

    16k GitHub stars~20k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Deployment

    matrixorigin/memoria

    Deploy Memoria with Docker Compose or Kubernetes. An agent skill from matrixorigin/memoria.

    610 GitHub stars~1.6k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Onboarding Validation

    open-edge-platform/edge-ai-suites

    Validate the get-started experience of Open Edge Platform (OEP) software components from the perspective of a first-time user.

    140 GitHub stars~3.3k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Agenticx Deployer

    DemonDamon/AgenticX

    Guide for deploying AgenticX agents to production including Docker containerization, Kubernetes orchestration, Volcengine AgentKit cloud deployment, and API server setup.

    340 GitHub stars~866 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Aspire Deployment

    CommunityToolkit/Aspire

    WORKFLOW SKILL — Deploy Aspire apps from AppHost models to Docker Compose, Kubernetes, Azure, AWS, or preview Radius.

    627 GitHub stars~4.5k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Documenso Deploy Integration

What does Documenso Deploy Integration do?

Deploy Documenso integrations across different platforms and environments. Documenso Deploy Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Deploy Documenso integrations across different platforms and environments.

When should I use Documenso Deploy Integration?

Documenso Deploy Integration fits situations like: deploying to cloud platforms; containerizing applications; setting up infrastructure for Documenso integrations; with phrases like deploy documenso.

How do I install Documenso Deploy Integration in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill documenso-deploy-integration -a claude-code`. Or copy the skill folder (skills/.curated/documenso-deploy-integration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/documenso-deploy-integration in your project. Claude Code loads it when a task matches its description.

How do I install Documenso Deploy Integration in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill documenso-deploy-integration -a codex`. Or copy the skill folder (skills/.curated/documenso-deploy-integration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/documenso-deploy-integration in your project. Codex loads it when a task matches its description.

Can I use Documenso Deploy Integration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill documenso-deploy-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/documenso-deploy-integration, .gemini/skills/documenso-deploy-integration, .github/skills/documenso-deploy-integration and .opencode/skills/documenso-deploy-integration in your project.

What does Documenso Deploy Integration need to run?

Going by SKILL.md and its folder, Documenso Deploy Integration needs the command-line tools its instructions call (gcloud and openssl) and credentials named DOCUMENSO_API_KEY, NEXTAUTH_SECRET, NEXT_PRIVATE_ENCRYPTION_KEY and ENCRYPTION_KEY. Our summary lists: Docker; A credential in DOCUMENSO_API_KEY; A credential in NEXTAUTH_SECRET. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(docker:*), Bash(kubectl:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Documenso Deploy Integration access the network?

SKILL.md names 2 domains. As links in the text: docs.documenso.com and github.com. This is read from the text; nothing was executed.

Is Documenso Deploy Integration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Documenso Deploy Integration use?

Documenso Deploy Integration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Documenso Deploy Integration use?

About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Documenso Deploy Integration?

Skills that share tags, products or a category with Documenso Deploy Integration: LangBot Deployment Guide (langbot-app/LangBot, 18k stars), Debug Openshell Cluster (NVIDIA/OpenShell, 16k stars), Deployment (matrixorigin/memoria, 610 stars) and Onboarding Validation (open-edge-platform/edge-ai-suites, 140 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Documenso Deploy Integration?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.