Name: lucid
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

lucid

Lucid integration. Manage Organizations. Use when the user wants to interact with Lucid data.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/lucid/SKILL.md

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete commands throughout and a clear connection state machine, but it omits validation checkpoints for destructive action/proxy operations and has minor structural redundancy. It is a strong, mostly efficient CLI guide.

Suggestions

Add an explicit validation/verification checkpoint before running modifying or destructive actions and before proxy requests using POST/PUT/PATCH/DELETE (e.g., confirm the target or dry-run first) to lift workflow clarity above 3.

Fix the step numbering ("1b" appears with no "1a"; "skip to Step 2" references an unlabeled Step 2) and dedupe the `action list` command repeated in both 'Searching for actions' and 'Popular actions'.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands and Membrane-specific state-machine detail that Claude would not know, with only minor over-explanation (the opening "Lucid is a visual collaboration suite..." paragraph and phrases like "This is the fastest way to get a connection").	4 / 5
Actionability	It provides copy-paste-ready commands for every common case — install, login, connection ensure, polling, action list/run, and proxy — plus a flags table, with placeholders only where IDs are inherently dynamic.	5 / 5
Workflow Clarity	The connection flow is well sequenced with state polling and a re-poll feedback loop, but running actions and proxy requests (which support POST/PUT/PATCH/DELETE) lack any validation/verification checkpoint before destructive operations, capping this dimension at 3.	3 / 5
Progressive Disclosure	The single-file body is well organized into clear one-level sections with no nested references and no bundle files needed, but the "1b"/"Step 2" numbering is inconsistent and the action-list command is duplicated across "Searching for actions" and "Popular actions".	4 / 5
	Total	16 / 20 Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description provides an explicit Use-when trigger and names the Lucid niche, but its capability list is thin (only Organizations) and it omits the Lucidchart/Lucidspark synonyms users actually say. It is solid but not comprehensive.

Suggestions

Name more concrete actions beyond 'Manage Organizations' (e.g., create/edit Lucidchart diagrams, manage Lucidspark boards, handle Documents, Pages, Workspaces, Teams, and Templates) to raise capability specificity.

Add natural trigger synonyms users say — 'Lucidchart', 'Lucidspark', 'diagrams', 'whiteboards' — alongside 'Lucid data' so the skill surfaces for the right requests.

Dimension	Reasoning	Score
Specificity	It names the domain ("Lucid integration") and one concrete action ("Manage Organizations"), but the integration phrase is vague and only a single Lucid entity is named rather than the full scope (Documents, Pages, Workspaces, Teams, Templates).	3 / 5
Completeness	Both a "what" ("Lucid integration. Manage Organizations.") and an explicit "when" ("Use when the user wants to interact with Lucid data.") are present; the "when" is explicit but generic, so it stops short of a 5.	4 / 5
Trigger Term Quality	"Lucid", "Organizations", and "interact with Lucid data" are relevant keywords, but common natural synonyms users would say — "Lucidchart", "Lucidspark", "diagrams", "whiteboards" — are absent.	3 / 5
Distinctiveness Conflict Risk	"Lucid" is a distinct product niche with low conflict risk, but the broad phrasing ("Lucid integration", "interact with Lucid data") leaves minor overlap risk versus a more tightly-scoped trigger.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/lucid/SKILL.md
Commit: f484c82

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.