CtrlK
BlogDocsLog inGet started
Tessl Logo

tanstack-ai-memory-in-memory

Use when wiring inMemory() from @tanstack/ai-memory/in-memory — explains setup, options (embedder, extract, topK/minScore), when to pick it (dev/tests/single-process demos), and what NOT to use it for (multi-process or persistent).

77

Quality

96%

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

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

An exemplary lean skill body: executable setup code, concrete option defaults, explicit use/avoid guidance, and a capacity limit with a migration pointer — all in under 60 lines with zero filler. Nothing material is missing for the common wiring path.

DimensionReasoningScore

Conciseness

'Zero-dependency `recall`/`save` adapter backed by a `Map`. Records vanish on process restart.' — every line earns its place; no padding, no re-explaining concepts Claude already knows, and even the capacity limit is one tight paragraph.

5 / 5

Actionability

The Setup block is complete, copy-paste-ready TypeScript wiring the adapter into memoryMiddleware with a concrete scope, and Options gives executable signatures with real defaults (topK 6, minScore 0.15) covering the common cases.

5 / 5

Workflow Clarity

Single-task skill (import inMemory(), pass it to memoryMiddleware) and the single action is unambiguous, with a comment flagging the one decision point (static vs. derived scope). No destructive or batch operations, so no validation checkpoints are needed.

5 / 5

Progressive Disclosure

Roughly 50-line body with well-organized sections (When to use / When NOT / Setup / Options / Capacity), no content that belongs in separate files, and the single cross-reference to the sibling redis skill is clearly signaled — appropriate structure for a skill with no external references.

5 / 5

Total

20

/

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 tight, highly specific description that states both what the skill covers and explicit use/avoid triggers for a single well-known adapter. The only gap is modest synonym coverage for natural user phrasings like 'memory adapter' or 'recall/save'.

Suggestions

Add a natural synonym or two users would plausibly type, e.g. 'in-memory memory adapter' or 'recall/save', to broaden trigger matching.

Consider mentioning 'persistence' alongside 'persistent' so plain-language queries about memory persistence also surface this skill's boundary.

DimensionReasoningScore

Specificity

Names the exact module path '@tanstack/ai-memory/in-memory' and enumerates concrete specifics — 'setup', 'options (embedder, extract, topK/minScore)', 'when to pick it (dev/tests/single-process demos)', and 'what NOT to use it for (multi-process or persistent)' — with comprehensive coverage of the adapter's surface.

5 / 5

Completeness

Explicitly answers both: 'what' ('explains setup, options (embedder, extract, topK/minScore)') and 'when' via a leading 'Use when wiring inMemory()...' trigger clause, plus concrete negative triggers for when to avoid it.

5 / 5

Trigger Term Quality

Good natural keywords ('inMemory', 'dev/tests', 'single-process demos', 'multi-process', 'persistent') but misses common phrasings a user might say, such as 'memory adapter', 'recall/save', or 'in-memory storage'. Not 5 because synonym coverage is not comprehensive.

4 / 5

Distinctiveness Conflict Risk

Pinned to one specific subpath import with a clear niche, and the explicit 'what NOT to use it for (multi-process or persistent)' fence prevents mis-triggering against the sibling Redis/persistence skill.

5 / 5

Total

19

/

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.

Validation — 16 / 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.