Agent skill

Lucidchart Security Basics

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Threat-model and harden Lucid API, Standard Import, editor extension, and data connector integrations.

MITAuto-check passedSecurity

Install Lucidchart Security Basics

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill lucidchart-security-basics -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace lucidchart-security-basics --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/lucidchart-security-basics .claude/skills/lucidchart-security-basics && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lucidchart-security-basics
GitHub stars
2.8k
Token cost
~1k tokens
SKILL.md length
376 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Threat-model and harden Lucid API, Standard Import, editor extension, and data connector integrations.

  • Works in 8 steps: Pin the reviewed revision and enumerate… → Re-fetch authentication, scope, header,… → Search tracked files and build artifacts… → …
  • Reviewing secrets
  • SKILL.md covers Overview, Prerequisites, Tool Discipline and Current Contract, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Lucidchart Security Basics is an agent skill from jeremylongshore/tons-of-skills-marketplace. Threat-model and harden Lucid API, Standard Import, editor extension, and data connector integrations. Use when reviewing secrets, scopes, data flows, or release security. Trigger with "secure Lucid integration".

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; credential, scope, data-retention, publication, and production-remediation decisions require security and resource-owner approval

It sits in Security, covering Threat modeling. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Reviewing secrets
  • Release security
  • With secure Lucid integration

Example prompts

  • “secure Lucid integration”
  • “/lucidchart-security-basics”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code; credential, scope, data-retention, publication, and production-remediation decisions require security and resource-owner approval
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, Write, Edit

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Pin the reviewed revision and enumerate actors, components, data stores, network edges, documents, and source systems.
  2. Re-fetch authentication, scope, header, and surface-specific official docs.
  3. Search tracked files and build artifacts for credentials, unsafe environment files, overly broad scopes, sensitive fixtures, and…
  4. Threat-model credential theft, malicious imports, archive traversal/expansion, injected source data, cross-account access, connector…
  5. Validate inputs, archive paths/sizes/types, stable IDs, outputs, redirects, state, authorization, tenant boundaries, and redaction.
  6. Verify pinned dependencies, reproducible builds, artifact provenance, change review, secretless CI, and rollback.
  7. Rank findings by exploitability and impact; propose reversible fixes with owners and evidence.
  8. Present credential, scope, retention, or production changes for explicit approval and verify remediation independently.

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • WebFetch
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code; credential, scope, data-retention, publication, and production-remediation decisions require security and resource-owner approval

    From compatibility in the SKILL.md frontmatter.

Context cost

Lucidchart Security Basics loads about 1k tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 376 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 376 words, ~1,001 tokens.

Download SKILL.mdSave it as .claude/skills/lucidchart-security-basics/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
lucidchart-security-basics
description
Threat-model and harden Lucid API, Standard Import, editor extension, and data connector integrations. Use when reviewing secrets, scopes, data flows, or release security. Trigger with "secure Lucid integration".
allowed-tools
Read, Glob, Grep, WebFetch, Write, Edit
compatibility
Designed for Claude Code; credential, scope, data-retention, publication, and production-remediation decisions require security and resource-owner approval
argument-hint
[project-path] [surface]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
saas, lucidchart, security, oauth, least-privilege
model
inherit
effort
high

Lucid Integration Security Baseline

Overview

Establish least privilege, safe data handling, trustworthy package boundaries, and auditable operations for the exact Lucid integration surface.

Prerequisites

  • Architecture and data-flow inventory with classifications and owners
  • Credential/principal and extension-scope inventory
  • Repository, artifact, deployment, logging, retention, and incident evidence

Tool Discipline

Use Read, Glob, and Grep for bounded static inspection, WebFetch for current Lucid security contracts, and Write or Edit only for approved local remediation and redacted reports.

Current Contract

Lucid exposes multiple credential classes, operation-specific scopes/headers, Standard Import archives, editor-extension scopes, and optional connector runtimes. Each creates distinct trust boundaries; an extension bundle is not a safe place for confidential credentials.

Authentication

Map API keys and OAuth user/account tokens to an owner, exact scopes/resources, storage, expiration, rotation, revocation, and audit trail. Validate OAuth redirect URIs and state. Never log tokens, authorization codes, refresh tokens, cookies, or signed URLs.

Instructions

  1. Pin the reviewed revision and enumerate actors, components, data stores, network edges, documents, and source systems.
  2. Re-fetch authentication, scope, header, and surface-specific official docs.
  3. Search tracked files and build artifacts for credentials, unsafe environment files, overly broad scopes, sensitive fixtures, and unredacted logs.
  4. Threat-model credential theft, malicious imports, archive traversal/expansion, injected source data, cross-account access, connector compromise, replay, and supply-chain drift.
  5. Validate inputs, archive paths/sizes/types, stable IDs, outputs, redirects, state, authorization, tenant boundaries, and redaction.
  6. Verify pinned dependencies, reproducible builds, artifact provenance, change review, secretless CI, and rollback.
  7. Rank findings by exploitability and impact; propose reversible fixes with owners and evidence.
  8. Present credential, scope, retention, or production changes for explicit approval and verify remediation independently.
Show full SKILL.md (108 more words)Show less

