memory-tasks

Task management via Basic Memory schemas: create, track, and resume structured tasks that survive context compaction. Uses BM's schema system for uniform notes queryable through the knowledge graph.

Quality

70%

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 ./skills/memory-tasks/SKILL.md

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.

The body is a strong, executable reference: concrete BM tool calls with real parameters, a clear task lifecycle, and tight, jargon-free sections with no filler. Its only weaknesses are advisory rather than embedded validation checkpoints and slight repetition of resume guidance across sections.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — no padding explaining what Basic Memory or tasks are, and every section gives operational guidance. Small redundancies (resume guidance appears in "Resuming After Compaction", "Pre-Compaction Flush", and the Guidelines) keep it just below the 5 anchor.	4 / 5
Actionability	Fully executable, copy-paste-ready guidance: a complete `write_note` call with real parameters, an `edit_note` update snippet, and a query cheat-sheet table of `search_notes`/`schema_validate`/`schema_diff` invocations covering create, resume, update, complete, and query. Specific examples cover the common cases exactly as the 5 anchor requires.	5 / 5
Workflow Clarity	Clear sequences throughout — numbered steps for resuming after compaction and pre-compaction flush, plus a full create → update → complete lifecycle. Validation exists but only as an advisory guideline ("run schema_validate periodically") rather than an explicit checkpoint inside each workflow, which is the minor gap that separates this from 5.	4 / 5
Progressive Disclosure	No bundle files exist and none are needed: the ~170-line body is self-contained, well-sectioned, and easy to navigate. It is not 5 only because the Task schema YAML and the query table are natural candidates for a reference file if the skill grows.	4 / 5
	Total	17 / 20 Passed

Description

58%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 states a clear, concrete "what" tied to a specific technology (Basic Memory schemas), but omits any "when to use" trigger guidance, which caps its usefulness for routing. It also leans on internal jargon (BM, schema system, knowledge graph) over natural user phrasing.

Suggestions

Add an explicit trigger clause, e.g. "Use when starting multi-step work that may outlast the context window, when resuming work after compaction or restart, or when the user asks to create or check tasks."

Include natural synonyms users would actually say, such as "todo", "task list", "in-progress work", or "pick up where I left off", alongside the current terms.

Lead with the concrete capability verbs (create, update, complete, query, resume tasks) and trim jargon like "uniform notes queryable through the knowledge graph", which users would not naturally say.

Dimension	Reasoning	Score
Specificity	Names the domain ("Task management via Basic Memory schemas") and three concrete actions ("create, track, and resume structured tasks"), matching the anchor for several specific actions with minor gaps. It falls short of 5 because updating, completing, and querying tasks — covered in the body — are absent from the description.	4 / 5
Completeness	The "what" is clear (create, track, and resume structured tasks via BM schemas), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the "what" is concrete and specific, not vague.	3 / 5
Trigger Term Quality	Relevant keywords like "task management", "track", "resume", and "context compaction" are present, but common natural variations users would say ("todo", "task list", "in-progress work") are missing. Phrases like "BM's schema system" and "uniform notes queryable through the knowledge graph" are jargon rather than user speech, so this fits the 3 anchor better than 4.	3 / 5
Distinctiveness Conflict Risk	"Basic Memory schemas", "BM", and "knowledge graph" anchor a clear niche with distinct triggers, leaving only minor overlap risk with generic task/todo tracking skills. Not 5 because "task management" alone is a broad phrase that could collide with built-in task-tracking tools absent the BM qualifier.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: basicmachines-co/basic-memory
Path: skills/memory-tasks/SKILL.md
Commit: 194afe1

Reviewed: 7 days 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.