CtrlK
BlogDocsLog inGet started
Tessl Logo

tanstack-ai-memory-redis

Use when wiring redis() from @tanstack/ai-memory/redis in production — covers client setup (ioredis or node-redis via fromNodeRedis), the storage model, client-side ranking limits, and troubleshooting.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 tight, executable reference: complete code for both Redis client flavors, a precise storage model, and concrete troubleshooting with exact remediation. The only gap is the absence of an explicit post-setup validation checkpoint and the lack of any external reference offloading.

Suggestions

Add a short "Verify" step after setup, e.g. a save-then-recall round-trip to confirm the adapter works before relying on it.

Consider moving the detailed Troubleshooting entries into a references/ file to keep the overview shorter and apply progressive disclosure.

Note the node-redis version constraint (v4+) once in the snippet header rather than only in prose to make the requirement unmissable.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude's competence — no padding explaining Redis, memory adapters, or library basics — and load-bearing asides like "(no vector index required)" and "(never deleted)" each earn their tokens.

5 / 5

Actionability

Two complete copy-paste TypeScript setup snippets (ioredis and node-redis via fromNodeRedis) with exact imports, the concrete thrown error "client.sadd is not a function", the key layout "{prefix}:record:{id}", and an exact remediation target.

5 / 5

Workflow Clarity

Setup sequence is clear (pick A/B, build client, construct adapter, wire middleware) with a useful migration "Hard cut" warning, but there is no explicit validate-after-setup checkpoint or feedback loop to push it to 5; not a destructive/batch operation so the cap-3 rule does not apply.

4 / 5

Progressive Disclosure

No bundle files exist and the body is well-organized under clear section headers; at ~80 lines it sits just above the under-50-line simple-skill threshold and could arguably offload troubleshooting to a reference, so it is not the pristine section-only 5 case.

4 / 5

Total

18

/

20

Passed

Description

85%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 both capability and trigger conditions with low conflict risk. Its only weakness is trigger-term quality: the keywords are largely SDK identifiers rather than the natural phrases a user would actually say.

Suggestions

Add natural-language trigger terms a user would say, e.g. "Use when you need a Redis-backed memory adapter for TanStack AI recall/save".

Mention the recall/save verbs explicitly as keywords so the skill surfaces on memory-storage requests.

Optionally include synonyms like "Redis memory" alongside the package path to broaden natural-language matching.

DimensionReasoningScore

Specificity

Names four distinct concrete capability areas — "client setup (ioredis or node-redis via fromNodeRedis)", "the storage model", "client-side ranking limits", and "troubleshooting" — giving comprehensive coverage of the adapter, matching the multiple-specific-actions anchor rather than the minor-gaps anchor 4.

5 / 5

Completeness

Explicitly answers both what ("covers client setup…storage model…ranking limits…troubleshooting") and when ("Use when wiring redis() from @tanstack/ai-memory/redis in production") with concrete trigger phrasing, matching the both-what-and-when anchor.

5 / 5

Trigger Term Quality

Includes relevant real terms ("redis", "@tanstack/ai-memory/redis", "ioredis", "node-redis", "production", "troubleshooting") but leans on SDK identifiers rather than natural user phrasing and omits common synonyms such as "memory adapter" or "recall/save".

3 / 5

Distinctiveness Conflict Risk

The trigger is tightly scoped to the specific package path "@tanstack/ai-memory/redis" and the "redis()" call, a clear niche with minimal overlap with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
TanStack/ai
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.