Name: lucidworks
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

lucidworks

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

Quality

66%

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/lucidworks/SKILL.md

Quality

Content

67%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 body is a well-structured, actionable integration guide with executable CLI commands and a clear state-driven connection workflow, held back slightly by minor verbosity and placeholders that keep it from being fully copy-paste ready.

Suggestions

Remove the marketing preamble about Lucidworks being an AI-powered search platform and trim filler lines like 'Use action names and parameters as needed.' to improve token efficiency.

Complete the executable examples by filling in realistic placeholder values or showing a concrete worked example (e.g. a real actionId and connectionId) so commands are copy-paste ready.

Reconcile the connection workflow numbering (Step 2 vs '#### 1b') into a single coherent numbered sequence and add an explicit terminal check that the action succeeded.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (executable CLI commands and a flag table), but the opening marketing line ('AI-powered search platform... helps businesses build intelligent search applications') and filler like 'Use action names and parameters as needed.' could be trimmed, fitting the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	It provides concrete, executable commands for the common cases (login, connection ensure, action list/run, proxy request) with a full flag table, but placeholders like `<actionId>`, `CONNECTION_ID`, and the value-less `--tenant` flag leave minor gaps versus fully copy-paste-ready guidance.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop after user action, matching 'clear sequence with most checkpoints'; it stops short of anchor 5 because the 'Step 2' / '1b' numbering is disjointed and there is no terminal success validation.	4 / 5
Progressive Disclosure	The single file is well-organized with clear section headers and no bundle files or external references; content is appropriately placed for an overview, though the inline clientAction schema and full proxy flag table could be split out, leaving it just below the ideal one-level-deep reference structure of anchor 5.	4 / 5
	Total	15 / 20 Passed

Description

66%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 answers both what and when and is clearly distinguishable by the Lucidworks product name, but its listed actions are generic and trigger-term coverage is thin beyond the brand name.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Lucidworks-specific actions such as 'query collections, run pipelines, and manage records' to lift specificity.

Add natural trigger phrases and synonyms users would say (e.g. 'search Lucidworks', 'run a Lucidworks pipeline', 'query a collection') so the skill triggers on common phrasings, not just the brand name.

Tighten the 'Use when' clause to reference concrete objects (collections, pipelines, records) rather than the generic 'interact with Lucidworks data'.

Dimension	Reasoning	Score
Specificity	Names the Lucidworks domain and three actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, fitting the '1-2 concrete actions, not comprehensive' anchor; it does not reach the 'several specific actions' of 4.	3 / 5
Completeness	It provides a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Lucidworks data'), but the 'when' trigger phrases are not as comprehensive or specific as the anchor 5 example.	4 / 5
Trigger Term Quality	The natural trigger is essentially the product name plus 'interact with Lucidworks data'; it has relevant keywords but lacks synonyms, file extensions, or common variations, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The product-specific name 'Lucidworks' gives it a clear niche with minimal conflict risk against other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	15 / 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/lucidworks/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.