Name: redis-connections
Rating: 72.8 (1 reviews)
Author: redis

redis-connections

Redis client and connection guidance covering connection pooling, multiplexing, pipelining, client-side caching with RESP3, avoiding slow commands (KEYS, SMEMBERS, HGETALL), and tuning socket timeouts. Use when configuring a Redis client (redis-py, Jedis, Lettuce, NRedisStack), batching commands for throughput, eliminating per-request connection creation, iterating large keyspaces with SCAN, enabling client-side caching for read-heavy workloads, or setting connect and read timeouts.

Quality

88%

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

Quality

Content

85%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.

A well-structured, actionable skill body with executable code in every section and clean one-level-deep progressive disclosure to real reference files. It is concise and assumes competence; the only gap is the absence of explicit validation/verify checkpoints for batch operations, which leaves workflow clarity just short of a 5.

Suggestions

Add an explicit validation checkpoint for the SCAN cursor loop and pipeline execution (e.g., 'verify expected key count before processing' or 'handle partial pipeline errors via raise_on_error') to lift workflow_clarity to 5.

Trim a few framing sentences like 'The single biggest mistake in Redis client code is...' and 'Defaults vary by client and may be too generous' to make the body fully lean.

Consider adding a short 'Verify' step after enabling client-side caching (e.g., confirm invalidation behavior with a test write) since it is a stateful, hard-to-debug change.

Dimension	Reasoning	Score
Conciseness	The body is lean—short prose, tables, and compact code samples that assume Claude's knowledge of Redis; a few introductory sentences ('The single biggest mistake...', 'Defaults vary by client...') add mild framing that could be trimmed but earn their place by motivating the rule.	4 / 5
Actionability	Every section gives executable, copy-paste-ready code (ConnectionPool setup, pipeline loop, SCAN cursor loop, RESP3 cache config, timeout kwargs) plus concrete command substitutions in a table; the common cases are directly covered.	5 / 5
Workflow Clarity	Sections are clearly sequenced by topic with concrete guidance and rules of thumb, and the SCAN example includes a termination checkpoint (cursor == 0); however there are no explicit validate/verify feedback loops for the batch operations (pipelining, keyspace iteration), keeping it just below the explicit-checkpoint bar.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview with five well-signaled, one-level-deep references (pooling.md, pipelining.md, blocking.md, client-cache.md, timeouts.md) that all exist in the bundle, plus an external references list; content is appropriately split with clear navigation.	5 / 5
	Total	18 / 20 Passed

Description

92%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.

A strong, specific description that concretely enumerates capabilities and provides explicit 'Use when' trigger guidance across multiple named Redis clients. Minor room for broader trigger-term synonym coverage, but it clearly answers both what and when.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities—pooling, multiplexing, pipelining, client-side caching with RESP3, avoiding specific slow commands (KEYS, SMEMBERS, HGETALL), and tuning socket timeouts—giving comprehensive coverage of the domain.	5 / 5
Completeness	Explicitly answers 'what' (client/connection guidance across pooling, multiplexing, pipelining, caching, slow commands, timeouts) and 'when' with a concrete 'Use when...' clause enumerating trigger scenarios.	5 / 5
Trigger Term Quality	Strong natural trigger phrases ('configuring a Redis client', 'batching commands for throughput', 'iterating large keyspaces with SCAN') cover real user phrasings, but a few common variations (e.g., 'Redis latency', 'Redis client setup') and library names beyond the enumerated clients are partially covered rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	Clear niche (Redis client/connection efficiency) with specific trigger conditions and named clients; minimal overlap risk with other skills since the domain is narrowly scoped to connection-level Redis guidance.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: redis/agent-skills
Path: skills/redis-connections/SKILL.md
Commit: 172fb9e

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