mem0-oss-to-platform
mem0ai/mem0Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local `Memory` class) to the mem0 Platform / hosted / managed…
Scores out of 100 · grade A
2026-08-22Works
40% of the score100/100
- Loads cleanly: valid frontmatter, required fields present, no dangling references.
Maintained
25% of the score100/100
- no commits in the last 12 weeks
Adopted
20% of the score66/100
- 63,786 stars on the source repo.
Documented
15% of the score64/100
- No usage example or code block.
- 1,025-word body.
- Ships 5 bundled files.
Install
npx skills add mem0ai/mem0/mem0-oss-to-platformWhat it says it does
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local `Memory` class) to the mem0 Platform / hosted / managed SDK (the `MemoryClient` class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g. "migrate my mem0 setup to the platform", "switch from self-hosted mem0 to MemoryClient", "use my mem0 API key instead of a local Qdrant", "move mem0 to the cloud/hosted/managed service", or "replace my local mem0 vector store + embedder config with the platform". Applies to Python (`from mem0 import Memory` → `from mem0 import MemoryClient`) and TypeScript/JavaScript (`import { Memory } from "mem0ai/oss"` → `import MemoryClient from "mem0ai"`). Trigger even when the user doesn't say the word "migrate" but clearly wants their existing mem0 integration to run against the hosted platform. It first produces a reviewable migration plan, then executes it after the developer approves. Strictly scoped to the mem0 integration — it does not refactor, restructure, or "improve" any unrelated code.
Also in mem0ai/mem0
| Artifact | Score | What the check found | Type | Reach | Last commit |
|---|---|---|---|---|---|
| mem0-vercel-ai-sdkmem0ai/mem0 | clean | Skill | 64k stars | today | |
| mem0mem0ai/mem0 | clean | Skill | 1,905 installs | today | |
| mem0-climem0ai/mem0 | clean | Skill | 64k stars | today | |
| dreammem0ai/mem0 | clean | Skill | 64k stars | today | |
| onboardmem0ai/mem0 | clean | Skill | 64k stars | today | |
| memory-triagemem0ai/mem0 | clean | Skill | 64k stars | today |
Other language-specific skills
Browse all| Artifact | Score | What the check found | Category | Reach | Last commit |
|---|---|---|---|---|---|
| turborepovercel/turborepo | clean | Language-specific | 64,154 installs | today | |
| programmingcode-yeongyu/oh-my-openagent | No license | Language-specific | 68k stars | today | |
| cadearthtojake/text-to-cad | clean | Language-specific | 8,940 installs | today | |
| dxfearthtojake/text-to-cad | clean | Language-specific | 4,838 installs | today | |
| modern-pythontrailofbits/skills | clean | Language-specific | 6,975 installs | today | |
| printing-press-polishmvanhorn/cli-printing-press | clean | Language-specific | 5,602 installs | today |
Put this measurement in your README
A badge carrying how many listings this index holds from the repository and how many pass every static structural check. It reads from this index every time somebody loads your page, so it changes when the measurement changes and there is nothing to keep up to date. Free, no account, and the value is not something you or we can set by hand.
[](https://skillworks.kynth.studio/?q=mem0ai%2Fmem0)Would rather not hotlink us? Every badge is also served in shields.io’s endpoint schema, so shields renders the image and your readers never talk to our domain:
Published by Toolproof, the masthead over this index and eight others. The method behind the number is at toolproof.kynth.studio/methodology, and the whole thing is readable as JSON with no key at /api.
