Tessl • The package manager for agent skills

SkillPublic

remember

Explicitly save important knowledge to auto-memory with timestamp and context. Use when a discovery is too important to rely on auto-capture.

Quality

75%

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 ./engineering-team/self-improving-agent/skills/remember/SKILL.md

Quality

Content

75%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 well-structured, actionable instruction set for a simple slash-command skill: a concrete duplicate-check step, exact entry format, a line-budget warning, and clear exclusions. Its main weaknesses are minor — a convoluted and under-specified MEMORY_DIR path derivation, no handling for a missing MEMORY.md file, and slight redundancy between Step 3 and the Tips section. One internal inconsistency: the body says entries don't need timestamps while the frontmatter description promises "timestamp and context".

Suggestions

Replace the convoluted sed pipeline with the actual expected path pattern (or a simple documented example) so the duplicate check is unambiguously executable.

Add one line to the workflow for the missing-file case: create MEMORY.md (with a header) before appending if it doesn't exist.

Dimension	Reasoning	Score
Conciseness	The body is efficient — concrete usage examples, a compact situation table, and a tight 5-step workflow with no explanations of concepts Claude already knows. Minor trimming is possible ("Keep entries concise" in Step 3 repeats the Tips section's "Be concise — one line beats a paragraph"), fitting anchor 4 rather than the every-token-earns-its-place anchor.	4 / 5
Actionability	Concrete, executable guidance is provided: the `grep -ni "<keywords>" "$MEMORY_DIR/MEMORY.md"` duplicate-check command and the `- {{concise fact or pattern}}` entry template, plus ✅/❌ examples in Tips. Minor gaps remain — the `MEMORY_DIR` sed pipeline is convoluted and its expected path convention is never stated — so it sits at anchor 4 rather than fully copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	A clear 5-step sequence (parse → check duplicates → write → suggest promotion → confirm) with an explicit duplicate-check checkpoint and a user decision point ("Update the existing entry or add a new one?"). The gap: no instruction for creating MEMORY.md when it doesn't exist yet, matching anchor 4's minor-validation-gaps profile rather than anchor 5.	4 / 5
Progressive Disclosure	Well-organized single-file skill — Usage, When to Use, Workflow, exclusions, and Tips are cleanly sectioned, and nothing that belongs in a separate file is inlined. At ~93 lines with no external references needed, it fits anchor 4's good-structure profile; navigation is easy but there's no deeper material to signal.	4 / 5
	Total	16 / 20 Passed

Description

62%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 answers both what and when with a clear, concise, third-person statement, but its trigger vocabulary is thin — it misses the natural phrases a user would actually say when invoking this skill. It also promises "timestamp and context", which the skill body explicitly contradicts ("Auto-memory entries don't need timestamps, IDs, or metadata"), creating an expectation mismatch. Solid but not exemplary.

Suggestions

Add natural trigger synonyms users would actually say, e.g. "Use when the user says 'remember this', 'don't forget', or 'keep this in memory'."

Remove "with timestamp and context" or add a concrete second action (e.g., "checks for duplicate entries and warns when MEMORY.md nears its line limit") to raise specificity.

Make the when-clause concrete rather than abstract: replace "a discovery is too important to rely on auto-capture" with specific situations like "after solving a hard debugging problem or learning a project convention".

Dimension	Reasoning	Score
Specificity	"Explicitly save important knowledge to auto-memory" names the domain (auto-memory) and one concrete action (saving knowledge), matching the 1-2-concrete-actions anchor. It does not list several distinct actions, so it falls short of anchor 4.	3 / 5
Completeness	Both a clear "what" ("Explicitly save important knowledge to auto-memory") and an explicit "when" ("Use when a discovery is too important to rely on auto-capture") are present. The when-clause is abstract rather than concrete trigger phrases, so it fits anchor 4, not the explicit-trigger-phrases of anchor 5.	4 / 5
Trigger Term Quality	Relevant keywords like "save", "knowledge", and "auto-memory" are present, but common natural phrases users would say ("remember this", "don't forget", "keep this in mind") are missing — matching the missing-synonyms anchor rather than the good-coverage anchor.	3 / 5
Distinctiveness Conflict Risk	The "auto-memory" niche is mostly distinct, but the description could overlap with closely related memory-management skills (e.g., memory review or promotion to CLAUDE.md), matching anchor 4's minor-overlap characterization rather than a fully distinct niche.	4 / 5
	Total	14 / 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: alirezarezvani/claude-skills
Path: engineering-team/self-improving-agent/skills/remember/SKILL.md
Revision: 27cfcd0

Reviewed: 21 hours ago

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.

remember

Table of Contents

Is this your skill?