CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ai-persistence

Durability and state persistence for TanStack AI chats with @tanstack/ai-persistence. Routes to server chat persistence (withPersistence), client persistence (localStorage/IndexedDB), the store contracts, and adapter recipes. Distinguishes delivery durability (resumable streams) from conversation state. Use when conversations must survive reloads, multi-device, approvals, or server restarts — NOT for stream reconnect alone.

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

78%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 routing skill: nearly all content is non-obvious, library-specific guidance with executable code and explicit validation rules, and detail is properly pushed to sub-skills via clear routing tables. It loses points for a few over-twisty passages, elided/minimal example code, and the absence of error-recovery loops around the conformance and authorization checkpoints.

Suggestions

Trim the chat-vs-generation store identity paragraph and deduplicate the blob-key rules (currently covered in both the contracts section and the 'Where bytes land' paragraph) to reduce token cost.

Complete the client example (replace '// ...' with the rendered message list) and show the minimal shape of the './persistence' adapter import so the end-to-end sketch is fully copy-paste runnable.

Add a short feedback loop after the conformance-testkit rule: what a failure looks like and the fix-re-run cycle, since adapter implementation is the skill's most error-prone workflow.

DimensionReasoningScore

Conciseness

The body is dense and assumes TanStack AI knowledge throughout — no space is spent on concepts Claude already knows — but at ~250 lines some passages could be tightened (e.g., the runId/threadId identity explanation) and the blob-key rules are stated more than once.

4 / 5

Actionability

Concrete, executable guidance dominates: a complete server route with withPersistence, a client useChat snippet, the exact blob key format, the storageKey callback signature, and a copy-paste allowInputUrl predicate. Minor gaps remain — the client example ends in '// ...' and the adapter import './persistence' is a placeholder — so it is 'mostly executable' rather than fully copy-paste ready.

4 / 5

Workflow Clarity

The 'Recommended production stack' gives a clear 1–4 sequence and validation checkpoints are explicit ('Run the conformance testkit against any adapter you write', 'Authorize thread access at the route boundary'), but there is no fix-and-retry feedback loop for failed conformance or authorization, keeping it below the top anchor.

4 / 5

Progressive Disclosure

The skill is a clean routing overview: two 'Need to... → Read' tables point one level deep to clearly-named sub-skills (stores, server, client, per-ORM adapter recipes), and the overview itself holds only overview-level content — matching the well-signaled-reference exemplar.

5 / 5

Total

17

/

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 description: it states concrete capabilities with named APIs, gives an explicit 'Use when' trigger with an anti-trigger for the closest confusable concern, and cleanly separates state persistence from delivery durability. The only gap is a handful of missing natural synonyms (e.g., 'chat history', 'restore').

DimensionReasoningScore

Specificity

Multiple concrete named actions with comprehensive coverage: 'Routes to server chat persistence (withPersistence), client persistence (localStorage/IndexedDB), the store contracts, and adapter recipes' names the exact APIs and storage mechanisms for every facet of the domain.

5 / 5

Completeness

Explicitly answers both questions: the 'what' is the routing list of persistence capabilities, and the 'when' is a concrete 'Use when conversations must survive reloads, multi-device, approvals, or server restarts — NOT for stream reconnect alone' trigger clause that even includes a negative trigger.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('survive reloads, multi-device, approvals, or server restarts', 'localStorage/IndexedDB', 'stream reconnect'), but common user phrasings like 'chat history', 'save conversation', or 'restore' are missing, so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche with minimal conflict risk: it names the specific package (@tanstack/ai-persistence) and explicitly carves out the nearest competing trigger ('Distinguishes delivery durability (resumable streams) from conversation state'), so it is unlikely to fire for stream-reconnect needs.

5 / 5

Total

19

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

TanStack/ai

Path

packages/ai-persistence/skills/ai-persistence/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.