Name: lucca
Rating: 63.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

lucca

Lucca integration. Manage data, records, and automate workflows. Use when the user wants to interact with Lucca data.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

75%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 copy-paste ready commands and a strong connection-state feedback loop, but it is held back by duplicated action-discovery guidance and a broken "Step 2" cross-reference that slightly muddies the workflow.

Suggestions

Remove the duplicate action-list guidance: the "Popular actions" section repeats the `membrane action list` discovery already shown in "Searching for actions" — merge them or have one reference the other.

Fix the dangling "skip to Step 2" reference in the Connecting section: either define and label a Step 2 (e.g., Searching for actions) or reword to "skip to Searching for actions", and relabel "1b" since there is no "1a".

Tighten padded phrasing such as "so you can focus on the integration logic rather than auth plumbing" and the bare Lucca Overview bullet list, which add tokens without adding executable guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands but repeats action-discovery guidance in both "Searching for actions" (`membrane action list`) and "Popular actions", and includes light padding like "so you can focus on the integration logic rather than auth plumbing", fitting "mostly efficient but includes some unnecessary explanation or could be tightened."	3 / 5
Actionability	Copy-paste ready commands throughout — `npm install -g @membranehq/cli@latest`, `membrane connection ensure`, and `membrane action run <actionId> --input '{...}'` — cover install, auth, connect, search, run, and proxy cases.	5 / 5
Workflow Clarity	The connection flow has an explicit feedback loop (poll with `--wait`, branch on READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after the user acts), but the dangling "skip to Step 2" reference with no defined Step 2 and no validation of action-run outcomes are minor gaps.	4 / 5
Progressive Disclosure	The body is organized into clear, navigable sections (Overview, Working with Lucca, Connecting, Searching, Proxy, Best practices) with no nested references, though all content — including the proxy flags reference table — is inline with no separate reference files, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

75%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 is strong: it answers both what and when explicitly with a clear trigger phrase and is highly distinct thanks to the named Lucca brand. Its main weakness is generic action language and missing HR-specific synonyms users would naturally say.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Lucca domain and a few actions, but the actions are generic ("Manage data, records") rather than concrete HR operations, matching the "names domain and 1-2 concrete actions, not comprehensive" anchor and sitting above the "actions minimal or generic" anchor.	3 / 5
Completeness	"Lucca integration. Manage data, records, and automate workflows" states what it does and "Use when the user wants to interact with Lucca data" gives an explicit when trigger, clearly answering both what and when with a concrete trigger phrase.	5 / 5
Trigger Term Quality	"Use when the user wants to interact with Lucca data" supplies a natural trigger phrase and the brand name "Lucca" repeats, but HR-domain synonyms users would actually say (payroll, leave, expenses, time tracking) are absent, fitting "some relevant keywords but missing common variations or synonyms."	3 / 5
Distinctiveness Conflict Risk	"Lucca integration" and "interact with Lucca data" anchor on a specific named product, yielding a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	16 / 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/lucca/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.