Agenticx Memory Architect
DemonDamon/AgenticX
Guide for setting up and using the AgenticX memory system including Mem0 integration, long-term memory, context management, and memory-enhanced agents.
Reports whether Mem0 memory is working in a repository, covering capture state, scope, API key, event counts and doctor checks, and flags an invalid key plainly.
Install Mem0 Status
$ npx skills add mem0ai/mem0 --skill status -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mem0ai/mem0 status --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mem0ai/mem0.git skills-src && mkdir -p .claude/skills && cp -r skills-src/integrations/kimi-plugin/skills/status .claude/skills/status && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "status" agent skill from https://github.com/mem0ai/mem0/tree/main/integrations/kimi-plugin/skills/status into .claude/skills/status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mem0ai/mem0/tree/main/integrations/kimi-plugin/skills/statusType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mem0ai/mem0 --skill status -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mem0ai/mem0 status --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mem0ai/mem0.git skills-src && mkdir -p .agents/skills && cp -r skills-src/integrations/kimi-plugin/skills/status .agents/skills/status && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "status" agent skill from https://github.com/mem0ai/mem0/tree/main/integrations/kimi-plugin/skills/status into .agents/skills/status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mem0ai/mem0 --skill status -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mem0ai/mem0 status --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mem0ai/mem0.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/integrations/kimi-plugin/skills/status .cursor/skills/status && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "status" agent skill from https://github.com/mem0ai/mem0/tree/main/integrations/kimi-plugin/skills/status into .cursor/skills/status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mem0ai/mem0.git --path integrations/kimi-plugin/skills/status--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mem0ai/mem0 --skill status -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mem0ai/mem0 status --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mem0ai/mem0.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/integrations/kimi-plugin/skills/status .gemini/skills/status && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "status" agent skill from https://github.com/mem0ai/mem0/tree/main/integrations/kimi-plugin/skills/status into .gemini/skills/status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mem0ai/mem0 statusInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mem0ai/mem0 --skill status -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mem0ai/mem0.git skills-src && mkdir -p .github/skills && cp -r skills-src/integrations/kimi-plugin/skills/status .github/skills/status && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "status" agent skill from https://github.com/mem0ai/mem0/tree/main/integrations/kimi-plugin/skills/status into .github/skills/status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mem0ai/mem0 --skill status -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mem0ai/mem0 status --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mem0ai/mem0.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/integrations/kimi-plugin/skills/status .opencode/skills/status && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "status" agent skill from https://github.com/mem0ai/mem0/tree/main/integrations/kimi-plugin/skills/status into .opencode/skills/status/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "status", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
status- GitHub stars
- 67k
- Token cost
- ~288 tokens
- SKILL.md length
- 103 words
- Files
- 1
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Reports whether Mem0 memory is working in a repository, covering capture state, scope, API key, event counts and doctor checks, and flags an invalid key plainly.
- Checking whether Mem0 memory capture is on for a repository
- Calls python3
- Working out why an expected memory is missing
- Diagnosing a suspected invalid or expired Mem0 API key
What it does
The agent runs two commands from the plugin's memory_cli.py, status with JSON output and doctor, and reports the combined result in plain language. It summarizes only fields the JSON really contains: whether capture is active or paused, the user ID and repository scope, whether an API key is configured, the event, flush and retrieval counts, and the doctor check results. The flushes figure is the number of completed flushes, not a pending count.
If doctor reports an authentication failure, such as a 401 or invalid key, the agent says clearly that the Mem0 API key is invalid or expired and that memories are not being created. It never presents an authentication failure as no memories found, and it suggests reinstalling the plugin with the api_key config option.
When your agent uses it
- Checking whether Mem0 memory capture is on for a repository
- Working out why an expected memory is missing
- Diagnosing a suspected invalid or expired Mem0 API key
- Reading flush and retrieval counts for the current repository
Example prompts
- “Check whether Mem0 memory is active in this repository.”
- “A memory I expected is missing, so run the status check and tell me why.”
- “Run the Mem0 doctor and say whether my API key is still valid.”
Requirements
- The Mem0 plugin for Kimi and Python 3
- A Mem0 API key
What it can do on your machine
Read from SKILL.md and the folder at commit c93420c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Mem0 Status loads about 288 tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 103 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mem0ai/mem0 at commit c93420c, republished under its Apache-2.0 licence (© mem0ai). 103 words, ~288 tokens.
Download SKILL.mdSave it as
.claude/skills/status/SKILL.md (or your agent's skills folder).- name
- status
- description
- Show whether Mem0 memory is working in this repository, covering configuration, capture state, pending flushes, and whether the Mem0 API key is valid. Use when the user asks whether memory is on, why a memory is missing, or anything looks broken.
- disable-model-invocation
- false
Memory status
Run both commands and report the combined result in plain language:
python3 "${KIMI_PLUGIN_ROOT}/core/memory_cli.py" --harness "kimi" status --json
python3 "${KIMI_PLUGIN_ROOT}/core/memory_cli.py" --harness "kimi" doctorSummarize, using only fields the JSON actually reports: whether capture is
active or paused, the user ID and repository scope (repo_id), whether an
API key is configured, the event/flush/retrieval counts (flushes is the
number of completed flushes, not a pending count), and the doctor check
results. If doctor reports an authentication failure (401 / invalid key), say
clearly that the Mem0 API key is invalid or expired and that memories are NOT
being created. Never report an auth failure as "no memories found". Suggest
reinstalling with --config api_key=... in that case.
© mem0ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in integrations/kimi-plugin/skills/status of mem0ai/mem0.
Open the folder on GitHubat commit c93420c
Compare with similar skills
Mem0 Status next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Mem0 Status this skillmem0ai/mem0 | 67k | — | ~288 | Automated safety check: Pass | Apache-2.0 | |
| Agenticx Memory ArchitectDemonDamon/AgenticX | 279 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Hyperspacedb MemoryYARlabs/hyperspace-db | 160 | — | ~880 | Automated safety check: Pass | MIT | |
| Self Improving Systemsooiyeefei/ccc | 494 | — | ~5.2k | Automated safety check: Pass | MIT | |
| Mem0Anil-matcha/awesome-muse-connectors | 1.3k | — | ~867 | Automated safety check: Pass | MIT | |
| Mem0majiayu000/claude-skill-registry | 666 | 1 repos | ~1.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Hyperspacedb Memory
YARlabs/hyperspace-db
Zero-overhead cognitive long-term and episodic memory for AI agents (Mem0 drop-in and mcp-hyperspace-memory).
Self Improving Systems
ooiyeefei/ccc
Decide whether your agent actually needs persistent memory, feedback loops, or closed-loop learning, then design the smallest thing that pays for itself.
Mem0
Anil-matcha/awesome-muse-connectors
Mem0 memory CLI: add memories from messages, semantic search, read or delete memories, poll async events.
Mem0
majiayu000/claude-skill-registry
Adds persistent, personalized long-term memory to LLM apps and agents with Mem0, the open-source memory layer: it extracts facts from conversations, stores them in a vector database and retrieves…
Mem0 Bridge
momori777/Artemis
Mem0 memory bridge for AI Girlfriend — search/read/write long-term memories from Qdrant vector DB.
More from mem0ai/mem0
All 25 skills in this repoMem0 Platform SDK
mem0ai/mem0
Adds persistent memory to AI apps with the Mem0 Python and TypeScript SDKs: store, search, update and delete user memories, with framework integrations.
Mem0 CLI Memory Commands
mem0ai/mem0
Adds, searches, lists, updates and deletes memories on the Mem0 platform from the terminal with the mem0 command, including a JSON mode built for agents.
Mem0 Provider for Vercel AI SDK
mem0ai/mem0
Adds persistent memory to Vercel AI SDK apps with the Mem0 provider, using a wrapped model or standalone retrieve and store utilities.
Mem0 Memory Deletion
mem0ai/mem0
Finds and deletes specific mem0 memories by search query or ID, always asking for confirmation first, and can undo the most recent memories added this session.
Mem0 Remember Command
mem0ai/mem0
Saves a fact, decision or preference the user states into mem0 as written, labeled with a memory type such as decision, convention or user_preference.
Mem0 Memory Scope
mem0ai/mem0
Shows or changes the default Mem0 memory scope, project, session or global, which decides where memories are saved and searched.
Related
Categories
Questions about Mem0 Status
What does Mem0 Status do?
Reports whether Mem0 memory is working in a repository, covering capture state, scope, API key, event counts and doctor checks, and flags an invalid key plainly. py, status with JSON output and doctor, and reports the combined result in plain language. It summarizes only fields the JSON really contains: whether capture is active or paused, the user ID and repository scope, whether an API key is configured, the event, flush and retrieval counts, and the doctor check results.
When should I use Mem0 Status?
Mem0 Status fits situations like: checking whether Mem0 memory capture is on for a repository; working out why an expected memory is missing; diagnosing a suspected invalid or expired Mem0 API key; reading flush and retrieval counts for the current repository.
How do I install Mem0 Status in Claude Code?
Run `npx skills add mem0ai/mem0 --skill status -a claude-code`. Or copy the skill folder (integrations/kimi-plugin/skills/status in mem0ai/mem0) into .claude/skills/status in your project. Claude Code loads it when a task matches its description.
How do I install Mem0 Status in Codex?
Run `npx skills add mem0ai/mem0 --skill status -a codex`. Or copy the skill folder (integrations/kimi-plugin/skills/status in mem0ai/mem0) into .agents/skills/status in your project. Codex loads it when a task matches its description.
Can I use Mem0 Status in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mem0ai/mem0 --skill status -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/status, .gemini/skills/status, .github/skills/status and .opencode/skills/status in your project.
What does Mem0 Status need to run?
Going by SKILL.md and its folder, Mem0 Status needs the command-line tools its instructions call (python3). Our summary lists: The Mem0 plugin for Kimi and Python 3; A Mem0 API key.
Does Mem0 Status access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Mem0 Status safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Mem0 Status use?
Mem0 Status is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Mem0 Status use?
About 288 tokens (SKILL.md is roughly 1.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Mem0 Status?
Skills that share tags, products or a category with Mem0 Status: Agenticx Memory Architect (DemonDamon/AgenticX, 279 stars), Hyperspacedb Memory (YARlabs/hyperspace-db, 160 stars), Self Improving Systems (ooiyeefei/ccc, 494 stars) and Mem0 (Anil-matcha/awesome-muse-connectors, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mem0 Status?
mem0ai (a GitHub organization) maintains it in mem0ai/mem0, which has 66,715 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 6, 2026.
Source: mem0ai/mem0 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.