Agent skill · data analytics · jeremylongshore
lucidchart-debug-bundle
Assemble a redacted, reproducible Lucid integration diagnostic bundle. Use when an API, Standard Import, extension, export, or data connector failure needs escalation. Trigger with "build Lucid debug bundle".
Why this skill is useful
Adds an executable script that automates the collection of diagnostic data from the Lucidchart API, which is not commonly available in public documentation.
What it needs
Requires curl, jq, tar 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
Redacted Lucid Debug Bundle Overview Create a minimal evidence package that reproduces a Lucid failure while excluding credentials, sensitive document content, and unnecessary personal data. Prerequisites Incident identifier, time window, affected component, and expected behavior Approval to inspect relevant local artifacts and sanitized responses A clean output directory outside application source and secret stores Tool Discipline Use Read, Glob, and Grep to collect bounded evidence, WebFetch for current contract comparison, and Write or Edit only inside the declared bundle directory. Current Contract Useful evidence differs by surface: REST requests need method, path family, safe headers, status and request identifiers; Standard Import needs archive structure and sanitized samples; extensions/connectors need versions, manifests, build output, and minimal fixtures. Authentication Never copy Authorization, cookies, API keys, OAuth codes, refresh tokens, client secrets, signed URLs, or raw environment files. Replace sensitive identifiers consistently so relationships remain diagnosable. Instructions 1. Declare incident scope, bundle path, retention, recipients, and exclusion rules. 2. Inventory candidate files and reject caches, dependencies, binaries, full documents, and unrelated logs by default. 3. Capture tool and SDK versions, safe manifest fields, operation category, sanitized request/response metadata, and exact timestamps. 4. For imports, include a structurally equivalent minimal archive or manifest—not protected production content. 5. For extension/connector failures, add a synthetic fixture and the smallest failing build/test receipt. 6. Scan recursively for token patterns, credentials, emails, personal data, and document content; manually review hits. 7. Write a manifest with file digests, provenance, redactions, reproduction steps, expected/actual behavior, and gaps. 8. Obtain approval before transmitting; record destination and deletion date. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lucidchart-debug-bundle