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.
74%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/memory-ingest/SKILL.mdTurn raw, unstructured input into structured Basic Memory entities. Meeting transcripts, conversation logs, pasted documents, email threads — anything with information worth preserving gets parsed, cross-referenced against existing knowledge, and written as proper notes.
If the project is unknown, discover it with bm_project_list().
Pass a nonempty project on every note, folder, context and schema call, even
with one project or a qualified memory:// URL. Use the chosen project's name,
workspace/project, or external ID; <project> below is a placeholder for it.
Recent activity also requires project. Search accepts project for one
project, projects for selected projects, or all_projects=True explicitly.
Discovery and bundled manuals need no project. Keep the same scope when following
returned paths, paginating, or recovering from a refusal.
1. Parse raw input → identify structure, extract key info
2. Extract entities → people, orgs, topics, action items
3. Search existing entities → multi-variation queries
4. Research new entities → optional web research (see memory-research)
5. Present entity proposal → get approval before creating
6. Create source note → verbatim content + observations + relations
7. Create approved entities → structured notes for each new entity
8. Extract action items → follow-ups and commitmentsRead the pasted content and identify its structure:
Don't rewrite or summarize the source content. Preserve it verbatim in the note — you'll add structured observations alongside it.
Give dated observations a qualifier with the date the source gives (see memory-notes):
@occurred: for what happened in the meeting, @due: for action items.
A file instead of pasted text. For a PDF, Word, PowerPoint, or CSV file in the project,
and if the bm CLI is available, run bm import document <path>. It writes an
extracted-text sidecar (<file>.<ext>.md) linked to the source by derived_from. Write
your structured note separately and link it to the sidecar; don't edit the sidecar.
Scan the content for entities worth tracking in the knowledge graph:
| Entity Type | Signals |
|---|---|
| Person | Names with roles, titles, or affiliations mentioned |
| Organization | Company names, agencies, institutions |
| Topic/Concept | Technical domains, methodologies, standards discussed substantively |
| Action Item | Commitments, deadlines, "I'll do X by Y" statements |
Infer type from context. If someone is introduced as "CTO of Acme Corp", that's both a Person and an Organization entity. If a technology is discussed in depth, it might warrant a Concept entity.
Exclude noise. Not every name mentioned is worth an entity. Filter for:
For each extracted entity, search Basic Memory with multiple query variations:
# Person — try full name, last name
bm_search(query="Sarah Chen", project="<project>")
bm_search(query="Chen", project="<project>")
# Organization — try full name, abbreviation, acronym
bm_search(query="National Renewable Energy Laboratory", project="<project>")
bm_search(query="NREL", project="<project>")
# Topic — try the full term and keywords
bm_search(query="edge computing", project="<project>")
bm_search(query="edge inference", project="<project>")Classify each entity as:
[[wiki-link]].For proposed entities where more context would be valuable, do a brief web search (2-3 queries max per entity):
Use hedging language ("appears to be", "estimated", "based on public information"). Never fabricate details.
This step is optional — skip it if the source material provides enough context, or if the user is in a hurry. See the memory-research skill for deeper research workflows.
Before creating anything, present what you found and what you'd like to create:
Entities found in Basic Memory:
- [[Sarah Chen]] (Person — existing)
- [[Acme Corp]] (Organization — existing)
Proposed new entities:
- Jordan Rivera (Person — VP Engineering at NovaTech, mentioned as project lead)
- NovaTech (Organization — SaaS platform, Series B, discussed as integration partner)
- Federated Learning (Concept — core technical topic of the discussion)
Approve all / select individually / skip entity creation?Include enough context with each proposed entity for the user to make a quick decision.
Create the primary note for the ingested content. This is the "record of what happened" — it preserves the raw material and adds structured metadata.
bm_write(
title="NovaTech Meeting - Jordan Rivera - Feb 22, 2026",
directory="meetings/2026",
note_type="meeting",
tags=["meeting", "novatech", "federated-learning"],
metadata={"date": "2026-02-22"},
content="""
# NovaTech Meeting - Jordan Rivera - Feb 22, 2026
Brief one-sentence summary of what this meeting was about.
## Transcript
[Preserve all source content verbatim — do not summarize or rewrite]
## Observations
- [opportunity] NovaTech interested in integration partnership
- [insight] Their platform handles 10K concurrent sessions, relevant to our scale needs
- [next_step] @due:2026-02-27 Send technical spec document
- [sentiment] Strong enthusiasm from their engineering team
- [decision] @occurred:2026-02-22 Agreed to start with a proof-of-concept integration
## Relations
- attended [[Jordan Rivera]]
- with [[NovaTech]]
- discussed [[Federated Learning]]
- follow_up [[Send NovaTech Technical Spec]]
""",
project="<project>",
)bm_write(
title="Edge Computing Architecture Whitepaper",
directory="references",
note_type="reference",
tags=["edge-computing", "architecture", "reference"],
metadata={"source": "https://example.com/whitepaper.pdf", "date_ingested": "2026-02-22"},
content="""
# Edge Computing Architecture Whitepaper
## Source Content
[Preserve relevant content — for long documents, include key sections rather than the entire text]
## Observations
- [key_finding] Latency drops 40% with edge inference vs cloud-only
- [technique] Model sharding across heterogeneous edge nodes
- [limitation] Requires minimum 8GB RAM per edge node
## Relations
- relates_to [[Edge Computing]]
- relates_to [[Model Optimization]]
""",
project="<project>",
)Use categories that capture the nature of the information. Common categories for ingested content:
| Category | Use For |
|---|---|
opportunity | Business or collaboration opportunities identified |
decision | Decisions made or agreed upon |
insight | Non-obvious understanding gained |
next_step | Concrete action items or follow-ups |
sentiment | Enthusiasm, concerns, hesitations expressed |
risk | Risks or concerns identified |
requirement | Requirements or constraints discovered |
key_finding | Important facts from reference material |
technique | Methods, approaches, or patterns described |
context | Background information that may be useful later |
Invent categories as needed — these are suggestions, not a fixed list.
For each entity the user approved, create a structured note. Match the entity type to an appropriate template.
If bm_write reports similar existing notes, treat that as a match Step 3 missed. Ask the
user whether to merge the new note into the existing one or link the two, and keep both
notes until they decide.
bm_write(
title="Jordan Rivera",
directory="people",
note_type="person",
tags=["person", "novatech", "engineering"],
content="""
# Jordan Rivera
## Overview
VP of Engineering at NovaTech. Met during integration partnership discussion.
## Background
[Role, expertise, context from meeting + any web research]
## Observations
- [role] VP Engineering at NovaTech
- [expertise] Distributed systems, federated learning
- [met] 2026-02-22 during integration discussion
## Relations
- works_at [[NovaTech]]
- discussed_in [[NovaTech Meeting - Jordan Rivera - Feb 22, 2026]]
""",
project="<project>",
)bm_write(
title="NovaTech",
directory="organizations",
note_type="organization",
tags=["organization", "saas", "integration-partner"],
content="""
# NovaTech
## Overview
SaaS platform company. Series B stage.
[Additional context from meeting + web research]
## Products & Services
[What they offer, if discussed or researched]
## Observations
- [stage] Series B, ~200 employees
- [relevance] Potential integration partner for our platform
- [first_contact] 2026-02-22
## Relations
- employs [[Jordan Rivera]]
- discussed_in [[NovaTech Meeting - Jordan Rivera - Feb 22, 2026]]
""",
project="<project>",
)bm_write(
title="Federated Learning",
directory="concepts",
note_type="concept",
tags=["concept", "machine-learning", "distributed-systems"],
content="""
# Federated Learning
## Overview
[Brief description of the concept from the discussion context]
## Observations
- [definition] Machine learning approach where models train across decentralized data sources
- [relevance] Core technique discussed in NovaTech integration
## Relations
- discussed_in [[NovaTech Meeting - Jordan Rivera - Feb 22, 2026]]
""",
project="<project>",
)Adapt templates to your domain. The key elements are: type and tags as parameters, an overview section, observations with categories, and relations linking back to the source.
Review the source content for commitments and follow-ups:
Action Items:
- Send NovaTech technical spec document by Friday (your commitment)
- Jordan will share their API documentation by next week (their commitment)
Follow-Up Reminders:
- 1 week: Check if Jordan sent API docs
- 2 weeks: Schedule follow-up call to discuss POC scopeIf using the memory-tasks skill, create Task notes for your action items. Otherwise, capture them as observations in the source note.
basicmachines-co/basic-memory
4519c23
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.