Agent skill · software engineering · jeremylongshore
lucidchart-upgrade-migration
Plan and execute a reversible Lucid SDK, CLI, manifest, API-version, Standard Import, or connector migration. Use when a Lucid integration has dependency or contract drift. Trigger with "upgrade Lucid integration".
Why this skill is useful
Adds executable scripts for Lucidchart API version detection and document migration that are not available in public documentation.
What it needs
Requires typescript installed locally. Requires lucidchart account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Reversible Lucid Upgrade and Migration Overview Move one Lucid contract boundary at a time with an immutable baseline, representative fixtures, canary evidence, and tested rollback. Prerequisites Clean source revision, dependency lockfile, manifests, deployed artifact identity, and current production version Representative synthetic imports, documents, data, and connector events where applicable Owners for code, data, Lucid application, source system, and rollback Tool Discipline Use Read, Glob, and Grep for version and usage inventory, WebFetch for current official migration contracts, and Write or Edit only for approved local changes, tests, and receipts. Current Contract The Standard Import format evolves and may render differently over time. Extension SDK/CLI and manifest behavior are versioned through project dependencies. REST resources may require Lucid-Api-Version. These are separate migration axes and must not be changed blindly together. Authentication Preserve credential classes and least scopes unless a documented target contract requires change. Treat new scopes, redirect URIs, consent, account grants, and secret rotation as separate approved migrations. Instructions 1. Inventory current and target package/CLI versions, API-version headers, manifests/scopes, import fixtures, connector schemas, and deployment artifacts. 2. Capture a clean baseline: build, types, manifests, tests, fixture imports/exports, data reconciliation, and rollback. 3. Re-fetch exact official docs and inspect target installed types/changelogs; create a breaking-change matrix. 4. Split changes into reversible steps: tooling/dependencies, compile fixes, manifest/scopes, format/schema, API version, and deployment. 5. Present dependency edits and any auth/data contract changes for approval. 6. Apply one step, regenerate the lockfile with the project package manager, and run narrow then full affected gates. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lucidchart-upgrade-migration