Agent skill · marketing growth · jeremylongshore
lucidchart-core-workflow-b
Build and verify a Lucid editor extension that imports or synchronizes governed data. Use when connecting an approved data source to Lucidchart. Trigger with "sync data to Lucidchart".
Why this skill is useful
Adds specific API commands for managing Lucidchart document collaboration and permissions that the AI wouldn't reliably generate on its own.
What it needs
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
Governed Lucid Data Import and Sync Overview Design an editor extension, and only when required a data connector, that imports or synchronizes approved data without inventing REST endpoints. Prerequisites A classified source schema, stable record identifiers, and named data owner A Lucid developer application and explicit extension scopes A reconciliation, deletion, and rollback policy Tool Discipline Use Read, Glob, and Grep to inspect extension code and schemas, WebFetch for current Lucid contracts, and Write or Edit only for local implementation and evidence. Current Contract Lucid documents support data through the Extension API. Data connectors are an optional server-side companion for sources that require OAuth, scheduled updates, or webhook-driven refresh. Consult installed SDK types and official docs rather than guessing namespaces or methods. Authentication Keep source-system credentials server-side. Request the least Lucid extension scopes and OAuth access required. Never place API keys, refresh tokens, or client secrets in extension bundles, logs, fixtures, or document data. Instructions 1. Classify the job as one-time import, user-triggered refresh, scheduled sync, or webhook-assisted connector sync. 2. Map source keys, field types, null handling, redaction, row ownership, and conflict policy before writing code. 3. Inspect the installed lucid-extension-sdk types and current data-import documentation. 4. Implement a deterministic transform with stable IDs and explicit validation errors. 5. Test against synthetic fixtures, including duplicate, deleted, reordered, and malformed records. 6. Present the intended scopes, data movement, write count, destination, and rollback before live access. 7. After approval, run a bounded canary and reconcile source, Lucid data, visual bindings, and deletions. 8. Record fixture digest, scope set, counts, rejects, drift, and rollback result. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lucidchart-core-workflow-b--646412