Name: groundlight
Rating: 56.8 (1 reviews)
Author: membranedev

groundlight

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

Quality

65%

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/groundlight/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 delivers strong, executable Membrane CLI guidance with a sensible connection-state workflow, but it is let down by a vague Overview section, dangling step references, and some introductory padding. Fixing the step numbering and grounding the Overview in real Groundlight actions would meaningfully raise clarity and actionability.

Suggestions

Replace the placeholder 'Groundlight Overview' bullet list with concrete Groundlight action examples (e.g., querying detectors, submitting images, retrieving findings) so the overview is actionable.

Fix the broken step numbering: label the connection step '1a', resolve the dangling 'skip to Step 2' reference, and number the subsequent search/run steps consistently.

Trim the introductory 'Groundlight is a SaaS app...' paragraph to one line or move it into the description, since it explains context Claude can infer from the docs link.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste CLI commands, but the opening paragraph over-explains what Groundlight is and the near-empty 'Groundlight Overview' section ('Use action names and parameters as needed') adds little value and could be trimmed or removed.	3 / 5
Actionability	It provides concrete, executable bash commands for install, login, connection, action discovery, action run, and proxy requests with flag tables, but the vague Overview section and 'Use action names and parameters as needed' leave a minor gap.	4 / 5
Workflow Clarity	There is a clear connect -> poll-for-state -> search -> run sequence with validation via state polling (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the dangling 'skip to Step 2' reference and unlabeled '1b' numbering introduce a minor clarity gap.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with no external bundle files needed, but the duplication between 'Searching for actions' and 'Popular actions' and the thin Overview section are minor organization gaps.	4 / 5
	Total	15 / 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 answers both 'what' and 'when' with an explicit trigger clause, but its capability list is generic and not grounded in Groundlight-specific terms. Tightening the actions to Groundlight's real features would lift specificity and trigger quality.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with Groundlight-specific ones (e.g., 'list and query detectors, submit images for inspection, retrieve findings').

Add natural trigger terms users would say, such as 'detectors', 'image inspection', or 'visual monitoring', alongside 'Groundlight data'.

Make the 'Use when' clause concrete by naming the Groundlight tasks it covers rather than only 'interact with Groundlight data'.

Dimension	Reasoning	Score
Specificity	It names the Groundlight domain and a few actions ('Manage data, records, and automate workflows'), but those actions are generic and not tied to Groundlight's actual capabilities (image monitoring, detectors), so coverage is incomplete rather than comprehensive.	3 / 5
Completeness	It states both what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with Groundlight data'), but the 'when' could be more specific about Groundlight tasks.	4 / 5
Trigger Term Quality	'Groundlight', 'data', 'records', and 'workflows' are relevant keywords, but Groundlight-specific natural terms users would say (detectors, image monitoring, findings) and common variations are missing.	3 / 5
Distinctiveness Conflict Risk	The Groundlight niche is clearly distinct, but the generic capability phrasing ('Manage data, records, and automate workflows') creates minor overlap risk with other generic integration skills.	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/groundlight/SKILL.md
Commit: f484c82

Reviewed: 5 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.