Agent skill · software engineering · jeremylongshore
lucidchart-ci-integration
Gate Lucid REST, Standard Import, and Extension API changes with deterministic checks. Use when adding CI to a Lucid integration. Trigger with "add Lucid CI".
Why this skill is useful
Adds a complete CI integration workflow for Lucidchart with executable scripts for unit and integration tests that validate API interactions.
What it needs
Requires node 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
Lucid Integration CI Gate Overview Build a secretless pull-request gate and a separately approved live verification lane for Lucid integrations. Prerequisites The integration kind: REST API, Standard Import, editor extension, or data connector Repository ownership rules and sanitized fixtures Current Lucid documentation for every API version, scope, and package command used Tool Discipline Use Read, Glob, and Grep to inspect manifests, import archives, code, tests, and workflows. Use WebFetch only for current official Lucid pages. Use Write or Edit only within the approved repository scope. Current Contract REST requests use Bearer authorization and a valid resource-specific Lucid-Api-Version. Standard Import archives contain document.json; their rendered result can change as the format evolves. Official extension builds use lucid-package; pull-request jobs do not need production tokens. Authentication Keep API keys, OAuth client secrets, access tokens, refresh tokens, authorization codes, and account tokens out of fork and pull-request jobs. A protected live lane may use only an approved secret, correct token type, least scopes, and exact redirect URI. Instructions 1. Classify the integration and list its authoritative manifest, schema, API-version, and scope inputs. 2. Inspect every workflow and fixture with Read, Glob, and Grep. 3. Add schema and archive checks for Standard Import, including unique IDs, required pages, media limits, and path safety. 4. For extensions, run the documented build and bundle commands in a pinned runtime and verify the manifest requests only used scopes. 5. Mock REST responses by endpoint and version; cover 401, 403, 429, 5xx, malformed payload, and timeout behavior. 6. Keep fork jobs synthetic. Put any live smoke test behind protected-environment approval and cleanup. 7. Save a redacted receipt naming inputs, versions, checks, and remaining manual verification. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lucidchart-ci-integration