CtrlK
BlogDocsLog inGet started
Tessl Logo

engram-memory-protocol

Persistent memory discipline for Engram contributors. Trigger: Decisions, bugfixes, discoveries, preferences, or session closure.

61

Quality

71%

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/memory-protocol/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 a tight, well-structured rule set with concrete tool calls, explicit sequencing, and a delivery guarantee. The main gap is the absence of an explicit validation/retry checkpoint for memory writes and worked argument examples.

DimensionReasoningScore

Conciseness

Lean bullet-driven rules with no over-explanation of concepts Claude already knows and no padding; every line is an actionable directive that assumes competence.

5 / 5

Actionability

Names concrete tool calls (mem_save, mem_context, mem_search, mem_session_summary), a structured content schema (What/Why/Where/Learned), and an explicit ordering rule, but provides no example payloads or argument shapes.

4 / 5

Workflow Clarity

Multi-step sequences are clearly numbered (Session Close 1-2, After compaction 1-2-3) with a delivery-guarantee fallback, but there is no explicit validate->fix->retry checkpoint confirming a mem_write succeeded before proceeding.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, with clean well-labeled section headers and no nested references; meets the simple-skill exception allowing a 5 on well-organized sections alone.

5 / 5

Total

18

/

20

Passed

Description

57%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 cleanly pairs a scoping 'what' with an explicit trigger clause, but the triggers are abstract categories rather than concrete natural-language phrases and it lists no concrete capabilities. Tightening the trigger phrasing and naming specific actions would lift specificity and completeness.

Suggestions

Replace abstract trigger categories with natural user phrases, e.g. 'Use when the user asks to remember a decision, recall a previous choice, or wrap up a session'.

Add concrete capabilities, e.g. 'Saves decisions, bugfixes, and preferences; searches and recalls prior context; summarizes sessions'.

Keep the Engram scoping but mirror its tool terms (mem_save/mem_search) in the description to sharpen distinctiveness.

DimensionReasoningScore

Specificity

Names the domain ('Persistent memory discipline') but lists no concrete actions; it states a discipline category rather than capabilities like saving, searching, or summarizing memories, matching the 'names domain, minimal/generic actions' anchor.

2 / 5

Completeness

Both a 'what' ('Persistent memory discipline for Engram contributors') and a 'when' (explicit Trigger clause) are present; the when is explicit but couched as abstract categories rather than concrete user-facing trigger phrases, so it is not a 5.

4 / 5

Trigger Term Quality

The 'Trigger: Decisions, bugfixes, discoveries, preferences, or session closure' line offers relevant categories but they are abstract rather than the natural phrases a user would say (e.g. 'remember this', 'what did we decide'), missing common variations.

3 / 5

Distinctiveness Conflict Risk

The Engram-specific scoping gives it a clear niche with minimal conflict risk, though the broad trigger categories (decisions/bugfixes/discoveries) overlap slightly with general development skills.

4 / 5

Total

13

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Gentleman-Programming/engram
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.