Name: redis-observability
Rating: 77.60000000000001 (1 reviews)
Author: redis

redis-observability

Redis observability guidance — which metrics to monitor (memory, connections, hit ratio, ops/sec, rejected connections), which built-in commands to reach for during incident triage (SLOWLOG, INFO, MEMORY DOCTOR, CLIENT LIST, FT.PROFILE), and when to use the Redis Insight GUI. Use when setting up monitoring or alerts for a Redis instance, diagnosing a performance regression, profiling a slow FT.SEARCH query, or wiring Redis metrics into Prometheus, Datadog, or similar.

Quality

96%

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

93%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, lean reference body with executable commands and code, and correctly factored one-level-deep references. The only gap is the absence of an explicit numbered triage workflow, which is a minor issue for this non-destructive skill.

Suggestions

Add a short numbered incident-triage sequence (e.g., 1. check INFO memory -> 2. run MEMORY DOCTOR -> 3. inspect SLOWLOG GET) to lift workflow clarity toward 5.

Optionally add a one-line validation/check checkpoint after the SLOWLOG and MEMORY DOCTOR examples (e.g., 're-run after a config change to confirm resolution').

The 'References' section duplicates the Redis Insight link already given inline in section 3 — collapse to avoid a minor redundancy.

Dimension	Reasoning	Score
Conciseness	The body is lean — metric/command tables and two short Python snippets with no padding — and assumes Claude knows Redis basics, fitting the lean-and-efficient anchor at 5; the only mild over-explanation is the Redis Insight paragraph, but it earns its place and is far from the verbosity of anchor 4.	5 / 5
Actionability	Provides exact executable commands with thresholds (SLOWLOG GET 10, MEMORY DOCTOR, FT.PROFILE <idx> SEARCH QUERY), specific alert cutoffs (> 80% of maxmemory, Hit ratio < 80%), and two copy-paste-ready Python snippets covering the common incident cases, matching the fully-executable anchor at 5.	5 / 5
Workflow Clarity	The three-section triage flow (monitor metrics -> debugging commands -> Insight) plus the 'two most useful for incident triage' callout gives a clear sequence, but there is no explicit numbered workflow or checkpoint; it sits above anchor 3 (steps present, checkpoints missing) yet below anchor 5 (explicit validation steps).	4 / 5
Progressive Disclosure	A clean overview delegates detail to two real, verified one-level-deep reference files (references/metrics.md, references/commands.md) with clearly signaled inline links, and content is appropriately split — matching the clear-overview-with-well-signaled-one-level-deep-references anchor at 5.	5 / 5
	Total	19 / 20 Passed

Description

100%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 clearly states what the skill covers and when to invoke it, with natural trigger phrases and low conflict risk. No meaningful gaps across any dimension.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete capabilities with specifics — metrics to monitor (memory, connections, hit ratio, ops/sec, rejected connections), triage commands (SLOWLOG, INFO, MEMORY DOCTOR, CLIENT LIST, FT.PROFILE), and the Redis Insight GUI — matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.	5 / 5
Completeness	Explicitly answers both 'what' (metrics, commands, GUI usage) and 'when' via a full 'Use when setting up monitoring... diagnosing... profiling... wiring...' clause with concrete triggers, matching the anchor-5 example and clearly above anchor 4 where 'when' is only adequate.	5 / 5
Trigger Term Quality	Natural user phrases ('setting up monitoring or alerts', 'diagnosing a performance regression', 'profiling a slow FT.SEARCH query') plus named tools (Prometheus, Datadog, Redis Insight) give comprehensive coverage including synonyms, fitting the anchor-5 example better than the few-terms-missing anchor at 4.	5 / 5
Distinctiveness Conflict Risk	The Redis-specific niche anchored to distinctive command names (SLOWLOG, FT.PROFILE) and tools (Redis Insight) creates clear triggers with minimal overlap risk, matching the clear-niche anchor at 5 rather than the minor-overlap anchor at 4.	5 / 5
	Total	20 / 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-observability/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.