Agent skill · software engineering · jeremylongshore
lucidchart-deploy-integration
Package, validate, stage, publish, and roll back a Lucid extension or data connector. Use when moving a tested Lucid integration beyond local development. Trigger with "deploy Lucid integration".
Why this skill is useful
Adds a complete Docker deployment script and health check for a Lucidchart integration that the AI wouldn't generate on its own.
What it needs
Requires docker, docker-compose, node installed locally. Requires lucid account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Governed Lucid Integration Deployment Overview Move a Lucid extension and any companion data connector through reproducible build, canary, publication, and rollback gates using current official tooling. Prerequisites A clean reviewed revision with passing local build, type, manifest, fixture, and secret scans Environment owners, approved scopes, release notes, canary users, and rollback artifact Current lucid-package and project-specific connector deployment instructions Tool Discipline Use Read, Glob, and Grep for repository and release evidence, WebFetch for current Lucid publication contracts, and Write or Edit only for local manifests, receipts, and release notes. Current Contract Lucid editor extensions use the official package CLI and Extension SDK. A data connector is a separately operated server component with its own identity, hosting, secrets, observability, and rollback. Verify installed CLI syntax rather than relying on cached commands. Authentication Separate developer, publisher, connector-runtime, and source-system identities. Keep credentials in approved secret stores; use least privilege and ensure rollback does not depend on an expired personal token. Instructions 1. Pin source revision, CLI/SDK versions, manifest, scopes, connector image, fixtures, and documentation. 2. Run the repository's secretless build, type, manifest, fixture, and compatibility gates. 3. Produce immutable extension and connector artifacts with checksums and provenance. 4. Compare requested scopes, OAuth redirects, data flows, and webhook behavior with the reviewed release. 5. Present artifact digests, target, canary cohort, expected mutations, monitoring, and rollback commands for approval. 6. After approval, upload or deploy only to the documented staging/developer target and run the canary. 7. Reconcile UI behavior, connector data, permissions, errors, and service health before production publication. 8. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lucidchart-deploy-integration--dea668