CtrlK
BlogDocsLog inGet started
Tessl Logo

memory-management

Guide the agent to recall, remember, and route durable learning into Memory, Skills, Scheduled Tasks, or Tape.

62

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./resources/skills/memory-management/SKILL.md
SKILL.md
Quality
Evals
Security

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 an exemplary instruction-only skill: lean, decision-oriented, and concrete about which tool to use, when, and with which trigger cues. The only real improvement would be a compact example of a saved memory entry and the routing rules expressed as a single decision tree.

DimensionReasoningScore

Conciseness

Every line is a decision rule, exclusion, or routing instruction ("Do not remember raw tool results, bash output, grep output, file contents, transient mechanics..."); nothing explains concepts Claude already knows. This matches the 'lean and efficient; every token earns its place' anchor, and there is no padding to push it toward 4.

5 / 5

Actionability

Concrete tool names paired with explicit trigger cues ("Use `memory_recall` when the user refers to previous work with cues such as again, last time, before, continue") and a five-category taxonomy make the guidance directly executable. It is not a 5 only because no example of a written memory entry or invocation syntax for `memory_remember` is shown — a minor gap.

4 / 5

Workflow Clarity

The flow is well sequenced (recall → remember → procedure → recurring) and ends with an explicit six-item end-of-task checklist, giving clear decision checkpoints. It falls short of 5 because this is multi-path routing rather than a single unambiguous action, and the checklist asks questions without stating the follow-through action per branch.

4 / 5

Progressive Disclosure

At ~48 lines with clear section headers and no content that belongs in external files, this fits the guideline that a sub-50-line skill with no need for references scores 5 on well-organized sections alone. No bundle files exist, so there are no buried or nested references to penalize.

5 / 5

Total

18

/

20

Passed

Description

58%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 gives a clear, third-person statement of what the skill does with a distinct subsystem-routing identity, but it omits any explicit 'when to use' trigger guidance and carries only a thin set of natural trigger keywords. Adding a 'Use when...' clause with the user-cued phrases already present in the body would lift both completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause to the description, e.g. "Use when the user asks to remember, recall, or continue earlier work, says 'last time' or 'again', or wants to preserve a reusable procedure or recurring task."

Include a few natural trigger synonyms in the description itself (again, last time, continue, keep, save) rather than leaving them only in the body.

Optionally mention verbatim capture ('preserve an exact statement') in the description so the what-coverage matches the body's full scope.

DimensionReasoningScore

Specificity

"recall, remember, and route durable learning into Memory, Skills, Scheduled Tasks, or Tape" lists several concrete named actions with explicit destinations, matching the 'several specific actions with minor gaps' anchor. It falls short of 5 because coverage stops at routing — verbatim capture, memory categories, and retrieval-evidence distinctions are not mentioned.

4 / 5

Completeness

The 'what' is clear (guide recall, remember, and routing of durable learning), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the judging guideline. It is not a 2 because the 'what' is explicit rather than vague.

3 / 5

Trigger Term Quality

"recall", "remember", and "durable learning" are natural user phrases, but common variations the body itself cites ("again", "last time", "continue", "same project") are absent from the description. This matches 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

Naming the four subsystems ("Memory, Skills, Scheduled Tasks, or Tape") carves a distinct routing niche with only minor overlap risk against generic save/note-taking prompts. It misses a 5 because the anchor example pairs that niche with explicit distinct trigger phrases, which this description lacks.

4 / 5

Total

14

/

20

Passed

Validation

100%

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
ThinkInAIXYZ/deepchat
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.