CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory-lifecycle

Manage note status transitions in Basic Memory: archive completed work, move notes between status folders, update frontmatter. Use when marking items complete or archiving entities.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, actionable skill body: concrete tool calls throughout, a clear sequenced workflow with ambiguity handling, and good single-file organization. The main tightening opportunities are the redundant Guidelines recap and the repetitive folder-convention examples, plus adding an explicit post-move verification step.

DimensionReasoningScore

Conciseness

The body is efficient and code-forward with no explanations of concepts Claude already knows, but the Guidelines section restates points already made ("Archive, never delete", permalink behavior, move-then-edit order) and Folder Conventions shows three near-identical folder trees, which is more than the anchor-5 "every token earns its place" but only minor trimming beyond anchor 3.

4 / 5

Actionability

Fully executable, copy-paste-ready tool calls with complete parameters (bm_search, bm_move, bm_edit with command and metadata), exact identifiers and destinations, a worked revert example, and a concrete confirmation output format covering the common cases.

5 / 5

Workflow Clarity

The four-step workflow (find, move, update frontmatter, confirm) is clearly sequenced with ambiguity checkpoints ("present options and ask which one", "don't guess"), batch confirmation, and locked-note failure handling, but there is no explicit post-move/post-edit verification step, so it sits below anchor 5's explicit validation loops. The destructive/batch cap does not apply since moves are non-destructive and batch operations include a confirm-the-list step.

4 / 5

Progressive Disclosure

As a single-file skill with no bundle files, it is well-sectioned with clear headers, tables, and cross-references to sibling skills (memory-tasks, memory-notes, memory-defrag); minor gaps such as the longish Edge Cases and Folder Conventions sections keep it below a fully optimized anchor-5 structure.

4 / 5

Total

17

/

20

Passed

Description

75%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 concise, third-person description that explicitly covers both capabilities and trigger conditions for a clearly named system. Its main weakness is that the when-clause and action list capture only the completion/archiving slice of the skill's broader status-lifecycle scope.

DimensionReasoningScore

Specificity

Names the domain (Basic Memory) and three concrete actions — "archive completed work", "move notes between status folders", "update frontmatter" — but omits capabilities the skill covers such as reactivating/reverting archived items, so it falls short of the comprehensive anchor 5.

4 / 5

Completeness

Both what (three concrete status-transition actions) and when ("Use when marking items complete or archiving entities") are explicit, but the when-clause covers only completion/archiving and not the pausing, reactivation, and periodic-cleanup triggers the skill documents, so it does not reach the fully comprehensive anchor 5.

4 / 5

Trigger Term Quality

Natural phrases users would say are present ("marking items complete", "archiving entities"), giving good keyword coverage, though common variations like "done", "finished", or "cancelled" that the skill body handles are missing from the description.

4 / 5

Distinctiveness Conflict Risk

"Basic Memory" and status-folder transitions carve out a clear niche with distinct triggers, but closely related sibling skills (memory-tasks, memory-notes) share territory around task completion and note updates, creating minor overlap risk.

4 / 5

Total

16

/

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

basicmachines-co/basic-memory

Path

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