Agent skill

Lucidchart Upgrade Migration

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

Plan and execute a reversible Lucid SDK, CLI, manifest, API-version, Standard Import, or connector migration.

MITAuto-check passedDevOps & Cloud

Install Lucidchart Upgrade Migration

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

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

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

At a glance

Plan and execute a reversible Lucid SDK, CLI, manifest, API-version, Standard Import, or connector migration.

  • Works in 8 steps: Inventory current and target package/CLI… → Capture a clean baseline: build, types,… → Re-fetch exact official docs and inspect… → …
  • A Lucid integration has dependency
  • SKILL.md covers Overview, Prerequisites, Tool Discipline and Current Contract, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Lucidchart Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".

Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; dependency mutation, API-version changes, data migration, installation, and production rollout require owner approval

It sits in DevOps & Cloud. 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

  • A Lucid integration has dependency
  • With upgrade Lucid integration

Example prompts

  • “upgrade Lucid integration”
  • “/lucidchart-upgrade-migration”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code; dependency mutation, API-version changes, data migration, installation, and production rollout require owner approval
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, Write, Edit

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Inventory current and target package/CLI versions, API-version headers, manifests/scopes, import fixtures, connector schemas, and…
  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. Test old/new representative fixtures and compare rendering, data, identifiers, errors, and performance.
  8. Deploy a bounded canary after approval; reconcile, monitor, and roll back on threshold breach before broader promotion.

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
    • Glob
    • Grep
    • WebFetch
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

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

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

  • Compatibility

    Designed for Claude Code; dependency mutation, API-version changes, data migration, installation, and production rollout require owner approval

    From compatibility in the SKILL.md frontmatter.

Context cost

Lucidchart Upgrade Migration loads about 989 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 61 tokens; SKILL.md has 393 words of instructions outside code blocks.

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

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). 393 words, ~989 tokens.

Download SKILL.mdSave it as .claude/skills/lucidchart-upgrade-migration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
lucidchart-upgrade-migration
description
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".
allowed-tools
Read, Glob, Grep, WebFetch, Write, Edit
compatibility
Designed for Claude Code; dependency mutation, API-version changes, data migration, installation, and production rollout require owner approval
argument-hint
[project-path] [target-version]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
saas, lucidchart, migration, upgrades, compatibility
model
inherit
effort
high

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. Test old/new representative fixtures and compare rendering, data, identifiers, errors, and performance.
  8. Deploy a bounded canary after approval; reconcile, monitor, and roll back on threshold breach before broader promotion.
Show full SKILL.md (112 more words)Show less

Approval Boundaries

Do not upgrade packages, change API versions/scopes, rewrite stored data, reinstall extensions, or deploy merely because a newer version exists.

Output

Return baseline/target matrix, official evidence, changed files, dependency and scope diffs, tests, canary, rendering/data variance, approval, and rollback status.

Error Handling

ConditionResponse
Target types remove a used APIStop and redesign with supported primitives; do not conceal it with casts.
Import renders differentlyPreserve both artifacts, quantify variance, and require owner acceptance.
Rollback changes data/schemaTest a forward repair and recovery copy before rollout.

Example

text
axis=sdk; baseline=locked; target=reviewed; fixture-parity=pass; scope-delta=none; canary=not-approved

Resources

Next Steps

Promote only after canary parity, explicit acceptance of known variance, and tested rollback from the exact artifact.

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

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Lucidchart 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.

Lucidchart Upgrade Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lucidchart Upgrade Migration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~989Automated safety check: PassMIT
Monitor CInrwl/nx29k6 repos~4.7kAutomated safety check: PassMIT
Terraform and OpenTofu Guideagentscope-ai/QwenPaw36k6 repos~4.2kAutomated safety check: PassApache-2.0
Vercel Optimize Auditvercel-labs/agent-skills32k8 repos~4.3kAutomated safety check: PassNone
Analyze GitHub Action Logswithastro/astro63k1 repos~1.3kAutomated safety check: PassCustom licence
Openclaw Live Updateropenclaw/openclaw392k—~3.7kAutomated safety check: PassMIT

Similar skills

  • Monitor CI

    nrwl/nx

    Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.

    29k GitHub starsUsed in 6 repos~4.7k tokens
    DevOps & CloudAuto-check passed
  • Terraform and OpenTofu Guide

    agentscope-ai/QwenPaw

    Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.

    36k GitHub starsUsed in 6 repos~4.2k tokens
    DevOps & CloudAuto-check passed
  • Vercel Optimize Audit

    vercel-labs/agent-skills

    Official

    Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.

    32k GitHub starsUsed in 8 repos~4.3k tokens
    DevOps & CloudAuto-check passed
  • Official

    Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.

    63k GitHub starsUsed in 1 repo~1.3k tokens
    DevOps & CloudAuto-check passed
  • Openclaw Live Updater

    openclaw/openclaw

    Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.

    392k GitHub stars~3.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Docs Learn PR Preview

    netdata/netdata

    Use only when the user explicitly asks to build, run, preview, inspect, or validate learn.netdata.cloud locally using the contents of a PR or documentation branch before merge.

    81k GitHub stars~2k tokensUpdated today
    DevOps & CloudAuto-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

Categories

Questions about Lucidchart Upgrade Migration

What does Lucidchart Upgrade Migration do?

Plan and execute a reversible Lucid SDK, CLI, manifest, API-version, Standard Import, or connector migration. Lucidchart Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Plan and execute a reversible Lucid SDK, CLI, manifest, API-version, Standard Import, or connector migration.

When should I use Lucidchart Upgrade Migration?

Lucidchart Upgrade Migration fits situations like: A Lucid integration has dependency; with upgrade Lucid integration.

How do I install Lucidchart Upgrade Migration in Claude Code?

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

How do I install Lucidchart Upgrade Migration in Codex?

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

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

What does Lucidchart Upgrade Migration need to run?

SKILL.md names no scripts, command-line tools or credentials: Lucidchart Upgrade Migration is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; dependency mutation, API-version changes, data migration, installation, and production rollout require owner approval.

Does Lucidchart Upgrade Migration access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

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

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

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

What are the alternatives to Lucidchart Upgrade Migration?

Skills that share tags, products or a category with Lucidchart Upgrade Migration: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 36k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Analyze GitHub Action Logs (withastro/astro, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lucidchart 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.