CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory-ingest

Turn meeting transcripts, conversation logs, or pasted documents into structured Basic Memory notes: match existing entities, propose new ones with approval, and capture action items.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

63%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 thorough, well-sequenced ingestion workflow with genuinely executable code templates and thoughtful guardrails (approval gates, duplicate recovery, hedging rules). The main costs are token efficiency — a repetitive Guidelines section and redundant near-identical templates — and a monolithic 330-line body whose template material would be better split into a references file.

Suggestions

Trim the Guidelines section to only the bullets that add new guidance ('Infer, don't interrogate', 'Prose and observations together', 'Link everything back') and drop the ones restating Steps 1, 3, 4, and 5.

Move the Person/Organization/Concept templates and the observation-category table to a references/templates.md file, keeping one representative example inline and linking to the rest.

Add a short example of updating an existing entity (the search-before-create pattern the Guidelines require), since 'Update existing entities with new information' is currently instructed but never shown.

DimensionReasoningScore

Conciseness

The body avoids teaching concepts Claude already knows, but the Guidelines section restates roughly sixty percent of step content already stated inline ('Preserve source content verbatim' repeats Step 1, 'Get approval for new entities' repeats Step 5, 'Use hedging' repeats Step 4), and the Person/Organization/Concept templates share most of their structure. This matches anchor 3 — mostly efficient but could be tightened — rather than 2, since there is no padding or fluff, and rather than 4, because the repetition is more than minor.

3 / 5

Actionability

Five complete, executable code blocks (multi-variation bm_search, two bm_write source-note templates, three entity templates) plus a concrete proposal format cover the common cases, and the bm import CLI fallback is given verbatim. It is not a 5 because the Guidelines explicitly instruct 'Update existing entities with new information rather than creating duplicates' yet no command or example for updating is shown — a minor gap in a common case.

4 / 5

Workflow Clarity

The 8-step sequence is clearly numbered with a workflow overview, an approval checkpoint before creation (Step 5), and an explicit error-recovery loop for duplicate detection (Step 7: 'treat that as a match Step 3 missed... keep both notes until they decide'). It falls short of anchor 5 because there is no explicit validation step verifying that created notes and their relations are correct.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers and sibling-skill references are clearly signaled ('see the memory-research skill'), but the skill is ~330 lines with no bundle files: the three full entity templates (~100 lines) and the observation-category table are detailed material inlined in SKILL.md that belongs in a references/ file. This matches anchor 3 — content that should be separate is inline — rather than 2, since structure is present and navigation within the file is easy.

3 / 5

Total

14

/

20

Passed

Description

71%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 with concrete, third-person action statements and a well-defined niche in Basic Memory ingestion. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which both caps completeness and limits natural trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause with concrete triggers, e.g. 'Use when the user pastes a meeting transcript or conversation log, says "process these notes" or "add this to Basic Memory", or asks to extract knowledge from a pasted document or email thread.'

Include a few natural synonyms in the trigger language — 'meeting notes', 'email threads', 'chat logs' — so the description matches the phrasings users actually say.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'match existing entities, propose new ones with approval, and capture action items' — covering the skill's core capabilities comprehensively, matching the density of the anchor-5 example. It is not a 4 because no meaningful capability gap remains in the core workflow.

5 / 5

Completeness

The 'what' is clearly stated (turn inputs into structured notes, match/propose entities, capture action items), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline. The input types ('meeting transcripts, conversation logs, or pasted documents') only weakly imply when to use the skill.

3 / 5

Trigger Term Quality

'meeting transcripts', 'conversation logs', and 'pasted documents' are natural phrases users would say, giving good keyword coverage. It falls short of anchor 5 because common synonyms like 'meeting notes', 'email threads', or 'chat logs' are missing, but exceeds anchor 3 because multiple relevant trigger terms are present rather than a single keyword.

4 / 5

Distinctiveness Conflict Risk

Phrases like 'structured Basic Memory notes', 'match existing entities', and 'propose new ones with approval' carve a clear ingestion niche that generic note-taking skills would not match. It is not a 5 because the skill belongs to a family of memory-related skills (memory-notes, memory-research, memory-tasks referenced in the body), creating minor overlap risk on triggers like 'add this to Basic Memory'.

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