CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory-system

为 Agent 设计、实现或评估用户记忆系统时使用——涵盖记忆能力三层次评估框架、轨迹与长期记忆分层、Simple Notes 到 Advanced JSON Cards 及可执行代码的存储格式选型、Mem0/Memobase 框架取舍、记忆压缩整理与隐私脱敏,以及何时该用记忆而非 RAG 的判断。

Quality

85%

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

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 knowledge-dense, mostly actionable design reference with concrete heuristics, a sequenced lifecycle, and honest tradeoff guidance. Its main weaknesses are a duplicated format taxonomy, monolithic inlining of framework/evaluation details that belong in separate reference files, and bundle references that point to nonexistent paths.

Suggestions

Split the Mem0/Memobase framework comparison, the evaluation methodology, and the compression pipeline out of 核心原则 into one-level-deep reference files (e.g., references/frameworks.md, references/evaluation.md) and link them from a leaner overview.

Remove the duplication between the four-format bullet list and the 速查 table — keep only the table (it already carries 结构/优势/代价).

Verify the bundle actually ships the referenced paths (chapter3/user-memory/, chapter3/mem0/, chapter3/memobase/, chapter3/user-memory-evaluation/, book/chapter3.md) or drop/replace them with files that exist.

DimensionReasoningScore

Conciseness

Dense, high-signal domain guidance with no filler or explanations of concepts Claude already knows; the material (Mem0 v3 ADD-only internals, LoCoMo scores, three-tier acceptance criteria) is genuinely non-obvious. One notable trimmable redundancy: the four storage formats are described twice in adjacent blocks (bullet list "Simple Notes:最小不可分事实…" then a 速查 table repeating the same 结构/优势/代价), which is more than the 5 anchor's 'every token earns its place' but short of the 3 anchor's diffuse padding.

4 / 5

Actionability

As an instruction-only skill the guidance is largely executable: concrete selection heuristics ("关键且少量…用 Advanced JSON Cards;大量且非关键…用 Simple Notes"), a named privacy stack (Ollama + Qwen3 0.6B, 正则快筛 + LLM 深析), and a step-by-step evaluation protocol (~20 cases per level, LLM-as-a-judge). Minor gaps: no runnable commands/snippets inline and the 配套代码 paths cannot be opened from this bundle.

4 / 5

Workflow Clarity

The lifecycle is clearly sequenced with checkpoints: "读取相关记忆 → 会话结束后后台提取候选事实 → 来源与策略核验 → 更新(增/改/删/合并)", plus evidence-checking rules for conflicts ("追溯各自原始信息源…证据不足则保留待确认状态") and for pruning ("定期整理必须回到原始证据核查"). It falls short of the 5 anchor only because the feedback/retry loop for failed 核验 is implied rather than an explicit validate→fix→re-validate cycle.

4 / 5

Progressive Disclosure

Section structure is good (何时使用/核心原则/实践模式/常见陷阱/配套代码/深度阅读), but the 核心原则 section is a monolithic ~30-line wall mixing framework internals, format taxonomy, compression pipeline, and evaluation methodology — content that belongs in separate reference files. Referenced paths ("chapter3/user-memory/", "book/chapter3.md") do not exist in this bundle, so the references cannot be followed and are not clearly signaled beyond a single 深度阅读 line.

3 / 5

Total

15

/

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: explicit use-when trigger, enumerated concrete capabilities, named frameworks, and a clear niche boundary versus RAG. The only weakness is missing a few natural trigger synonyms (preferences, personalization, cross-session).

DimensionReasoningScore

Specificity

Multiple specific concrete capabilities are enumerated: "设计、实现或评估用户记忆系统", "存储格式选型"(Simple Notes 到 Advanced JSON Cards 及可执行代码), "Mem0/Memobase 框架取舍", "记忆压缩整理与隐私脱敏". Coverage of the domain is comprehensive, not generic.

5 / 5

Completeness

The 'when' is explicit and concrete ("为 Agent 设计、实现或评估用户记忆系统时使用") and the 'what' is explicitly enumerated (三层次评估框架、轨迹与长期记忆分层、格式选型、框架取舍、压缩与脱敏、记忆 vs RAG 判断). Both questions are answered with concrete trigger phrases, matching the 5 anchor; the 4 anchor's weaker/implicit 'when' does not apply.

5 / 5

Trigger Term Quality

Good natural-term coverage: "用户记忆系统", "长期记忆", "Mem0", "Memobase", "RAG", "隐私脱敏". A few common phrasings a user might naturally say are missing (e.g., "偏好", "个性化", "跨会话"), so it does not reach the synonym-complete level of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche (user memory for Agents) with named frameworks (Mem0/Memobase) and an explicit boundary against RAG knowledge bases ("何时该用记忆而非 RAG"). Minimal overlap risk with adjacent skills; the 4 anchor's 'minor overlap risk with closely related skills' is not present.

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

bojieli/ai-agent-book

Path

skills/memory-system/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.