---
name: lucidchart-install-auth
description: '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".'
argument-hint: "[project-path] [auth-mode]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.8.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags: [ saas, lucidchart, authentication, oauth, api-key ]
model: inherit
effort: medium
compatibility: Designed for Claude Code; credential creation, OAuth registration, consent, and account-token grants require administrator or resource-owner approval
title: lucidchart-install-auth
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/lucidchart-install-auth
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/lucidchart-install-auth/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/lucidchart-install-auth`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/lucidchart-install-auth`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/lucidchart-install-auth) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/lucidchart-install-auth`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/lucidchart-install-auth --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/lucidchart-install-auth --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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. After credentials are provisioned outside the transcript, perform the smallest documented read-only verification and capture only status, principal class, scopes, and safe request identifiers.

## Approval Boundaries

Do not create keys, register or modify OAuth apps, authorize accounts, broaden scopes, or rotate/revoke credentials without the relevant owner.

## Output

Return auth decision, required scopes and headers, secretless configuration, verification receipt, rotation/revocation owner, and unresolved access gaps.

## Error Handling

| Condition | Response |
|---|---|
| Operation rejects a credential class | Re-check the operation-specific auth table; do not try random headers. |
| OAuth redirect or state validation fails | Stop the exchange and repair the application configuration. |
| Scope is insufficient | Request the narrow documented scope; never silently broaden consent. |

## Example

```text
mode=oauth-user; principal=user-delegated; scopes=verified-current-docs; token-output=redacted; smoke=pass
```

## Resources

- [Official documentation map](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/lucidchart-install-auth/references/official-docs.md)

## Next Steps

Test revocation and rotation in a non-production environment before depending on the credential operationally.
