memory

Two-layer memory system with Dream-managed knowledge files.

Quality

47%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./nanobot/skills/memory/SKILL.md

Quality

Discovery

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

This description is extremely vague and fails to communicate what the skill actually does or when it should be used. It relies on internal jargon ('Dream-managed', 'two-layer memory system') that would not help Claude select this skill appropriately. It needs a complete rewrite with concrete actions and explicit trigger conditions.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Stores and retrieves persistent context across conversations, organizes knowledge into short-term and long-term memory files.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to remember something, recall previous context, manage notes, or store knowledge for future sessions.'

Replace jargon like 'Dream-managed' with plain language that describes the mechanism or benefit in terms users would understand.

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like 'two-layer memory system' and 'Dream-managed knowledge files' without describing any concrete actions the skill performs. No specific operations are listed.	1 / 3
Completeness	The description barely addresses 'what' (a memory system) in vague terms and completely omits 'when' — there is no 'Use when...' clause or any explicit trigger guidance.	1 / 3
Trigger Term Quality	The terms 'two-layer memory system' and 'Dream-managed knowledge files' are technical jargon that users would never naturally say. There are no natural keywords a user would use to invoke this skill.	1 / 3
Distinctiveness Conflict Risk	The mention of 'Dream-managed' and 'two-layer memory system' is somewhat distinctive terminology that narrows the domain, but the overall vagueness could still cause confusion with other memory or knowledge management skills.	2 / 3
	Total	5 / 12 Passed

Implementation

87%

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

This is a well-crafted, concise skill that clearly defines a two-layer memory system with appropriate constraints. Its strongest aspects are the concrete grep examples and the clear delineation of managed vs. user-accessible files. The only notable weakness is that the search workflow could be more explicitly sequenced with clearer decision points.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It doesn't explain what JSONL is beyond what's needed, doesn't over-explain grep, and every section serves a clear purpose. The constraint warnings are appropriately brief.	3 / 3
Actionability	Provides concrete, copy-paste-ready grep examples with specific parameters (case_insensitive, fixed_strings, output_mode, etc.). The file structure is clearly enumerated with exact paths. The guidance on search strategy (count first, then content) is specific and practical.	3 / 3
Workflow Clarity	The search workflow has a reasonable progression (count → files_with_matches → content), but it's described implicitly rather than as explicit steps. The skill lacks a clear workflow for what to do when information is found to be outdated (just says 'Dream will fix it'), and there's no validation checkpoint for search results.	2 / 3
Progressive Disclosure	For a skill of this size and scope, the content is well-organized into clear sections (Structure, Search Past Events, Important). The referenced files (SOUL.md, USER.md, MEMORY.md, history.jsonl) are clearly listed with their purposes. No bundle files are needed for this straightforward skill.	3 / 3
	Total	11 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: HKUDS/nanobot
Commit: ab9f499

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.