New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Documenso Upgrade Migration

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

Manage Documenso API version upgrades and SDK migrations. An agent skill from jeremylongshore/tons-of-skills-marketplace.

MITAuto-check passedDevelopment

Install Documenso Upgrade Migration

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

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace documenso-upgrade-migration --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-upgrade-migration .claude/skills/documenso-upgrade-migration && 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-upgrade-migration
GitHub stars
2.8k
Token cost
~1.8k tokens
SKILL.md length
364 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Manage Documenso API version upgrades and SDK migrations. An agent skill from jeremylongshore/tons-of-skills-marketplace.

  • Works in 5 steps: Upgrade SDK to Latest → v1 REST to v2 SDK Migration → Gradual Migration with Feature Flags → …
  • Upgrading from v1 to v2 API
  • SKILL.md covers Output, Examples, Current State and Overview, plus 7 more sections
  • Calls docker, npm and pip; needs DOCUMENSO_API_KEY

What it does

Documenso Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Manage Documenso API version upgrades and SDK migrations. Use when upgrading from v1 to v2 API, updating SDK versions, or migrating between Documenso versions. Trigger with phrases like "documenso upgrade", "documenso v2 migration", "update documenso SDK", "documenso API version".

Its SKILL.md is about 1.8k 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 Development, covering Code migrations. It works with Python and TypeScript. 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

  • Upgrading from v1 to v2 API
  • Updating SDK versions
  • Migrating between Documenso versions
  • With phrases like documenso upgrade

Example prompts

  • “documenso upgrade”
  • “documenso v2 migration”
  • “update documenso SDK”
  • “/documenso-upgrade-migration”

Requirements

  • Python 3
  • Node.js
  • Docker
  • A credential in DOCUMENSO_API_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(npm:*)

Workflow steps

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

  1. Upgrade SDK to Latest
  2. v1 REST to v2 SDK Migration
  3. Gradual Migration with Feature Flags
  4. Self-Hosted Version Upgrade
  5. Migration Testing

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(npm:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • docker
    • npm
    • pip
    • curl

    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):

    • github.com
    • openapi.documenso.com
    • docs.documenso.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

    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 Upgrade Migration loads about 1.8k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 77 tokens; SKILL.md has 364 words of instructions outside code blocks.

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

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). 364 words, ~1,784 tokens.

Download SKILL.mdSave it as .claude/skills/documenso-upgrade-migration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
documenso-upgrade-migration
description
Manage Documenso API version upgrades and SDK migrations. Use when upgrading from v1 to v2 API, updating SDK versions, or migrating between Documenso versions. Trigger with phrases like "documenso upgrade", "documenso v2 migration", "update documenso SDK", "documenso API version".
allowed-tools
Read, Write, Edit, Bash(npm:*)
compatibility
Designed for Claude Code
version
1.14.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, documenso, api, migration

Documenso Upgrade & Migration

Output

  • A versioned upgrade record with compatibility, access/audit checks, staged evidence, and a verified rollback revision.
  • A paused/reversible release decision when any signing, authorization, or retention requirement regresses.

Examples

Upgrade in a development workspace using synthetic documents and signers, test the previous and target versions for lifecycle, callback, access, and audit behavior, then stage a canary. Retain the prior release/configuration and roll back immediately if a control fails; do not validate upgrades by changing live signed documents.

Current State

!npm list @documenso/sdk-typescript 2>/dev/null || echo 'SDK not installed' !npm list documenso-sdk-python 2>/dev/null || pip show documenso-sdk-python 2>/dev/null | head -3 || echo 'Python SDK not installed'

Overview

Guide for upgrading between Documenso API versions and SDK updates. Documenso has two API versions: v1 (legacy, document-centric) and v2 (recommended, envelope-based with multi-document support). The TypeScript and Python SDKs use the v2 API by default.

Prerequisites

  • Current Documenso integration working
  • Test environment available
  • Feature flag system (recommended for gradual rollout)

API Version Comparison

Featurev1 (legacy)v2 (recommended)
Base path/api/v1//api/v2/
Document modelDocumentsEnvelopes (can contain multiple documents)
SDK supportREST onlyTypeScript + Python SDK
Template API/templates/{id}/create-documentVia envelope create
AuthenticationAuthorization: BearerAuthorization: Bearer (same)
StatusMaintained, not deprecatedActively developed

