CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory-comark

Write Basic Memory notes that render as charts, tables, boards, and live views with `::bm-*` Comark components. Use when a note reads better as a figure or board, or already has `::bm-*` directives.

Quality

92%

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

92%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.

An exemplary skill body: concrete syntax examples, a working query language with shape constraints per component, explicit read-back validation for live views, and a well-structured split between inline essentials and a single well-signaled reference file. The only improvement area is trimming a handful of elaborate prose passages in the snapshot and error-recovery sections.

Suggestions

Tighten the snapshot paragraph in 'Live views' — the Freeze-snapshot editor workflow could be shortened to the two rules an agent needs: label snapshot rows in prose and keep them in the chart's row grammar.

Compress the 'Unknown props preserve the original directive and data through nearby rich edits...' passage in the error section to the actionable core (never author bm-problem recovery nodes; check names and props against the reference), moving editor-repair mechanics detail to the reference file.

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious Comark rules (directive syntax, query grammar, error codes) and never explains basics Claude already knows, but a few passages could be tightened — notably the snapshot-body paragraph and the "Unknown props preserve the original directive... / reviewed agent replacement and undo" prose — placing it between the 4 and 5 anchors.

4 / 5

Actionability

Guidance is fully executable: copy-paste-ready component examples, an exact query pipeline grammar ("notes | where type == decision and status == open | count"), a concrete validation tool call (bm_read(identifier="<note>", view="text", project="<project>")), and a per-code error table with specific fixes.

5 / 5

Workflow Clarity

Sections form a clear sequence (pick a component → write → validate live views → edit → handle errors) with an explicit validation checkpoint ("Read it back after writing a live view and confirm the view has rows before you state a number in prose"), feedback loops (Component problems listed in bm_write/bm_edit results to fix right away with bm_edit), and a closing five-point checklist.

5 / 5

Progressive Disclosure

The body inlines only the 12 most common components and clearly signals the verified, one-level-deep reference — "The full vocabulary, every prop, and every data grammar are in [references/components.md](references/components.md). Read it before using a component you have not used before" — with the 740-line bundle file confirmed present and containing no nested document references.

5 / 5

Total

19

/

20

Passed

Description

87%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: it states a concrete capability, scopes it to a distinct niche, and includes an explicit 'Use when' clause with two natural trigger conditions. The only gap is moderate synonym coverage and a single-verb action list, which keeps specificity and trigger quality at 4.

DimensionReasoningScore

Specificity

The description names several concrete render targets — "render as charts, tables, boards, and live views with `::bm-*` Comark components" — but offers a single action verb ("Write") with multiple objects, which falls short of the 5 anchor's multiple distinct concrete actions while exceeding the 1-2 actions of the 3 anchor.

4 / 5

Completeness

It explicitly answers both what ("Write Basic Memory notes that render as charts, tables, boards, and live views with `::bm-*` Comark components") and when ("Use when a note reads better as a figure or board, or already has `::bm-*` directives") with concrete trigger phrases, exactly matching the 5 anchor; third-person voice is maintained throughout.

5 / 5

Trigger Term Quality

Natural phrases are present ("charts, tables, boards", "reads better as a figure or board", "`::bm-*` directives") and users would plausibly say them, but a few common synonyms like "diagram", "kanban", or "dashboard" are missing, matching "good keyword coverage; a few natural terms missing" rather than comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Basic Memory notes", "Comark", and "`::bm-*`" define a clear niche with distinct triggers, and the when-clause is scoped to note-authoring contexts, giving minimal conflict risk with generic charting or markdown skills.

5 / 5

Total

18

/

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