Agent skill · software engineering · jeremylongshore
lucidchart-performance-tuning
Measure and improve Lucid Standard Import, export, editor extension, or data connector performance without weakening correctness. Use when Lucid workflows are slow or resource-heavy. Trigger with "optimize Lucid performance".
Why this skill is useful
Adds executable scripts for caching, batching, and pagination strategies specific to Lucidchart API integration.
What it needs
Requires node, redis 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
Evidence-Driven Lucid Performance Tuning Overview Tune one measured workflow at a time while preserving document fidelity, data reconciliation, authorization, and documented limits. Prerequisites A reproducible scenario, representative sanitized fixture, baseline, and service objective Component classification: import, export, REST operation, editor extension, or connector Owners for data correctness and any live environment Tool Discipline Use Read, Glob, and Grep for code, fixtures, and receipts, WebFetch for current limits/contracts, and Write or Edit only for local benchmarks, scoped improvements, and reports. Current Contract Each Lucid surface has different constraints. Standard Import performance depends on archive structure, uncompressed assets, pages, objects, and data; extension/connector performance depends on the installed SDK, transforms, network behavior, and UI work. Rate limits are endpoint-specific. Authentication Benchmark offline first. Use dedicated test credentials and synthetic data for live measurements. Never log tokens or expose restricted document data in traces. Instructions 1. Define the user-visible objective and correctness invariants before measuring. 2. Record versions, fixture digest, cold/warm state, network assumptions, concurrency, and timing method. 3. Establish at least three comparable baseline samples with latency distribution and resource counts. 4. Profile the dominant phase: archive generation/upload/render, export polling/download, extension transform/UI, or connector fetch/reconcile. 5. Propose one reversible change such as bounded batching, deduplication, incremental reconciliation, asset reduction, caching with invalidation, or deferred UI work. 6. Run the same samples and compare latency, memory, requests, payload, rejects, document fidelity, and reconciliation. 7. Present any live load increase or concurrency change for approval; honor endpoint-specific limits and backpressure. 8. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lucidchart-performance-tuning--3db1a0