remember

Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/remember/SKILL.md

Quality

Content

86%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.

The body is a lean, well-organized instruction skill with a clear sequenced workflow and a useful classification taxonomy. The main gap is the absence of worked examples and an explicit verify-before-write feedback loop for the destructive/overwriting aspect of writing to memory.

Suggestions

Add 1-2 short worked examples showing how a sample session finding is classified and routed to a specific surface.

Insert an explicit verification step before writing (e.g. confirm the target surface and check for an existing conflicting entry before overwriting).

Show the concrete write targets or commands for each memory surface so guidance is fully actionable.

Dimension	Reasoning	Score
Conciseness	The body is lean and sectioned (Goal, Memory surfaces, Workflow, Rules, Output) with no padding or explanation of concepts Claude already knows; every section earns its place, matching the level-5 anchor.	5 / 5
Actionability	Concrete instruction-only guidance is given via an explicit classification taxonomy and per-item destination routing, but there are no worked examples of each category or exact write targets, so it is mostly executable with minor gaps rather than fully copy-paste ready.	4 / 5
Workflow Clarity	A clear five-step sequence runs gather to conflict call-out, and step 5 plus the uncertainty rule act as soft validation checkpoints; however there is no explicit verify-before-overwrite feedback loop, so it sits at level 4 rather than 5.	4 / 5
Progressive Disclosure	This is a simple skill under 50 lines with no external references needed, and it is organized into clear, well-signaled sections, so per the simple-skills scoring note it qualifies for the level-5 anchor.	5 / 5
	Total	18 / 20 Passed

Description

53%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.

The description clearly states what the skill does and names its target surfaces, giving it a distinct niche, but it omits any "Use when..." trigger guidance and lacks natural user-facing trigger phrases. Adding an explicit when-to-use clause with common synonyms would lift completeness and trigger_term_quality.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when the user asks to save, remember, or organize knowledge from a session.'

Add natural trigger synonyms users actually say ('save this', 'remember this', 'keep this for later', 'add to memory').

Optionally enumerate a couple more concrete actions (e.g. 'classify, deduplicate, and route') to raise specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ("Review reusable project knowledge" and "decide what belongs" across named surfaces), but does not enumerate several specific actions, matching the level-3 anchor; it is above generic single-action phrasing yet below the multi-action coverage of level 4.	3 / 5
Completeness	The description gives a clear "what" but no "Use when..." clause or equivalent explicit trigger, so per the judging guidelines completeness is capped at 3; it is not level 2 because the "what" is clear, and not level 4 because the "when" is absent.	3 / 5
Trigger Term Quality	Relevant keywords like "project memory", "notepad", and "durable docs" are present, but common natural variations a user would say (e.g. "save this", "remember this", "keep this for later") are missing, matching level 3 rather than the broader coverage of level 4.	3 / 5
Distinctiveness Conflict Risk	The memory-surface routing niche is mostly distinct with named target surfaces and minor overlap risk with related memory skills; it is more specific than the broad level-3 anchor but lacks the fully concrete triggers of level 5.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Yeachan-Heo/oh-my-claudecode
Path: skills/remember/SKILL.md
Commit: dc7ba1d

Reviewed: 3 days 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.