CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bun-redis

Use when working with Redis in Bun (ioredis, Upstash), caching, pub/sub, session storage, or key-value operations.

59

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/bun/skills/bun-redis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 strong, example-driven reference with highly executable code and clearly organized sections, but it functions as a monolithic inline Redis API tutorial that duplicates knowledge Claude already has. The reference-file pointers are well designed but currently broken since no reference files ship with the skill.

Suggestions

Create the referenced `references/clustering.md` and `references/lua-scripts.md` files, or remove the "When to Load References" section — the current pointers lead to nonexistent files.

Move the exhaustive data-structure command coverage (hashes, lists, sets, sorted sets) into a reference file, keeping only one representative example of each in SKILL.md to cut token cost.

Trim the basic string operations section to the few operations that differ from standard Redis semantics, since Claude already knows the common set/get/incr/del API.

DimensionReasoningScore

Conciseness

Snippets are code-forward and compact, but large stretches ("Strings", "Hashes", "Lists", "Sets", "Sorted Sets") re-document standard Redis commands and ioredis APIs Claude already knows, and the body runs ~330 lines of inline API tutorial that could be tightened.

3 / 5

Actionability

Nearly every example (connection setup, basic ops, data structures, pub/sub, transactions, Upstash, session middleware) is complete, copy-paste-ready TypeScript covering the common cases; only the caching patterns lean on undefined `db`/`eq` placeholders, which are clearly the user's own database layer.

5 / 5

Workflow Clarity

Multi-step patterns (cache-aside check→fetch→setex, write-through, rate-limit incr→expire, session middleware get→next→save) are clearly sequenced with correct ordering. No validation checkpoints appear, but none of the operations are destructive or batch operations that would require them.

4 / 5

Progressive Disclosure

The "When to Load References" section is a well-signaled pattern, but both files it names (`references/clustering.md`, `references/lua-scripts.md`) do not exist in the bundle, leaving dangling pointers. Additionally, bulk API-reference content (data structures, basic operations) is inlined in SKILL.md rather than split into reference files.

3 / 5

Total

15

/

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.

A focused, trigger-heavy description with good natural keywords and a clear niche, but it reads entirely as a when-clause and never tells the reader what the skill actually does. Adding an explicit capability statement would round it out.

Suggestions

Lead with a what-clause of concrete actions, e.g., "Set up Redis clients (ioredis, Upstash) in Bun and implement caching, pub/sub, session storage, and rate-limiting patterns.", then keep the Use-when clause.

Add missing natural trigger terms such as "rate limiting", "message queue", and "Bun Redis client" to widen keyword coverage.

Narrow the generic "caching" and "session storage" triggers to "Redis caching" / "Redis-backed sessions" to reduce overlap with non-Redis caching skills.

DimensionReasoningScore

Specificity

Names the domain ("Redis in Bun"), specific client libraries ("ioredis, Upstash"), and several capability areas ("caching, pub/sub, session storage, or key-value operations") — specific rather than vague, though no concrete action verbs state what the skill does.

4 / 5

Completeness

The "when" is explicit and well-scoped, but the "what" is only implied by the domain — the description never states actions the skill performs (e.g., setting up clients or implementing caching/session/pub-sub patterns). It sits between anchor 3 (what present, when weak) and anchor 4 (both present).

3 / 5

Trigger Term Quality

Good natural keyword coverage ("Redis", "Bun", "ioredis", "Upstash", "caching", "pub/sub", "session storage", "key-value") that users would naturally say; a few natural terms like "rate limiting", "message queue", and "Redis Cluster" are missing.

4 / 5

Distinctiveness Conflict Risk

The Redis-in-Bun niche with named client libraries is mostly distinct, but generic trigger terms like "caching" and "session storage" could fire for non-Redis caching or session work handled by other skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/bun/skills/bun-redis/SKILL.md

Reviewed

Table of Contents

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.