CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

persistent-memory

Persists topic-scoped context across conversations as plain markdown with write, read, consolidate, and forget operations, a never-store list for secrets, and a consent preview before every write. Triggers on "remember this", "save to memory", "what do you remember about", "forget that", "/persistent-memory".

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

Quality

Content

52%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 SKILL.md body is well-structured as a gated, per-operation index with clear sequencing and real consent/validation checkpoints, but the bundle does not deliver what it promises: every referenced rules/ and templates/ file is missing, so the skill cannot actually be executed past phase 0 of any operation. Redundant restatement of the gates across three sections further inflates the token cost of an index whose substance lives elsewhere.

Suggestions

Ship the referenced bundle files: all 11 rules/*.md files and templates/pointer-snippet.md linked from the 'Required Reading by Operation' table are absent from the bundle, dead-ending every operation at phase 0. Add them, or inline the minimal content each operation needs to run.

Collapse the triple restatement of the write gates (Core Workflow gate column, Core Principles, and Definition of Done) into a single location, and link each rules/*.md file once per section instead of repeating it in every row of a phase table.

Link references/research-sources.md directly (e.g., from the Reflexion note in Core Principles) and remove its dangling ../rules/scaling-tiers.md pointer, so the one bundle file that exists is actually reachable.

DimensionReasoningScore

Conciseness

The body avoids teaching known concepts and uses compact tables, but the same content is restated three times: Core Principles ("Two-phase write... Extract candidates first, then resolve each..."), Anti-patterns ("Re-recording the same fact instead of UPDATE-ing"), and Definition of Done ("Candidate list shown to the user with ADD / UPDATE / DELETE / NOOP tags") all re-encode the phase-table gates, and phase tables repeat the same rules/*.md link up to five times in one table. This is beyond anchor 4's 'minor instances that could be trimmed' but short of anchor 2's padded prose, so 3 fits best.

3 / 5

Actionability

Concrete elements are present (exact paths like `~/.agent-memory/<scope>/`, named files INDEX.md/AUDIT.log, `$0 == "write"` parsing, a literal pointer snippet, a literal summary string "Saved N memories to <scope> (<tier>)."), but every phase's operational substance — the never-store list contents, candidate extraction, merge criteria, staleness cutoffs — is deferred to rules/*.md files that do not exist in the bundle, so key details are missing rather than minor. That places it at anchor 3 ('some concrete guidance but incomplete'), not 4.

3 / 5

Workflow Clarity

Each operation has an explicitly sequenced phase table with a named gate per phase plus a global gate rule ("Do not proceed to the next phase until the prior phase's gate passes"), and destructive operations carry real validation ("User saw the entries and explicitly confirmed", consent preview, AUDIT.log), so the destructive-operation cap does not apply. Not 5: no error-recovery feedback loops are specified for failed gates, and the step-level detail lives in the missing rules files, leaving minor validation gaps at anchor 4.

4 / 5

Progressive Disclosure

The written design matches the top anchor (thin index, per-operation 'Required Reading' table, one-level-deep links), but scoring against the actual bundle shows all 11 referenced rules/*.md files and templates/pointer-snippet.md are absent — every on-demand read dead-ends. The only bundle file present, references/research-sources.md, is never directly linked from SKILL.md and itself points to a missing ../rules/scaling-tiers.md. The disclosure structure is claimed but not delivered, which is worse than anchor 3's 'references present but not clearly signaled'.

2 / 5

Total

12

/

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.

A strong description: concrete capability list, explicit trigger phrases, and a well-delineated niche. The main gaps are minor — the `list` operation is unmentioned and a few natural trigger synonyms ("recall", "add to memory") are absent — which keeps specificity and trigger quality at 4 rather than 5.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("write, read, consolidate, and forget operations", "a never-store list for secrets", "a consent preview before every write") with a concrete storage form ("plain markdown"), matching the anchor for several specific actions. It is not 5 because the `list` operation from the body is omitted and the actions are bare operation names rather than comprehensive action+object coverage; it clearly exceeds 3's '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers both questions: 'what' ("Persists topic-scoped context across conversations as plain markdown with write, read, consolidate, and forget operations, a never-store list for secrets, and a consent preview before every write") and 'when' via an explicit trigger clause ("Triggers on 'remember this', 'save to memory'...") with concrete trigger phrases, matching the anchor-5 example's structure. The 'when' is as explicit as the top anchor, so 4 (when 'could be more explicit') does not fit.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say ("remember this", "save to memory", "what do you remember about", "forget that", "/persistent-memory"), giving good keyword coverage. Not 5: common variations present in the body's own trigger table ("recall", "add to memory", "list memory", "what do you know about") are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (topic-scoped markdown memory with consent/forget) with distinct triggers and a slash-command name, so well above anchor 3's overlap risk. Not 5: generic memory requests like "what do you remember about" and "remember this" are exactly the phrases answered by built-in/host memory features, leaving minor conflict risk with closely related memory tooling.

4 / 5

Total

17

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 38 missing

Warning

Total

13

/

16

Passed

Repository

mthines/agent-skills

Path

skills/authoring/persistent-memory/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.