Individual skill
lucidchart-common-errors
Triage Lucid authentication, scope, version, import, export, extension, and connector failures from bounded evidence. Use when a Lucid integration fails. Trigger with "troubleshoot Lucid".
skills/.curated/lucidchart-common-errors/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,917
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- saas Declared skill tag
- lucidchart Declared skill tag
- troubleshooting Declared skill tag
- oauth Declared skill tag
- diagnostics Declared skill tag
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,588 bytesreferences/official-docs.mddoc · 928 bytes
Read excerpt
# Lucid Integration Error Triage
## Overview
Identify the failing layer before changing credentials, scopes, documents, packages, or connector state.
## Prerequisites
- A redacted request ID, timestamp, status, integration kind, endpoint or command, and API/package version
- Expected token type and scopes from the exact official operation page
- Permission to inspect the relevant repository and Lucid project
## Tool Discipline
Use `Read`, `Glob`, and `Grep` for local evidence, `WebFetch` for official Lucid contracts and status, and `Write` or `Edit` only for approved fixes or redacted receipts.