Instructions

Step 1: Upgrade SDK to Latest
bash
# Check current version
npm list @documenso/sdk-typescript

# Upgrade
npm install @documenso/sdk-typescript@latest

# Check for breaking changes
npm info @documenso/sdk-typescript changelog

# Python
pip install --upgrade documenso-sdk-python
Step 2: v1 REST to v2 SDK Migration
typescript
// BEFORE: v1 REST API
const BASE = "https://app.documenso.com/api/v1";
const headers = { Authorization: `Bearer ${process.env.DOCUMENSO_API_KEY}` };

// Create document
const res = await fetch(`${BASE}/documents`, {
  method: "POST",
  headers: { ...headers, "Content-Type": "application/json" },
  body: JSON.stringify({ title: "Contract" }),
});
const doc = await res.json();

// List documents
const listRes = await fetch(`${BASE}/documents?page=1&perPage=20`, { headers });
const { documents } = await listRes.json();

// AFTER: v2 SDK
import { Documenso } from "@documenso/sdk-typescript";
const client = new Documenso({ apiKey: process.env.DOCUMENSO_API_KEY! });

// Create document
const doc = await client.documents.createV0({ title: "Contract" });

// List documents
const { documents } = await client.documents.findV0({ page: 1, perPage: 20 });
Show full SKILL.md (147 more words)Show less
Step 3: Gradual Migration with Feature Flags
typescript
// src/documenso/migration.ts
import { Documenso } from "@documenso/sdk-typescript";

const USE_V2 = process.env.DOCUMENSO_USE_V2 === "true";

export async function createDocument(title: string) {
  if (USE_V2) {
    const client = new Documenso({ apiKey: process.env.DOCUMENSO_API_KEY! });
    return client.documents.createV0({ title });
  }

  // Legacy v1
  const res = await fetch("https://app.documenso.com/api/v1/documents", {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.DOCUMENSO_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({ title }),
  });
  return res.json();
}

// Enable gradually:
// 1. DOCUMENSO_USE_V2=true in staging → test
// 2. DOCUMENSO_USE_V2=true for 10% of production traffic
// 3. Monitor error rates
// 4. Roll to 100%
// 5. Remove v1 code
Step 4: Self-Hosted Version Upgrade
bash
# Self-hosted Documenso upgrades are simple:
# 1. Pull new image
docker pull documenso/documenso:latest

# 2. Restart container (migrations run automatically on start)
docker compose -f docker-compose.prod.yml up -d documenso

# 3. Verify
docker logs documenso --tail 20 | grep "prisma migrate"
curl -s https://sign.yourcompany.com/api/health

# Rollback if needed:
docker compose -f docker-compose.prod.yml down documenso
docker pull documenso/documenso:previous-tag
docker compose -f docker-compose.prod.yml up -d documenso
Step 5: Migration Testing
typescript
// tests/migration/v1-v2-parity.test.ts
import { describe, it, expect } from "vitest";

describe("v1/v2 API Parity", () => {
  it("creates documents with same result shape", async () => {
    // Create via v1
    const v1Doc = await createDocumentV1("Parity Test");
    // Create via v2
    const v2Doc = await createDocumentV2("Parity Test");

    // Verify same essential fields
    expect(v1Doc.title).toBe(v2Doc.title);
    expect(typeof v1Doc.id).toBe("number");
    expect(typeof v2Doc.documentId).toBe("number");
  });

  it("lists documents consistently", async () => {
    const v1List = await listDocumentsV1();
    const v2List = await listDocumentsV2();

    // Same documents visible via both APIs
    expect(v1List.length).toBe(v2List.length);
  });
});

Migration Checklist

  • Current SDK version documented
  • Changelog reviewed for breaking changes
  • Feature branch created for migration
  • v2 SDK installed alongside v1 code
  • Feature flag for gradual rollout
  • Parity tests passing (v1 and v2 produce same results)
  • Staging fully tested on v2
  • Production rolled out gradually
  • v1 code removed after full rollout
  • Self-hosted: container upgraded and migrations verified

Error Handling

