Two-layer memory system with Dream-managed knowledge files.
47
49%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./nanobot/skills/memory/SKILL.mdQuality
Discovery
7%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 uses internal/technical jargon that provides almost no actionable information for skill selection. It fails to describe concrete capabilities, lacks natural trigger terms users would say, and provides no guidance on when the skill should be activated. It reads more like an internal architecture note than a functional skill description.
Suggestions
Describe concrete actions the skill performs, e.g., 'Stores and retrieves conversation context, saves user preferences, and maintains persistent notes across sessions.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to remember something, recall previous context, save notes, or manage persistent knowledge.'
Replace jargon like 'two-layer memory system' and 'Dream-managed knowledge files' with plain language describing what the user experiences or requests.
| 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 lacks any 'when' clause or explicit trigger guidance for when Claude should use this skill. | 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
92%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 actionable search examples. Its strengths are token efficiency and concrete grep commands that Claude can immediately use. The only minor weakness is that referenced files (SOUL.md, USER.md, MEMORY.md) aren't linked or described in terms of their format, though the 'do not edit' constraint is clearly communicated.
| 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 earns its place. The examples are compact and directly useful. | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready grep commands with multiple realistic examples covering different search patterns (keyword, timestamp, count, content mode). The file structure is clearly specified with exact paths and clear do/don't instructions. | 3 / 3 |
Workflow Clarity | For this skill's scope (a memory system with search), the workflow is clear: the structure section explains what exists, the search section provides a progressive approach (count first, then content), and constraints are explicit. The escalation from grep modes to exec as last resort is a well-defined workflow. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections (Structure, Search, Important), but it references files like SOUL.md, USER.md, and MEMORY.md without linking to them or explaining their format. No bundle files are provided, so there's no external reference structure to evaluate, but the skill could benefit from clearer navigation to related resources like the /dream-log command's location. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
90%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 | |
2666582
Table of Contents
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.