list-projects

Lists mem0 projects with memory counts and last activity dates for the current user.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/nhatnguyen1122/Agent-Memory-Eval --skill list-projects-nhatnguyen1122
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: list-projects
Source: https://github.com/nhatnguyen1122/Agent-Memory-Eval/tree/main/mem0/integrations/mem0-plugin/skills/list-projects
Command: npx skills add https://github.com/nhatnguyen1122/Agent-Memory-Eval --skill list-projects-nhatnguyen1122

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When using mem0 across multiple repositories, it is hard to know which projects have stored memories, how many memories each project holds, and when each was last active. This Skill discovers all project scopes for the current user and summarizes memory distribution. ## Core Features & Use Cases - Project Discovery: Fetches both null-scoped and app-scoped memories in parallel, then merges and deduplicates results to find every project. - Per-Project Statistics: Groups memories by resolved project name and reports total counts, most recent activity date, and top memory types. - Use Case: Before cleaning up old data, run this Skill to see that your "api-service" repo has 42 memories while "docs-site" has only 3, so you know where to focus. ## Quick Start Ask the assistant to list all my mem0 projects with their memory counts and last activity dates.

Frequently Asked Questions about list-projects

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list all mem0 projects with stored memories?

Fetch memories with get_memories using two queries: one filtered by user_id only for null-scoped memories, and one adding an app_id exists filter for app-scoped memories. Merge the results, deduplicate by memory id, and group by project.

Why does filtering mem0 memories by user_id miss some projects?

A filter with only user_id triggers implicit null scoping, which excludes memories that have a non-null app_id. You must run a second query with an app_id exists filter and merge both result sets.

How are mem0 project names resolved from memories?

The project is resolved first from the top-level app_id field, then from metadata.project_id for legacy memories, then metadata.project for the oldest format. Memories with none of these are grouped as unscoped.

What happens if no mem0 memories exist for a user?

The Skill displays an empty state message telling the user no projects were found and suggesting they run the mem0 onboarding command to get started.

Is there a dedicated mem0 API endpoint to list projects?

No, there is no dedicated list-projects endpoint. Projects are discovered by fetching the user's memories across all scopes with pagination up to 1000 memories and extracting distinct app_id values.