Name: redis-labs
Rating: 59.2 (1 reviews)
Author: membranedev

redis-labs

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

Quality

68%

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/redis-labs/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 body is highly actionable with copy-paste-ready CLI commands and a clear connection workflow with polling and state-based checkpoints. It is slightly verbose in the intro and could offload some reference material to bundle files, but is otherwise well-structured.

Suggestions

Trim the introductory paragraph explaining what Redis Labs is, since Claude already knows this; lead directly with the workflow.

Add an explicit validation checkpoint after running actions (e.g. check the 'output' field for errors before reporting success).

Move the proxy flag table and detailed clientAction schema into a reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands, but the opening paragraph explaining what Redis Labs is and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary explanation Claude does not need, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands across the whole workflow (install, login, connection ensure, poll with --wait, action list/run with --input, proxy with a flag table), covering the common cases, matching 'fully executable; copy-paste ready code or commands'.	5 / 5
Workflow Clarity	Clear sequenced workflow (install -> login -> connect -> poll state -> search -> run/proxy) with an explicit polling feedback loop and state branching, but lacks an explicit post-action success verification checkpoint and has minor numbering inconsistency, matching 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested references, but everything is inlined (proxy options table, detailed clientAction schema) with no bundle files to offload reference material, matching 'good structure; most content appropriately placed; minor organization gaps'.	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 states both what it does and when to use it, anchored to a specific product, with an explicit 'Use when' clause. Its weaknesses are generic action verbs and thin trigger-term coverage beyond the product name.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Redis-specific actions (e.g. 'read and write keys, manage vector indexes, run Redis Functions').

Expand trigger terms with natural synonyms users say, such as 'cache', 'key-value store', 'Redis cloud', or 'vector search'.

Make the 'when' clause more concrete with specific trigger phrases (e.g. 'Use when the user wants to query, cache, or index data in Redis Labs').

Dimension	Reasoning	Score
Specificity	Names the Redis Labs domain and a few action areas ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete specific actions, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	Explicitly states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Redis Labs data"), but the 'when' clause is generic rather than concrete trigger phrases, fitting 'has both what and when; when could be more explicit'.	4 / 5
Trigger Term Quality	Contains the product name "Redis Labs" as the main keyword but offers few natural synonyms or phrasings a user would say (e.g. cache, key-value store, Redis cloud), matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific named product ("Redis Labs integration") giving a clear niche with low conflict risk, though the generic action verbs create minor overlap with general data skills, matching 'mostly distinct; minor overlap risk'.	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/redis-labs/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.