Agent skill · software engineering · jeremylongshore
lucidchart-install-auth
Choose and configure the correct Lucid authentication model: API key, OAuth user token, or OAuth account token. Use when bootstrapping or repairing Lucid REST access. Trigger with "configure Lucid auth".
Why this skill is useful
Provides specific commands and setup instructions for integrating with the Lucidchart API that the AI wouldn't reliably generate on its own.
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
Lucid Installation and Authentication Overview Select the least-privilege credential class for the operation, configure a secretless local contract, and verify identity and scope without exposing credentials. Prerequisites The exact Lucid operation, resource owner, environment, and required scopes A registered OAuth application when user or account OAuth is selected An approved secret store and rotation owner Tool Discipline Use Read, Glob, and Grep to inspect configuration templates, WebFetch for current auth and scope contracts, and Write or Edit only for secretless examples or redacted receipts. Current Contract Lucid documents API keys, OAuth user tokens, and OAuth account tokens. OAuth applications use Authorization Code Flow. REST credentials are normally sent as Authorization: Bearer ...; an operation may also require a resource-specific Lucid-Api-Version header. Authentication Use an API key only where the current operation supports it and personal ownership is acceptable. Use OAuth user tokens for delegated user access and consented scopes. Use OAuth account tokens only for documented account-level use with administrator authorization. Never substitute a fabricated Lucid-Api-Key header or log authorization values. Instructions 1. Re-fetch authentication methods, the exact operation, access scopes, and headers. 2. Create an auth decision record: credential class, principal, resources, scopes, expiration, rotation, and revocation. 3. Inspect the project for hard-coded tokens, unsafe redirects, committed environment files, and mixed credential classes. 4. Define environment-variable names and a secret-provider interface without writing values. 5. For OAuth, validate exact redirect URIs, state handling, authorization-code exchange, secure token storage, refresh behavior, and revocation. 6. Present any app registration, consent, account grant, or secret creation for explicit approval. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lucidchart-install-auth