lucidchart-upgrade-migration
Upgrade Migration for Lucidchart. Trigger: "lucidchart upgrade migration".
Best use case
lucidchart-upgrade-migration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Upgrade Migration for Lucidchart. Trigger: "lucidchart upgrade migration".
Teams using lucidchart-upgrade-migration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/lucidchart-upgrade-migration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How lucidchart-upgrade-migration Compares
| Feature / Agent | lucidchart-upgrade-migration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Upgrade Migration for Lucidchart. Trigger: "lucidchart upgrade migration".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Lucidchart Upgrade & Migration
## Overview
Lucidchart (Lucid) provides a diagramming and visual collaboration platform with APIs for document management, shape manipulation, and data linking. The API uses version headers and evolves its document schema, shape library definitions, and permission models. Tracking API versions is critical because Lucid's document format changes affect embedded diagram exports, shape coordinate systems shift between API versions, and breaking changes to the data linking API can corrupt live-data diagrams connected to external databases.
## Version Detection
```typescript
const LUCID_BASE = "https://api.lucid.co/v1";
async function detectLucidApiVersion(apiKey: string): Promise<void> {
const res = await fetch(`${LUCID_BASE}/documents`, {
headers: {
Authorization: `Bearer ${apiKey}`,
"Lucid-Api-Version": "2",
"Content-Type": "application/json",
},
});
const serverVersion = res.headers.get("x-lucid-api-version") ?? "unknown";
const minSupported = res.headers.get("x-lucid-min-version");
console.log(`Lucid API version: ${serverVersion}, min supported: ${minSupported}`);
// Check if current version header is being accepted or forced up
const requestedVersion = "2";
if (serverVersion !== requestedVersion) {
console.warn(`Requested v${requestedVersion} but server responded with v${serverVersion}`);
}
const deprecation = res.headers.get("x-lucid-deprecation-notice");
if (deprecation) console.warn(`Deprecation: ${deprecation}`);
}
```
## Migration Checklist
- [ ] Review Lucid developer changelog for API version bumps
- [ ] Update `Lucid-Api-Version` header in all API calls to target version
- [ ] Audit document export code — SVG/PNG render parameters may change
- [ ] Verify shape library IDs are still valid (deprecated shapes removed)
- [ ] Check document permission model for new sharing/access level fields
- [ ] Update data linking configuration if external data source schema changed
- [ ] Test page/layer structure — nested page support may affect document queries
- [ ] Validate webhook event payloads for document change notifications
- [ ] Check if coordinate system units changed (points vs. pixels)
- [ ] Run export comparison: render same document with old and new API versions
## Schema Migration
```typescript
// Lucid document schema: flat shape list → page-grouped shape hierarchy
interface OldDocument {
id: string;
title: string;
shapes: Array<{ id: string; type: string; x: number; y: number; width: number; height: number; text?: string }>;
lastModified: string;
}
interface NewDocument {
id: string;
title: string;
pages: Array<{
id: string;
title: string;
layers: Array<{
id: string;
shapes: Array<{
id: string;
type: string;
bounds: { x: number; y: number; width: number; height: number };
text?: { content: string; style: Record<string, any> };
}>;
}>;
}>;
lastModified: string;
version: number;
}
function migrateDocument(old: OldDocument): NewDocument {
return {
id: old.id,
title: old.title,
pages: [{
id: "page-1",
title: "Page 1",
layers: [{
id: "layer-1",
shapes: old.shapes.map((s) => ({
id: s.id,
type: s.type,
bounds: { x: s.x, y: s.y, width: s.width, height: s.height },
text: s.text ? { content: s.text, style: {} } : undefined,
})),
}],
}],
lastModified: old.lastModified,
version: 2,
};
}
```
## Rollback Strategy
```typescript
class LucidClient {
private apiVersion: number;
constructor(private apiKey: string, version: number = 2) {
this.apiVersion = version;
}
async getDocument(docId: string): Promise<any> {
try {
const res = await fetch(`https://api.lucid.co/v1/documents/${docId}`, {
headers: {
Authorization: `Bearer ${this.apiKey}`,
"Lucid-Api-Version": String(this.apiVersion),
},
});
if (!res.ok) throw new Error(`Lucid API ${res.status}`);
return await res.json();
} catch (err) {
if (this.apiVersion > 1) {
console.warn(`Falling back Lucid API from v${this.apiVersion} to v${this.apiVersion - 1}`);
this.apiVersion -= 1;
return this.getDocument(docId);
}
throw err;
}
}
}
```
## Error Handling
| Migration Issue | Symptom | Fix |
|----------------|---------|-----|
| API version header missing | `400` with `Lucid-Api-Version header required` | Add `Lucid-Api-Version` header to all requests |
| Shape ID format changed | `404` when referencing shapes by old numeric ID | Migrate to new UUID-based shape identifiers |
| Document export dimensions wrong | SVG exports render at unexpected scale | Check if coordinate units changed from points to pixels in new version |
| Data link schema invalid | `422` on data linking update | Re-map external data columns to new document field schema |
| Permission model expanded | `403` on previously accessible documents | Request updated OAuth scopes for new permission levels |
## Resources
- [Lucid Developer Portal](https://developer.lucid.co/reference/overview)
- [Lucid API Changelog](https://developer.lucid.co/changelog)
## Next Steps
For CI pipeline integration, see `lucidchart-ci-integration`.Related Skills
workhuman-upgrade-migration
Workhuman upgrade migration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman upgrade migration".
wispr-upgrade-migration
Wispr Flow upgrade migration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr upgrade migration".
windsurf-upgrade-migration
Upgrade Windsurf IDE, migrate settings from VS Code or Cursor, and handle breaking changes. Use when upgrading Windsurf versions, migrating from another editor, or handling configuration changes after updates. Trigger with phrases like "upgrade windsurf", "windsurf update", "migrate to windsurf", "windsurf from cursor", "windsurf from vscode".
windsurf-migration-deep-dive
Migrate to Windsurf from VS Code, Cursor, or other AI IDEs with full configuration transfer. Use when migrating a team to Windsurf, transferring Cursor rules, or evaluating Windsurf against other AI editors. Trigger with phrases like "migrate to windsurf", "switch to windsurf", "windsurf from cursor", "windsurf from copilot", "windsurf evaluation".
webflow-upgrade-migration
Analyze, plan, and execute Webflow SDK upgrades (webflow-api v1 to v3) with breaking change detection, API v1-to-v2 migration, and deprecation handling. Trigger with phrases like "upgrade webflow", "webflow migration", "webflow breaking changes", "update webflow SDK", "webflow v1 to v2".
webflow-migration-deep-dive
Execute major Webflow migrations — from other CMS platforms to Webflow CMS, between Webflow sites, or large-scale content re-architecture using the Data API v2 bulk endpoints, strangler fig pattern, and data validation. Trigger with phrases like "migrate to webflow", "webflow migration", "import into webflow", "webflow replatform", "move content to webflow", "webflow bulk import", "wordpress to webflow".
vercel-upgrade-migration
Upgrade Vercel CLI, Node.js runtime, and Next.js framework versions with breaking change detection. Use when upgrading Vercel CLI versions, migrating Node.js runtimes, or updating Next.js between major versions on Vercel. Trigger with phrases like "upgrade vercel", "vercel migration", "vercel breaking changes", "update vercel CLI", "next.js upgrade on vercel".
vercel-migration-deep-dive
Migrate to Vercel from other platforms or re-architecture existing Vercel deployments. Use when migrating from Netlify, AWS, or Cloudflare to Vercel, or when re-platforming an existing Vercel application. Trigger with phrases like "migrate to vercel", "vercel migration", "switch to vercel", "netlify to vercel", "aws to vercel", "vercel replatform".
veeva-upgrade-migration
Veeva Vault upgrade migration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva upgrade migration".
veeva-migration-deep-dive
Veeva Vault migration deep dive for enterprise operations. Use when implementing advanced Veeva Vault patterns. Trigger: "veeva migration deep dive".
vastai-upgrade-migration
Upgrade Vast.ai CLI, migrate API versions, and handle breaking changes. Use when upgrading vastai CLI, detecting deprecations, or migrating between API versions. Trigger with phrases like "upgrade vastai", "vastai migration", "vastai breaking changes", "update vastai CLI".
vastai-migration-deep-dive
Migrate GPU workloads to or from Vast.ai, or between GPU providers. Use when switching from AWS/GCP/Azure GPU instances to Vast.ai, migrating between GPU types, or re-platforming ML infrastructure. Trigger with phrases like "migrate to vastai", "vastai migration", "switch to vastai", "vastai from aws", "vastai from lambda".