CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

80%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 tight, highly actionable instruction-only skill body with concrete tool calls, paths, and content rules. Its main weakness is workflow clarity: merges and rewrites of existing memory files proceed without any verification step despite being destructive batch operations. A minor duplication of the no-rescan instruction could also be trimmed.

Suggestions

Add a validation checkpoint after writing a merged file, e.g. re-read the file with file_reader to confirm the merge preserved existing facts and valid frontmatter before moving to the next item.

Deduplicate the repeated instruction not to list the memories directory (lines 23 and 74), keeping it only in the pre-loaded-files section.

Clarify what counts as 'stale parts' when merging (e.g. superseded facts vs. contradicted preferences) so the destructive drop step is less ambiguous.

DimensionReasoningScore

Conciseness

The body is lean and prescriptive with no re-taught concepts, but the "do NOT re-scan the directory" instruction is duplicated ("do NOT re-scan the directory with terminal or file_reader" and "Do NOT use terminal or file_reader to list the memories directory"), which could be trimmed.

4 / 5

Actionability

Fully actionable for an instruction-only skill: exact paths (~/.clacky/memories/<topic-slug>.md), concrete tool calls (file_reader(path: ...)), slug rules with examples, numeric size limits, an absolute-date example, and a complete frontmatter template.

5 / 5

Workflow Clarity

The two-step workflow (pick target file with match/no-match branches, then write) is clearly sequenced, but merging and rewriting existing memory files is destructive and items are processed in batch, with no validation/verification checkpoint — the rubric's destructive/batch cap applies.

3 / 5

Progressive Disclosure

No bundle files exist and none are needed; all ~63 lines of content belong inline in this single-purpose subagent prompt, organized under clear sections (Existing Memory Files, Workflow, Guidelines) with easy navigation.

5 / 5

Total

17

/

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 with explicit what/when structure, concrete sub-capabilities, and natural trigger phrasing. It uses appropriate third-person imperative voice and stays concise. Minor improvements possible by adding common trigger synonyms and sharpening the overlap boundary with conversation-review skills.

DimensionReasoningScore

Specificity

Lists several specific actions ("Handles file naming, topic merging, frontmatter, and size limits") plus a concrete storage path, but the lead action "Persist information to long-term memory" is somewhat abstract, leaving minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both what ("Persist information to long-term memory at ~/.clacky/memories/" plus concrete sub-tasks) and when ("Use when the user asks you to remember/note something, or when reviewing a finished conversation") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"asks you to remember/note something" and "facts worth keeping" are natural user phrasings, but common synonyms like "keep this in mind", "don't forget", or "save this" are missing.

4 / 5

Distinctiveness Conflict Risk

The remember/note trigger and dedicated memory directory form a clear niche, but "reviewing a finished conversation for facts worth keeping" risks overlap with summarization or review skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.