CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/memory-tasks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-crafted, highly actionable skill body: executable tool calls with concurrency-safe editing, clearly sequenced resume and flush workflows, and a useful query reference. Remaining gaps are minor — slight redundancy in the guidelines section, a couple of incomplete call examples, and no explicit verification step in the batch flush.

DimensionReasoningScore

Conciseness

The body is operational and dense — schema YAML, concrete tool calls, and a query table with no padding or explanation of concepts Claude already knows. It is not 5 because the final Guidelines section repeats points already made in Key Principles (context guidance, linking relations), and 'Why both frontmatter and observations?' could be tightened.

4 / 5

Actionability

Provides copy-paste-ready bm_write, bm_search, and bm_edit calls with concrete metadata, filters, and checksum parameters, plus a query table covering common cases. Not 5: body updates are shown only as target markdown without the corresponding edit call, and 'Completing Tasks' shows a YAML fragment rather than an executable call.

4 / 5

Workflow Clarity

Resume-after-compaction and pre-compaction flush are clearly numbered, and the checksum conflict loop ('re-read before writing') is an explicit feedback loop for concurrent edits. Not 5 because the batch flush workflow lacks a per-task verification checkpoint, and validation (bm_schema_validate) is recommended rather than embedded as a workflow step.

4 / 5

Progressive Disclosure

No bundle files exist, and the single-file body is well-organized into clearly headed sections with content appropriately placed inline (schema, examples, query reference). Not 5 because the '(see memory-notes)' pointer is only lightly signaled and the ~205-line body could move the schema definition or query table to a reference file.

4 / 5

Total

16

/

20

Passed

Description

66%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 specific, tool-anchored description that clearly states what the skill does, with good natural trigger terms and low conflict risk. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which leaves the 'when to use' guidance only weakly implied.

Suggestions

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

Include common user synonyms such as "to-do list", "checklist", or "work in progress (WIP)" alongside "tasks" to broaden natural trigger coverage.

Mention the update, complete, and query/search operations explicitly to close the coverage gap left by the generic verb "track".

DimensionReasoningScore

Specificity

Names the domain ("Task management via Basic Memory schemas") and lists three concrete actions ("create, track, and resume structured tasks that survive context compaction"), matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because update, complete, and query operations are only implied by 'track', and short of 3-level coverage since more than 1-2 actions are explicitly listed.

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, capping completeness at 3 per the judging guidelines. 'When' is only weakly implied by the compaction mention, so it does not reach the 4 anchor's explicit-but-imprecise 'when'.

3 / 5

Trigger Term Quality

Includes natural phrases users would say such as "task management", "create", "track", "resume", and "context compaction", matching 'good keyword coverage; a few natural terms missing'. Not 5 because common synonyms like "to-do list", "checklist", or "work in progress" are absent; not 3 because coverage goes beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

"via Basic Memory schemas", "BM's schema system", and "knowledge graph" tie the description to a specific tool, giving it a clear niche with mostly distinct triggers. Minor overlap remains with generic task/todo-management skills, keeping it below the 5 anchor's minimal conflict risk.

4 / 5

Total

15

/

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-tasks/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.