CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ac-memory-manager

Manage persistent memory for autonomous coding. Use when storing/retrieving knowledge, managing Graphiti integration, persisting learnings, or accessing episodic memory.

Quality

78%

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 ./skills/ac-memory-manager/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 has a good Quick Start and clean structure with a correct one-level pointer to the real implementation script, but it is padded with redundant sections and concept definitions Claude already knows, and the Quick Start omits the initialize() step needed for cross-session retrieval to work. Trimming the Purpose/Memory Types sections and completing the example would lift it substantially.

Suggestions

Remove the 'Purpose' section and the 'Memory Types' list (or fold a one-line type reference into the store example) — both restate the description or define concepts Claude already knows.

Add the missing 'await memory.initialize()' step to the Quick Start, wrap the example in an async context, and show one more common call such as get() or forget() so the example is copy-paste ready.

Merge the one-line 'Integration' section into the Quick Start or the Graphiti mention in the description to eliminate another redundant section.

DimensionReasoningScore

Conciseness

Half the body is padding: the opening line duplicates the title, the 'Purpose' section restates the frontmatter description, and 'Memory Types' defines episodic/semantic/procedural concepts Claude already knows — several unnecessary sections, matching the anchor-2 example of noticeably verbose content.

2 / 5

Actionability

The Quick Start is concrete near-executable code ('memory = MemoryManager(project_dir)', 'await memory.store(...)') and the API pointer references a real script file, but project_dir is undefined, top-level await lacks a calling context, and key methods (initialize, get, forget) are not shown — minor gaps, not fully copy-paste ready.

4 / 5

Workflow Clarity

A clear sequence (instantiate → store → retrieve) for a simple single-purpose skill, but the omitted 'await memory.initialize()' step means cross-session retrieval silently returns nothing — a minor gap; the skill involves no destructive or batch operations, so no validation cap applies.

4 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections and a single clearly-signaled one-level reference ('See scripts/memory_manager.py') that exists in the bundle, satisfying the simple-skill condition for a top score.

5 / 5

Total

15

/

20

Passed

Description

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

Strong description: third-person voice, explicit 'Use when' clause with concrete triggers, and a distinct niche. Keyword coverage could add common synonyms like 'remember/recall' and the action list contains some redundancy (storing/persisting, retrieving/accessing).

DimensionReasoningScore

Specificity

Lists several concrete actions ('storing/retrieving knowledge, managing Graphiti integration, persisting learnings, or accessing episodic memory') beyond just naming the domain, though several are near-synonyms and somewhat abstract, so coverage falls short of the comprehensive anchor-5 example.

4 / 5

Completeness

Clearly answers both questions: 'Manage persistent memory for autonomous coding' states the what, and an explicit 'Use when storing/retrieving knowledge, managing Graphiti integration, persisting learnings, or accessing episodic memory' clause provides concrete trigger phrases, matching the anchor-5 example exactly.

5 / 5

Trigger Term Quality

Good natural-term coverage ('storing/retrieving knowledge', 'persisting learnings', 'episodic memory', 'Graphiti integration') but misses common variations users would say such as 'remember', 'recall', 'forget', or 'cross-session', fitting the good-coverage-with-a-few-gaps anchor rather than the comprehensive one.

4 / 5

Distinctiveness Conflict Risk

A clear niche (persistent memory via Graphiti/episodic memory) with distinct technical triggers, but phrases like 'storing/retrieving knowledge' could overlap with other memory or knowledge-base skills, so minor overlap risk remains.

4 / 5

Total

17

/

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

fernandezbaptiste/Skrillz

Path

skills/ac-memory-manager/SKILL.md

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.