CtrlK
BlogDocsLog inGet started
Tessl Logo

memory-search-best-practices

记忆系统多刀检索 + recall coverage 策略(8 类题型 recipe)。 Use when: 任务是 "哪些地方提过 X" / "X 的来源 / source map" / "有没有提过 Y / absence check" / "上次到现在变了什么 / delta" / 冷启动 onboard 复杂主题 / 任何召回任务搜了一刀觉得不够。 Not for: 只是选哪个入口走第一刀(用 memory-navigation)/ 已知精确 anchor 单 Read(直接 Read)/ 代码符号查(Grep/LSP)/ 新功能开发(不是 recall 任务)。 Output: 多 query 多 scope 召回 union 结果 + coverage matrix(item/source/谁提到/直接 vs 间接)+ "何时停下来"判据。 GOTCHA: 和 memory-navigation 互补不重叠 — memory-navigation 决定**第一刀走哪个工具**(search vs graph vs list_recent),本 skill 决定**要不要补刀 + 题型对应几刀几路 + 何时停**。Ragdoll家族(含 47/46/4.5/sonnet)必加载:治 magic word "我能猜出来 / 碎片够了 / 1 刀够了"病。

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, highly actionable body that gives parameterized tool calls, per-question-type recipes, and explicit stop criteria with feedback loops. Its main weaknesses are redundancy between the recipe and stop-criteria tables and a monolithic structure with no progressive disclosure into reference files.

Suggestions

Merge or cross-reference the '8 类题型 → recipe' and '何时停下来判据' tables — they cover overlapping ground and could be a single table with recipe + stop-condition columns, saving meaningful tokens.

Move the 'AUDHD coverage 案例 5 步 recipe' and/or 'Common Mistakes' into a references/ file (e.g. WORKED_EXAMPLE.md) and link to it from the body, enabling progressive disclosure and a leaner SKILL.md.

Drop the '和其他 Skill 的区别' table or trim it to one line, since the frontmatter GOTCHA and the '链入下一步' section already convey the same memory-navigation distinction.

DimensionReasoningScore

Conciseness

Mostly efficient and dense with task-specific knowledge Claude lacks, but the '何时停下来判据' table largely re-states the '8 类题型 → recipe' table, and the '和其他 Skill 的区别' section repeats the frontmatter GOTCHA. Not a 3 because of this verifiable redundancy; not a 1 because no padding with concepts Claude already knows.

2 / 3

Actionability

Concrete, parameterized calls throughout — 'search_evidence("audhd adhd asd", hybrid, scope=docs, limit=10)', 'graph_resolve(anchor, depth=1, relations=[feature_ref,related_to])', 'list_recent(scope=threads, since=N天)' — plus a fully spelled-out 5-step recipe. Copy-paste-ready executable guidance, matching the 3-anchor.

3 / 3

Workflow Clarity

Multi-step recipes are explicitly sequenced with validation/feedback checkpoints: '≥3 路命中无新 anchor 才停', '高置信命中 → 必 Read 原文', and magic-word force-stops ('我能猜出来' → 停). Clear sequence with explicit validation and error-recovery loops, matching the 3-anchor.

3 / 3

Progressive Disclosure

Sections are well-organized with clear headers, but the file is a single monolithic SKILL.md with no bundle files and no one-level-deep references offloading detail; the AUDHD 5-step case study and Common Mistakes table are inline material that could be split. Not a 3 because progressive disclosure into references is absent; not a 1 because organization is genuinely clear.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exceptionally well-structured description: it specifies concrete capabilities, provides explicit Use-when/Not-for triggers, names an output contract, and preempts a known conflict with a sibling skill. Voice is consistently third-person and trigger terms are natural and varied.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '多刀检索 + recall coverage 策略(8 类题型 recipe)' and an explicit 'Output: 多 query 多 scope 召回 union 结果 + coverage matrix + 何时停下来判据'. This matches the 3-anchor 'lists multiple specific concrete actions'.

3 / 3

Completeness

Explicitly answers 'what' (multi-cut retrieval + coverage strategy + 8 recipes), 'when' (Use when:), and even 'when not' (Not for:). Clearly answers both what AND when with explicit triggers, matching the 3-anchor.

3 / 3

Trigger Term Quality

Both an inline 'Use when:' clause and a dedicated 'triggers:' list cover natural phrases users would say — '哪些地方提过', 'source map', 'absence check', 'delta', '全集', 'provenance'. Good coverage of common variations, matching the 3-anchor.

3 / 3

Distinctiveness Conflict Risk

An explicit 'GOTCHA:' clause distinguishes it from memory-navigation ('第一刀走哪个工具' vs '补刀策略'), plus a 'Not for:' clause. Clear niche with distinct triggers, unlikely to conflict — the 3-anchor.

3 / 3

Total

12

/

12

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.

Validation15 / 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
zts212653/clowder-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.