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

67%

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

76%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 content is highly actionable with executable code and clear procedures, well-structured and token-efficient. Its main weakness is that batch/stateful workflows lack explicit validation-then-fix feedback loops despite the skill's own validation tooling being documented.

Suggestions

Embed an explicit validate->fix->retry checkpoint in the Pre-Compaction Flush and Resuming workflows (e.g., run schema_validate(noteType="Task") and resolve drift before updating).

Move the full Task schema YAML block into a referenced schema file (e.g., references/Task-schema.md) and summarize it inline to better separate overview from detail.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence, with mostly earned content; only minor asides (e.g., the "Why both frontmatter and observations?" paragraph) could be trimmed, fitting the efficient-with-minor-over-explanation anchor rather than the lean 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready code (write_note, search_notes calls), concrete YAML snippets, and a query table with exact API calls covering the common cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	Create/resume/update/complete/flush steps are clearly sequenced, but validation checkpoints are not embedded in the workflows even though the skill performs batch state updates (pre-compaction flush updates all active tasks); validation tools exist but are implicit, fitting the steps-present-but-checkpoints-missing anchor and the batch-operation cap.	3 / 5
Progressive Disclosure	As a single self-contained file with no bundle directories, it is well-organized under clear section headers with easy navigation; the inlined Task schema and query table are appropriately placed for a single-file skill, leaving only minor organization gaps versus the ideal 5.	4 / 5
	Total	16 / 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 concrete capabilities and is tied to a distinct Basic-Memory niche, but it omits any explicit "Use when..." trigger guidance and leans on technical jargon, capping completeness and trigger-term quality.

Suggestions

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

Surface more natural user-facing keywords/synonyms (e.g., "to-do", "track work", "resume work after restart") alongside the technical terms.

Spell out "Basic Memory" on first use rather than abbreviating to "BM" to aid discoverability.

Dimension	Reasoning	Score
Specificity	The phrase "create, track, and resume structured tasks" names three concrete actions within the named task-management domain, which lists several specific actions with only minor gaps, but it is not comprehensive like the score-5 anchor.	4 / 5
Completeness	It clearly answers "what" (create, track, and resume structured tasks) but provides no "Use when..." or equivalent explicit "when" guidance, so per the judging guidelines a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms like "tasks" and "task management" appear, but the coverage leans on technical jargon ("context compaction", "BM's schema system", "knowledge graph") and misses common synonyms a user would say; it falls below the good-keyword-coverage of a 4.	3 / 5
Distinctiveness Conflict Risk	"Task management via Basic Memory schemas" ties the skill to a specific subsystem giving it a clear niche with only minor overlap risk against generic task/todo skills, fitting mostly-distinct better than the somewhat-specific 3.	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: a5fb68e

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