/list-projects
Lists all projects with stored memories for the current user, showing memory counts and last activity dates. Use when checking which projects have memories, comparing memory distribution across repos, or finding a specific project scope.
$ npx -y skills add mem0ai/mem0 --skill list-projects --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/list-projects
Context preview
The summary Claude sees to decide when to auto-load this skill.
Lists all projects with stored memories for the current user, showing memory counts and last activity dates. Use when checking which projects have memories, comparing memory distribution across repos, or finding a specific project scope.
SKILL.md
list-projects.SKILL.mdname: list-projects
description: Lists all projects with stored memories for the current user, showing memory counts and last activity dates. Use when checking which projects have memories, comparing memory distribution across repos, or finding a specific project scope.
Mem0 List Projects
Show all known project scopes for the current user.
Execution
Step 1: Fetch memories to discover app_ids
There is no dedicated "list projects" API endpoint. Discover projects by fetching the user's memories across all scopes.
**Important:** A filter with only `user_id` triggers implicit null scoping — it excludes memories that have a non-null `app_id`. Run two queries and merge:
1. **Null-scoped:** `get_memories` with `filters={"AND": [{"user_id": "<active_user_id>"}]}`, `page_size=200` — catches memories without `app_id` 2. **App-scoped:** `get_memories` with `filters={"AND": [{"user_id": "<active_user_id>"}, {"app_id": {"exists": true}}]}`, `page_size=200` — catches memories with any `app_id`
Run both calls in parallel. Merge results, deduplicate by memory `id`.
If either response indicates more pages, paginate (up to 1000 total).
Step 2: Extract distinct projects
For each memory, determine project by: 1. Top-level `app_id` field (preferred) 2. `metadata.project_id` (legacy memories) 3. `metadata.project` (oldest format) 4. `"(unscoped)"` if none found
Group by resolved project name. For each project, count:
- Total memories
- Most recent `created_at` date
- Top 3 `metadata.type` values by frequency
Step 3: Display
## mem0 projects
<app_id_1> <count> memories (last: <date>) ← current
<app_id_2> <count> memories (last: <date>)
<N> projects, <M> total memories
Mark current project with `← current`. Sort by memory count descending.
Step 4: Empty state
If zero memories found:
No projects found. Run /mem0:onboard to get started.
Read more
name: list-projects description: Lists all projects with stored memories for the current user, showing memory counts and last activity dates. Use when checking which projects have memories, comparing memory distribution across repos, or finding a specific project scope.
Mem0 List Projects
Show all known project scopes for the current user.
Execution
Step 1: Fetch memories to discover app_ids
There is no dedicated "list projects" API endpoint. Discover projects by fetching the user's memories across all scopes.
**Important:** A filter with only `user_id` triggers implicit null scoping — it excludes memories that have a non-null `app_id`. Run two queries and merge:
1. **Null-scoped:** `get_memories` with `filters={"AND": [{"user_id": "<active_user_id>"}]}`, `page_size=200` — catches memories without `app_id` 2. **App-scoped:** `get_memories` with `filters={"AND": [{"user_id": "<active_user_id>"}, {"app_id": {"exists": true}}]}`, `page_size=200` — catches memories with any `app_id`
Run both calls in parallel. Merge results, deduplicate by memory `id`.
If either response indicates more pages, paginate (up to 1000 total).
Step 2: Extract distinct projects
For each memory, determine project by: 1. Top-level `app_id` field (preferred) 2. `metadata.project_id` (legacy memories) 3. `metadata.project` (oldest format) 4. `"(unscoped)"` if none found
Group by resolved project name. For each project, count:
- Total memories
- Most recent `created_at` date
- Top 3 `metadata.type` values by frequency
Step 3: Display
## mem0 projects <app_id_1> <count> memories (last: <date>) ← current <app_id_2> <count> memories (last: <date>) <N> projects, <M> total memories
Mark current project with `← current`. Sort by memory count descending.
Step 4: Empty state
If zero memories found:
No projects found. Run /mem0:onboard to get started.
Mem0 ("mem-zero") enhances AI assistants and agents with an intelligent memory layer, enabling personalized AI interactions.
Repo: mem0ai/mem0
Other skills on mem0.
- /context-loader
Searches and injects relevant memories into context before starting work on a task. Use when beginning a new task, switching context, or when project history, past decisions, or coding conventions need to be loaded.
Open skill - /dream
Consolidates stored memories by merging duplicates, resolving contradictions, and pruning stale entries. Use when memory count is high, search results feel noisy or repetitive, or periodic cleanup is needed to maintain memory quality.
Open skill - /export
Exports all project memories to a portable Markdown file for backup or migration. Use when backing up memories, migrating to another project, sharing memory state with teammates, or archiving before cleanup.
Open skill - /forget
Deletes memories by search query or memory ID with confirmation before removal. Use when removing outdated decisions, incorrect memories, sensitive data, or cleaning up after experiments. Also handles undo of recent additions.
Open skill - /health
Diagnoses mem0 connectivity, API key validity, and memory read/write functionality. Use when memory operations fail, searches return empty, add_memory errors occur, MCP connection drops, or to verify the plugin is working correctly.
Open skill - /import
Imports memories from an exported Markdown file or MEMORY.md into the current project. Use when migrating from another project, restoring from backup, importing Claude Code native MEMORY.md content, or setting up a new project with existing knowledge.
Open skill

