Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/lucidchart-install-auth

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/lucidchart-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈57 tokens for metadata: the name and description. ≈806 when used: this file. ≈233 more on demand in 1 file.

Description uses 2.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈229 characters, or 2.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

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

Resources

Next Steps

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

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides standard instructions for installing and authenticating with the Lucidchart API. It follows best practices for secret management by suggesting the use of environment variables and .env files for storing credentials.

  • Socket2mo

    1 alert: gptAnomaly

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[project-path] [auth-mode]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
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

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/lucidchart-install-auth