Agent skill · software engineering · jeremylongshore
lucidchart-core-workflow-a
Create and verify a Lucidchart document through the documented Standard Import REST workflow. Use when generating a diagram from governed data. Trigger with "create Lucid document".
Why this skill is useful
Adds executable scripts for creating, editing, and exporting Lucidchart documents using the Lucid REST API that aren't available in public documentation.
What it needs
Requires npm 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
Governed Lucid Standard Import Overview Transform an approved diagram specification into a deterministic .lucid archive, create the document, verify it, and retain rollback evidence. Prerequisites An approved diagram specification with data classification and owner A destination product and folder An authorized API key or OAuth user token with the exact create-document scope Tool Discipline Use Read, Glob, and Grep to inspect specifications and fixtures, WebFetch for current Standard Import and operation contracts, and Write or Edit for the local archive source and receipt only. Current Contract A Standard Import file is a ZIP with required document.json, at least one page, and unique item IDs. Creation uses the documented multipart endpoint with file, product, and optional title or parent. The format evolves, so a previously valid archive may render differently later. Authentication Use Bearer authorization with an approved API key or OAuth user token accepted by the operation. Never print the token. Validate token type, scope, destination access, and current document API version before mutation. Instructions 1. Freeze the input specification, intended product, folder, title, ownership, and rollback plan. 2. Build document.json and any /data or /images assets with unique stable IDs and safe relative paths. 3. Validate JSON, ZIP structure, uncompressed sizes, media types, referential integrity, and deterministic ordering locally. 4. Present a mutation preview including document count, pages, shapes, lines, data rows, images, and destination. 5. After approval, submit one idempotency-controlled creation request using exact documented headers and multipart fields. 6. Capture the returned identity without tokens, then retrieve or export only as permitted to verify representative content. 7. Record source digest, created ID, owner, verification, cleanup or retention decision, and rendering variance. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lucidchart-core-workflow-a