persist-memory

Persist information to long-term memory at ~/.clacky/memories/. Use when the user asks you to remember/note something, or when reviewing a finished conversation for facts worth keeping. Handles file naming, topic merging, frontmatter, and size limits.

Quality

80%

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 ./lib/clacky/default_skills/persist-memory/SKILL.md

Quality

Content

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

A compact, actionable, well-structured instruction skill that mostly assumes Claude's intelligence. Its main weakness is workflow clarity: a batch, overwrite-capable operation with no validation/verification step, which the rubric caps at 3.

Suggestions

Add an explicit validation checkpoint after writing — e.g., re-read the file or confirm the frontmatter parses and no existing content was lost before reporting success — since this workflow overwrites memory files and processes multiple items.

De-duplicate the "do NOT re-scan the directory" and "you do NOT decide whether to write" guidance so each appears once, trimming redundant tokens.

Include one short concrete example of a merged file (frontmatter + integrated content) to push actionability from mostly-executable to copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and avoids explaining known concepts, but the "do NOT re-scan" / "do NOT decide whether to write" admonitions are repeated across the intro and Guidelines and could be trimmed.	4 / 5
Actionability	It gives concrete tool calls (file_reader with a path), explicit new-file paths, slug rules, and a frontmatter template, but stops short of a full copy-paste example file showing merged content.	4 / 5
Workflow Clarity	The two-step sequence (pick target file, write) is clear, but this is a batch/overwrite operation ("For each item to persist"; overwrites existing files dropping "stale parts") with no validation checkpoint to confirm writes or guard against data loss, capping the score at 3.	3 / 5
Progressive Disclosure	At under 50 lines and single-purpose with no need for external references, the body is well-organized into clear sections (Workflow, Guidelines, sub-steps), satisfying the simple-skill exception for a top score.	5 / 5
	Total	16 / 20 Passed

Description

87%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, third-person description that concretely names its actions and gives explicit, natural trigger phrases for when to use it. It is distinctive and complete; only minor synonym/coverage gaps keep specificity and trigger quality from a perfect score.

Dimension	Reasoning	Score
Specificity	"Persist information to long-term memory" and "Handles file naming, topic merging, frontmatter, and size limits" list several concrete actions, but coverage is not quite comprehensive enough for a 5.	4 / 5
Completeness	It explicitly states both what it does (persist to ~/.clacky/memories/, handle naming/merging/frontmatter/size limits) and when to use it with concrete trigger phrases.	5 / 5
Trigger Term Quality	"Use when the user asks you to remember/note something, or when reviewing a finished conversation for facts worth keeping" gives good natural trigger phrases, though a few synonyms (e.g. "keep in mind", "save this") are missing.	4 / 5
Distinctiveness Conflict Risk	Memory persistence is a clear niche with distinct triggers ("remember/note something", "reviewing a finished conversation"), giving minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: clacky-ai/openclacky
Path: lib/clacky/default_skills/persist-memory/SKILL.md
Commit: 8a66b10

Reviewed: 1 day 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.