CtrlK
BlogDocsLog inGet started
Tessl Logo

tanstack-ai-memory-honcho

Use when wiring honcho() from @tanstack/ai-memory/honcho — a hosted memory adapter where recall is a dialectic answer over the user's representation (no discrete fragments). Requires the optional @honcho-ai/sdk peer.

68

Quality

86%

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

92%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 lean, dense, well-organized single-file skill: executable setup code, exact option defaults, and precise adapter semantics with zero filler. The only notable gap is that the code ends at middleware construction without showing the final wiring into an agent run.

DimensionReasoningScore

Conciseness

Every line carries Honcho-specific knowledge Claude cannot infer (session-key format '{tenantId|_}__{threadId}', env-var defaults, 'namespace is ignored', 'Honcho exposes no LLM tools'); there is no padding or re-teaching of known concepts. Not 4 — nothing needs trimming.

5 / 5

Actionability

The Setup block is complete, executable TypeScript with a concrete security caution ('never from req.body') and the Options list gives exact defaults. Not 5 because it stops at building the middleware — no example of attaching it to an actual agent/chat run to complete the common case.

4 / 5

Workflow Clarity

A simple, single-purpose skill under 50 lines whose single action (build the adapter per request from a server-validated session and pass it to memoryMiddleware) is unambiguous, with explicit sequencing in the code. No destructive or batch operations, so no validation cap applies.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references; the Setup / Options / scope-fields sections are well-organized and everything is at the appropriate level of detail for a single-file skill.

5 / 5

Total

19

/

20

Passed

Description

73%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 distinct, well-targeted description with an explicit trigger and concrete vendor-specific behavior. Its main gap is one-sided capability coverage: recall is described in detail while the adapter's save behavior is omitted entirely.

Suggestions

Mention the save/recording capability alongside recall so the 'what' covers both halves of the adapter's behavior (e.g., '...recall synthesizes a dialectic answer over the user's representation and save appends turn messages to the session').

Include one or two more natural trigger phrases users might say, such as 'Honcho memory', 'dialectic chat', or 'server-backed memory', to broaden keyword coverage beyond the exact import path.

Trim or fold the peer-dependency note ('Requires the optional @honcho-ai/sdk peer') into the trigger clause so it reads as a condition rather than trailing metadata.

DimensionReasoningScore

Specificity

Names the domain ('hosted memory adapter') and 1-2 concrete behaviors ('wiring honcho()', 'recall is a dialectic answer over the user's representation'), but never mentions the save side or any other capabilities, so coverage is not comprehensive. Not 4 because only one or two concrete actions are actually listed.

3 / 5

Completeness

Explicit trigger ('Use when wiring honcho() from @tanstack/ai-memory/honcho') plus a stated what ('a hosted memory adapter where recall is a dialectic answer'). Not 5 because the 'what' is one-sided — save behavior and overall adapter purpose beyond recall are not described.

4 / 5

Trigger Term Quality

'honcho()', '@tanstack/ai-memory/honcho', 'memory adapter', 'recall' are natural terms a user needing this skill would say. Not 5 because there is no broader synonym coverage (e.g., 'memory', 'Honcho SDK', 'dialectic chat').

4 / 5

Distinctiveness Conflict Risk

Names the exact subpath import ('@tanstack/ai-memory/honcho') and vendor-specific behavior (dialectic recall, no discrete fragments), giving it a clear niche with minimal conflict risk against other memory skills.

5 / 5

Total

16

/

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.