stats

Displays memory usage statistics for sessions and projects with category counts and API latency.

1|Updated Jan 13, 2022
One-click install
npx skills add https://github.com/jayho-k/TIL --skill stats-jayho-k
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stats
Source: https://github.com/jayho-k/TIL/tree/main/AI/mem0/code/mem0_code_analize/mem0/integrations/mem0-plugin/skills/stats
Command: npx skills add https://github.com/jayho-k/TIL --skill stats-jayho-k

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? It gives developers visibility into how many memories their mem0 instance has stored, how they are distributed across categories, and how the memory API is performing, without manual querying. ## Core Features & Use Cases - Session and lifetime stats: Reports memories written and searches performed in the current session alongside total project memory counts. - Category and age breakdown: Groups memories by platform-assigned category and computes age distribution buckets from creation dates. - Weekly digest mode: With the --weekly flag, generates a seven-day activity summary, writes it to ~/.mem0/weekly-digest.md, and appends a history log entry. - Use Case: After a week of coding with mem0 memory capture enabled, run the stats command to see which decision and convention memories accumulated and measure API round-trip latency. ## Quick Start Ask the assistant to show mem0 memory statistics for the current project, optionally with the weekly digest.

Frequently Asked Questions about stats

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

FAQPage Schema
How do I check how many memories mem0 has stored for my project?

Invoke the stats skill, which calls get_memories filtered by your user_id and app_id, then groups results by category and displays a count table. It also shows session-level writes and searches from the local stats file.

How do I generate a weekly memory activity digest in mem0?

Run the stats command with the --weekly flag. It queries memories created in the last seven days, groups them by category, summarizes highlights, writes the digest to ~/.mem0/weekly-digest.md, and appends a line to digest-history.log.

Why does the stats skill not query the API for session stats?

Session stats come from a local stats file because memories are stored without run_id and metadata filters on session_id return inconsistent results. The local file tracks adds and searches for the current session accurately.

How is API latency measured in the mem0 stats output?

Latency is measured by timing a search_memories MCP call with a simple query and top_k of 1. The time before and after the call gives the round-trip latency shown in the dashboard.

What happens if there are no new memories in the weekly digest?

If no memories were created in the past seven days, the digest shows an empty-state message with the total memory count for the project instead of a category table.