Agent skill · data analytics · jeremylongshore
lucidchart-cost-tuning
Review Lucid licensing, seats, plan capabilities, and integration operating effort without fabricating usage prices. Use when controlling Lucidchart total cost or right-sizing access. Trigger with "reduce Lucidchart cost".
Why this skill is useful
Adds executable scripts for caching and monitoring Lucidchart API usage that significantly reduce costs.
What it needs
Requires typescript 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 Cost and Value Review Overview Produce an evidence-backed right-sizing plan for licenses, seats, plan-dependent capabilities, and integration operations. Lucid's public developer documentation does not establish a universal per-export or per-API-call price. Prerequisites Authorized seat, role, plan, renewal, and usage evidence Current contract or official pricing source supplied by the account owner Named business and data owners for affected integrations Tool Discipline Use Read, Glob, and Grep for approved exports and repository evidence, WebFetch for current official plan documentation, and Write or Edit only for local analysis and a proposed action ledger. Current Contract Separate verified commercial terms from technical limits and internal operating costs. Treat public list prices and plan features as time-sensitive; never extrapolate them from API traffic, archive size, or export count. Authentication Prefer redacted offline exports. If account access is required, use read-only least privilege and never expose invoices, tokens, personal data, or contract terms beyond the approved audience. Instructions 1. Record evidence date, billing period, currency, contract source, current plan, and exclusions. 2. Inventory assigned seats, roles, active owners, dormant accounts, shared integrations, extensions, connectors, and critical documents. 3. Attribute cost only from invoices or current official commercial evidence; mark unknowns explicitly. 4. Measure operational effort separately: support, failures, connector hosting, observability, and manual reconciliation. 5. Propose reversible actions with owner, dependency, savings hypothesis, risk, and restoration path. 6. Present removals, role changes, plan changes, and integration shutdowns for approval. 7. After approved changes, compare realized invoices and service outcomes over a complete billing period. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lucidchart-cost-tuning--1b4d23