CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory-research

Research an external subject on the web and synthesize it into a structured Basic Memory note. Use when asked to research a company, person, technology, or topic, or given a bare name or URL.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 strong, highly actionable workflow: concrete bm_* tool calls, a dedup check, an approval gate, and a similar-notes feedback loop, all in a clearly sequenced six-step structure. The main cost is token weight — the three entity templates are largely redundant with each other and could be collapsed into one adaptable template or moved to a references file.

Suggestions

Collapse the Organization, Person, and Technology bm_write templates into one annotated template plus a short per-type table of directory/note_type/tags values, cutting roughly 60-80 lines of near-duplicate content.

State the approval requirement once (in Step 4 or the Guidelines) instead of three times across the intro, Step 4, and Guidelines.

Clarify the '(see **memory-notes**)' pointer — name the actual skill/path it refers to so the as-of-date convention it cites can be followed.

DimensionReasoningScore

Conciseness

The body is mostly efficient — no explanations of concepts Claude already knows, and guidance like the hedging rules is genuinely additive — but the three near-duplicate bm_write templates (Organization, Person, Technology) repeat the same structure (Overview / Background / Observations / Relations) at full length, and approval is stated three times (intro, Step 4, Guidelines). This matches anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') rather than 4, since the template repetition alone is a substantial trim.

3 / 5

Actionability

Fully executable guidance throughout: concrete bm_search calls with example queries and name-variation advice, a copy-paste markdown summary template, an explicit approval prompt, three parameter-complete bm_write invocations, and a concrete bm_edit insert_after_section example. Specific examples cover the common entity cases, matching anchor 5; the remaining placeholders ("<project>", [subject]) are inherent to a template skill, not gaps.

5 / 5

Workflow Clarity

Six clearly sequenced steps with explicit checkpoints: check Basic Memory for existing entities before creating (Step 2), an approval gate before writing (Step 4), and a feedback loop for error recovery in Step 5 ('If bm_write reports similar existing notes, check whether one of them is this entity... merge or link instead of duplicating'). This matches anchor 5's 'clear sequence with explicit validation steps; feedback loops for error recovery'; the operations are additive rather than destructive/batch, so the cap of 3 does not apply.

5 / 5

Progressive Disclosure

No bundle files exist and the skill is a single, well-sectioned file with clear headers (Project scope, Workflow steps, Guidelines) and no nested references, matching anchor 4 ('good structure; most content is appropriately placed; minor organization gaps'). It is not a 5 because the ~245-line body inlines three full entity templates that could live in a references/ file, and the parenthetical '(see **memory-notes**)' reference is not clearly signaled as an external skill or path.

4 / 5

Total

17

/

20

Passed

Description

78%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 well-constructed description with an explicit 'Use when...' clause covering multiple entity types and a URL trigger, tied clearly to the Basic Memory niche. Its only weakness is that the 'what' half lists just two actions (research, synthesize), leaving the fuller capability set (dedup checks, updates, context capture) implicit.

Suggestions

Add one or two more concrete actions to the 'what' half, e.g. '...synthesize it into a structured Basic Memory note, checking for existing entities first and updating rather than duplicating.'

Add a natural synonym trigger such as 'look up' or 'find background on' alongside 'research' to broaden the natural-phrases users would say.

DimensionReasoningScore

Specificity

The description names the domain (Basic Memory) and two concrete actions — "Research an external subject on the web and synthesize it into a structured Basic Memory note" — but stops at research + synthesize without listing further capabilities (e.g., checking for existing entities, updating notes, capturing user context). It matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') rather than 4, which expects several specific actions.

3 / 5

Completeness

It explicitly answers both questions: what ("Research an external subject on the web and synthesize it into a structured Basic Memory note") and when ("Use when asked to research a company, person, technology, or topic, or given a bare name or URL") with concrete trigger phrases, exactly matching the anchor-5 example pattern. Not below 5 since neither half is vague or implied.

5 / 5

Trigger Term Quality

"Use when asked to research a company, person, technology, or topic, or given a bare name or URL" gives good natural keyword coverage across entity types plus the URL trigger, matching anchor 4 ('good keyword coverage; a few natural terms missing'). It falls short of anchor 5 because common synonyms like "look up", "find information about", or "background on" are absent.

4 / 5

Distinctiveness Conflict Risk

The "structured Basic Memory note" anchor gives it a clear niche distinct from generic research or note skills, matching anchor 4 ('mostly distinct; minor overlap risk'). It is not a 5 because the broad trigger phrase "asked to research a company, person, technology, or topic" could also fire on general research requests where no memory note is wanted.

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