remember
Store a memory in MemMesh from the user's input. Prefers memory_observe (the engine decides what to extract) and falls back to memory_save only for verbatim/structured notes. Use when the user says "remember this", "save this", "note that", "from now on", "we decided", or explicitly asks to record a decision, preference, convention, or learning.
소스 정보
- 저장소
- ThinkfleetAI/memmesh
- 최근 소스 활동
- 2026년 7월 13일 02:13
- 감지된 SKILL.md 언어
- 영어
- 스타
- 420
- 포크
- 439
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- remember
- description
- Store a memory in MemMesh from the user's input. Prefers memory_observe (the engine decides what to extract) and falls back to memory_save only for verbatim/structured notes. Use when the user says "remember this", "save this", "note that", "from now on", "we decided", or explicitly asks to record a decision, preference, convention, or learning.
# remember
Persist something the user asked you to keep.
## Default: observe (let the engine extract)
For almost everything, call **`memory_observe`** with the user's raw statement.
The engine runs deterministic extraction and saves what's memorable — you don't
judge.
```jsonc
{ "name": "memory_observe",
"arguments": { "text": "<the user's exact statement>", "role": "user",
"projectId": "<git repo name or null>", "userId": "<OS user>" } }
```
## Verbatim: save (rare)
Only when the user says "save this exactly / verbatim" or you have structured
data the extractor would mangle, use **`memory_save`** with an explicit id,
type, and scope:
```jsonc
{ "name": "memory_save",
"arguments": { "id": "<21+ char id>", "platformId": "local", "type": "preference",
"scope": "user", "content": "prefers pnpm over npm" } }
```
Pick scope: `user` (personal preference/identity), `project` (a repo's rule/
decision/fact), else let the engine default.
## After saving
Briefly confirm what was stored and at which scope, so the user can correct it.
If they're *changing* an existing fact, see the `pin`/correction note: observe
the new statement and let the engine supersede — don't delete.
GitHub에서 보기