smithery.ai

mem-status

Show memory system status and tracked projects. Use to check memory system health and list projects.

First seen Apr 25, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.4
Allowed toolsmcp__obsidian-mem__mem_project_context, mcp__obsidian-mem__mem_list_projects, Bash

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,302 B
  • docs SUMMARY.md 118 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Memory Status Skill

Display memory system information and tracked projects.

When to Use

  • See if the memory system is working
  • List all tracked projects
  • Get context for a specific project

Usage

/mem-status
/mem-status projects

Workflow

  1. List Projects

Use memlistprojects tool

  1. Get Project Context

If a project is specified, use memprojectcontext

  1. Check Config

``bash cat ~/.cc-obsidian-mem/config.json ``

Output Format

## Memory System Status

### Projects in Memory
1. project-a (last active: 1 day ago)
2. project-b (last active: 3 days ago)
3. my-project (current)

### Quick Stats
- Total Notes: 156
- Errors Documented: 23
- Decisions Recorded: 15
- Knowledge Items: 45

Troubleshooting

If no data is being captured:

  1. Verify hooks are installed: check /plugin list
  2. Check config: cat ~/.cc-obsidian-mem/config.json
  3. Ensure vault path is correct and writable
  4. Check background log: cat /tmp/cc-obsidian-mem-background.log