Approval Boundaries

Do not inspect secret values, rotate/revoke credentials, alter scopes, delete data, change retention, or publish security-sensitive changes without authorization.

Output

Return surfaces, trust boundaries, principal/scope matrix, findings with evidence, severity, remediation, approvals, verification, and residual risk.

Error Handling

ConditionResponse
Active secret appears in tracked dataStop exposure, avoid repeating it, and escalate rotation through the owner.
Scope requirement is unclearDeny the capability until the exact documented scope is established.
Archive or source data is untrustedQuarantine and validate offline before any upload or rendering.

Example

text
surface=extension+connector; critical=0; high=1; bundle-secrets=0; least-scope=partial; production-mutations=0

Resources

Next Steps

Remediate highest-risk findings, rotate through accountable owners, and rerun the same evidence-backed checks.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/lucidchart-security-basics of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Lucidchart Security Basics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lucidchart Security Basics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lucidchart Security Basics this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1kAutomated safety check: PassMIT
Vuln Scanhashgraph-online/awesome-codex-plugins1.3k—~1.9kAutomated safety check: PassApache-2.0
Security And Hardeningpenpot/penpot61k6 repos~4.7kAutomated safety check: NotesMPL-2.0
Forensifyalexgreensh/repo-forensics190—~2.5kAutomated safety check: NotesCustom licence
Create Rulecartography-cncf/cartography4.1k—~3kAutomated safety check: PassApache-2.0
Security and Hardeningaddyosmani/agent-skills105k1 repos~4.4kAutomated safety check: NotesMIT

Similar skills

  • Vuln Scan

    hashgraph-online/awesome-codex-plugins

    Systematic vulnerability scan across injection, auth, data exposure, and dependencies — traced by reading code, not grepping for keywords.

    1.3k GitHub stars~1.9k tokensUpdated yesterday
    SecurityAuto-check passed
  • Hardens code against vulnerabilities. An agent skill from penpot/penpot.

    61k GitHub starsUsed in 6 repos~4.7k tokens
    SecurityAuto-check: notes
  • Forensify

    alexgreensh/repo-forensics

    Cross-agent self-inspection of your AI-agent stack. An agent skill from alexgreensh/repo-forensics.

    190 GitHub stars~2.5k tokensUpdated 14 days ago
    SecurityAuto-check: notes
  • Create Rule

    cartography-cncf/cartography

    Author a Cartography security rule (one or more Cypher Facts plus a Pydantic Finding output model) under cartography/rules/data/rules/.

    4.1k GitHub stars~3k tokensUpdated today
    SecurityAuto-check passed
  • Security and Hardening

    addyosmani/agent-skills

    Applies a threat-model-first approach to web code that handles untrusted input, authentication, data storage, dependencies or personal data.

    105k GitHub starsUsed in 1 repo~4.4k tokens
    SecurityAuto-check: notes
  • Commit Security Scan

    codexstar69/bug-hunter

    Scan code changes for security vulnerabilities using Bug Hunter-native artifacts and STRIDE context.

    520 GitHub stars~629 tokensUpdated 1 mo ago
    SecurityAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Lucidchart Security Basics

What does Lucidchart Security Basics do?

Threat-model and harden Lucid API, Standard Import, editor extension, and data connector integrations. Lucidchart Security Basics is an agent skill from jeremylongshore/tons-of-skills-marketplace. Threat-model and harden Lucid API, Standard Import, editor extension, and data connector integrations.

When should I use Lucidchart Security Basics?

Lucidchart Security Basics fits situations like: reviewing secrets; release security; with secure Lucid integration.

How do I install Lucidchart Security Basics in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lucidchart-security-basics -a claude-code`. Or copy the skill folder (skills/.curated/lucidchart-security-basics in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/lucidchart-security-basics in your project. Claude Code loads it when a task matches its description.

How do I install Lucidchart Security Basics in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lucidchart-security-basics -a codex`. Or copy the skill folder (skills/.curated/lucidchart-security-basics in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/lucidchart-security-basics in your project. Codex loads it when a task matches its description.

Can I use Lucidchart Security Basics in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill lucidchart-security-basics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lucidchart-security-basics, .gemini/skills/lucidchart-security-basics, .github/skills/lucidchart-security-basics and .opencode/skills/lucidchart-security-basics in your project.

What does Lucidchart Security Basics need to run?

SKILL.md names no scripts, command-line tools or credentials: Lucidchart Security Basics is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; credential, scope, data-retention, publication, and production-remediation decisions require security and resource-owner approval.

Does Lucidchart Security Basics access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Lucidchart Security Basics safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Lucidchart Security Basics use?

Lucidchart Security Basics is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lucidchart Security Basics use?

About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 266 tokens, read only when the agent opens those files.

What are the alternatives to Lucidchart Security Basics?

Skills that share tags, products or a category with Lucidchart Security Basics: Vuln Scan (hashgraph-online/awesome-codex-plugins, 1.3k stars), Security And Hardening (penpot/penpot, 61k stars), Forensify (alexgreensh/repo-forensics, 190 stars) and Create Rule (cartography-cncf/cartography, 4.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lucidchart Security Basics?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.