onboard
Set up MemMesh for a new project — verify the MCP server is wired, pick local vs hosted, import any existing project knowledge (MEMORY.md, CLAUDE.md, a mem0 export), and seed initial scopes. Use on first run in a repo, when the API key changes, or to re-run setup after config changes.
소스 정보
- 저장소
- ThinkfleetAI/memmesh
- 최근 소스 활동
- 2026년 7월 13일 02:13
- 감지된 SKILL.md 언어
- 영어
- 스타
- 405
- 포크
- 429
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- onboard
- description
- Set up MemMesh for a new project — verify the MCP server is wired, pick local vs hosted, import any existing project knowledge (MEMORY.md, CLAUDE.md, a mem0 export), and seed initial scopes. Use on first run in a repo, when the API key changes, or to re-run setup after config changes.
# onboard
Get a project ready to use MemMesh.
## 1. Verify wiring
```bash
memmesh doctor # binary + MCP config + skill presence
```
If the MCP server isn't connected, run `npx @thinkfleet/memmesh install` (see the
`memmesh-cli` skill), then re-check.
## 2. Local or hosted?
- **Local** (default): SQLite, no key, offline. Good for dev tools.
- **Hosted**: set `MEMMESH_API_KEY` / `sync.url` in
`~/.thinkfleet-memory/config.toml`. Needed for cross-device sync, the full SDK,
and server-side prediction/verticals.
## 3. Seed existing knowledge
If the repo already has durable context, import it (see the `import` skill):
`MEMORY.md`, `CLAUDE.md`, an ADR folder, or a **mem0 export** (then consider
`memmesh-migrate` for a full switch). Feed each item via `memory_observe` so the
engine extracts + builds the graph, scoped `project`.
## 4. Confirm
Run `stats` to show what's now in scope, and remind the user of the two-rule
loop: the agent will **observe** their messages and **recall** at session start
automatically (the always-on `memmesh` skill). Nothing else to configure.
GitHub에서 보기