Name: redis
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

redis

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

Quality

70%

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/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 executable Membrane CLI commands and a well-sequenced connection workflow, but it spends tokens explaining Redis basics Claude already knows and has minor workflow-numbering inconsistencies.

Suggestions

Remove the opening Redis definition paragraph and the generic 'Redis Overview' section; assume Claude knows what Redis is.

Fix the workflow numbering so 'Step 2' is an actual labeled section and the lone '1b' heading fits the sequence.

Consider moving the proxy flags table and detailed action-discovery examples into a reference file to lean down the main SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands, but it opens by explaining what Redis is ('Redis is an in-memory data structure store, used as a database, cache, message broker...') and includes a generic 'Redis Overview' (Key/Value, 'Use action names and parameters as needed') that Claude does not need, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Provides copy-paste-ready commands for every stage (install, login, connection ensure, polling, action list/run with JSON input, proxy requests) plus a flags table, fully covering the common cases at the 'fully executable' anchor.	5 / 5
Workflow Clarity	A clear install→auth→connect→search→run→proxy sequence exists with an explicit connection state-machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-action feedback loop, but the 'skip to Step 2' references and an isolated '1b' heading leave a minor numbering gap keeping it below level 5.	4 / 5
Progressive Disclosure	The single file is well-sectioned with clear headers and no nested references, but it is over 50 lines with no external reference split for the bulky proxy flag table / action details, matching 'good structure; minor organization gaps' rather than the ideal one-level-deep reference layout.	4 / 5
	Total	16 / 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 is well-formed with an explicit 'Use when...' trigger and a distinct Redis niche, but its capability verbs ('manage data, records, automate workflows') are generic rather than concrete Redis operations.

Suggestions

Replace generic verbs with concrete Redis operations, e.g. 'Read and write keys, manage data structures, and automate Redis workflows.'

Add common user synonyms/extensions such as 'cache', 'key-value store', or 'set/get keys' to broaden trigger-term coverage.

Tighten the 'what' clause with a couple of specific actions (e.g. 'query keys, set values, run pipeline commands') to push completeness toward level 5.

Dimension	Reasoning	Score
Specificity	Names the Redis domain and a couple of actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete operations, matching the '1-2 concrete actions, not comprehensive' anchor and falling below the 'several specific actions' level 4.	3 / 5
Completeness	Explicitly answers both what ('Redis integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Redis data.'), but the 'what' is generic enough that it does not reach the concrete-trigger-phrases level 5.	4 / 5
Trigger Term Quality	Includes relevant natural terms ('Redis', 'interact with Redis data') but lacks common variations or synonyms users might say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Redis is a clearly named, specific system with distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' 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/redis/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.