IssueCauseSolution
ID format mismatchv1 returns id, v2 returns documentIdUse adapter/mapping layer
Missing fieldAPI change in new versionUpdate to new field names
Enum case sensitivityv2 SDK uses uppercase enumsUse "SIGNER" not "signer"
Template API differencev1 templates vs v2 envelopesCheck API version for template operations

Resources

Next Steps

For CI/CD integration, see documenso-ci-integration.

© 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-upgrade-migration of jeremylongshore/tons-of-skills-marketplace.

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

Open the folder on GitHubat commit cfae287

Compare with similar skills

Documenso Upgrade Migration 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 Upgrade Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Documenso Upgrade Migration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.8kAutomated safety check: PassMIT
jscpd Code Migration Trackerkucherenko/jscpd6.4k—~5kAutomated safety check: PassMIT
Code Migrationanthropics/code-migration-kit-with-claude-code748—~983Automated safety check: PassCustom licence
RStudio Selenium to Playwright Migrationrstudio/rstudio5.1k—~3.6kAutomated safety check: PassCustom licence
Deprecated API UpdaterArabelaTso/Skills-4-SE253—~2.8kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • jscpd Code Migration Tracker

    kucherenko/jscpd

    Measures a code port between languages or frameworks with jscpd's function-level comparison, porting tests before code and tracking what is left unmatched.

    6.4k GitHub stars~5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Code Migration

    anthropics/code-migration-kit-with-claude-code

    Official

    Run a large-scale language migration with the six-step process: create the map and the rules, stress-test the rules, translate everything, compile, run it, match behavior.

    748 GitHub stars~983 tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • RStudio Selenium to Playwright Migration

    rstudio/rstudio

    Converts RStudio Python Selenium electron tests into TypeScript Playwright tests, checking each against a live RStudio before counting it as migrated.

    5.1k GitHub stars~3.6k tokensUpdated today
    Testing & QAAuto-check passed

  • Deprecated API Updater

    ArabelaTso/Skills-4-SE

    Identify and replace deprecated API usage in source code with modern alternatives.

    253 GitHub stars~2.8k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Convert Internal Package to TypeScript

    TryGhost/Ghost

    Moves a legacy internal Ghost package from JavaScript and CommonJS to TypeScript and ESM in three focused commits that keep git file history intact.

    56k GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed

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

Works with

Categories

Questions about Documenso Upgrade Migration

What does Documenso Upgrade Migration do?

Manage Documenso API version upgrades and SDK migrations. An agent skill from jeremylongshore/tons-of-skills-marketplace. Documenso Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Manage Documenso API version upgrades and SDK migrations.

When should I use Documenso Upgrade Migration?

Documenso Upgrade Migration fits situations like: upgrading from v1 to v2 API; updating SDK versions; migrating between Documenso versions; with phrases like documenso upgrade.

How do I install Documenso Upgrade Migration in Claude Code?

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

How do I install Documenso Upgrade Migration in Codex?

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

Can I use Documenso Upgrade Migration 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-upgrade-migration -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-upgrade-migration, .gemini/skills/documenso-upgrade-migration, .github/skills/documenso-upgrade-migration and .opencode/skills/documenso-upgrade-migration in your project.

What does Documenso Upgrade Migration need to run?

Going by SKILL.md and its folder, Documenso Upgrade Migration needs the command-line tools its instructions call (docker, npm, pip and curl) and credentials named DOCUMENSO_API_KEY. Our summary lists: Python 3; Node.js; Docker; A credential in DOCUMENSO_API_KEY. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(npm:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Documenso Upgrade Migration access the network?

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

Is Documenso Upgrade Migration 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 Upgrade Migration use?

Documenso Upgrade Migration 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 Upgrade Migration use?

About 1.8k tokens (SKILL.md is roughly 7.1k 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 1.7k tokens, read only when the agent opens those files.

What are the alternatives to Documenso Upgrade Migration?

Skills that share tags, products or a category with Documenso Upgrade Migration: jscpd Code Migration Tracker (kucherenko/jscpd, 6.4k stars), Code Migration (anthropics/code-migration-kit-with-claude-code, 748 stars), RStudio Selenium to Playwright Migration (rstudio/rstudio, 5.1k stars) and Deprecated API Updater (ArabelaTso/Skills-4-SE, 253 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Documenso Upgrade Migration?

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.