memory-manager

External persistent memory for cross-session knowledge. Use when storing error patterns, retrieving learned solutions, managing causal memory chains, or persisting project knowledge.

Quality

76%

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/memory-manager/SKILL.md

Quality

Content

71%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 well-organized with concrete, mostly executable code examples covering the core memory operations. Its weaknesses are broken bundle-file references, a duplicated inline taxonomy that already has a reference file, and minor verbosity in the ASCII and conceptual blocks.

Suggestions

Remove or create the two missing referenced files (references/RETRIEVAL-PATTERNS.md and scripts/knowledge_base.py) so every listed reference resolves to a real bundle file.

Trim the inline ASCII Memory Types box since references/MEMORY-TYPES.md already documents the taxonomy; keep a one-line pointer instead to avoid duplication.

Replace the "project_dir" placeholder in the Quick Start snippet with a concrete value or a one-line definition so the example is fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete code blocks and short sections, but the ~26-line ASCII "Memory Types" box and the illustrative "Causal Memory Pattern" block are mildly over-explanatory and could be trimmed, fitting anchor 4 rather than the fully lean anchor 5.	4 / 5
Actionability	Code examples for store, store_causal_chain, and get_similar_errors are concrete and largely copy-paste ready, with only minor gaps such as the undefined project_dir argument, matching anchor 4 rather than the fully executable anchor 5.	4 / 5
Workflow Clarity	The discrete memory operations are presented clearly and unambiguously, but the body exceeds 50 lines and there is no end-to-end sequenced workflow with validation checkpoints, so it sits at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	Structure is well-sectioned with a dedicated References block, but two referenced bundle files do not exist (references/RETRIEVAL-PATTERNS.md and scripts/knowledge_base.py) and the Memory Types taxonomy is duplicated inline while references/MEMORY-TYPES.md already exists, fitting anchor 3 (some structure, organization gaps) better than anchor 4.	3 / 5
	Total	15 / 20 Passed

Description

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

A strong, specific description that clearly answers both what the skill does and when to use it, with concrete enumerated actions. Its main weakness is trigger-term naturalness: "causal memory chains" is internal jargon and common user phrasings/synonyms are absent.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "storing error patterns, retrieving learned solutions, managing causal memory chains, or persisting project knowledge" — giving comprehensive coverage of the memory operations, matching the anchor 5 example that enumerates four specific actions.	5 / 5
Completeness	Explicitly states both what ("External persistent memory for cross-session knowledge") and when ("Use when storing error patterns, retrieving learned solutions, managing causal memory chains, or persisting project knowledge") with concrete trigger phrases, matching anchor 5.	5 / 5
Trigger Term Quality	Terms like "error patterns", "learned solutions", and "persisting project knowledge" are reasonably natural, but "causal memory chains" is internal jargon a user would not naturally say, and common synonyms/file-extension-style variations are missing, so it fits anchor 3 rather than 4.	3 / 5
Distinctiveness Conflict Risk	The "external persistent memory" / "causal memory chains" niche is mostly distinct, but "persisting project knowledge" is broad enough to overlap with general context or memory-related skills, placing it at anchor 4 rather than 5.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/memory-manager/SKILL.md
Commit: 93ed392

Reviewed: 2 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.