Skip to content
Skills Library
AI & agents · Review & audit

memory-status

/memory-status

Display Engram memory system status — configuration, file sizes, entry counts, and health check. Trigger when the user asks about memory state, what's been remembered, or for diagnostics.

Licence
MIT
Last repository change
26.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
2
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Display Engram memory system status — configuration, file sizes, entry counts, and health check. Trigger when the user asks about memory state, what's been remembered, or for diagnostics.

Original author description

Display Engram memory system status — configuration, file sizes, entry counts, and health check. Trigger when the user asks about memory state, what's been remembered, or for diagnostics.

How it works

  1. When to Use
  2. Workflow
Original SKILL.md headings · 97 lines, 336 words
SKILL.md preview
---
name: memory-status
description: Display Engram memory system status — configuration, file sizes, entry counts, and health check. Trigger when the user asks about memory state, what's been remembered, or for diagnostics.
---

# Memory Status

Display the current state of the Engram memory system.

## When to Use

Use when:
- The user asks about the memory system status
- The user wants to know what's been remembered
- Diagnostics are needed (missing files, empty preferences, etc.)
- The user asks "what do you know about me?"

## Workflow

### 1. Read Configuration

Read `.claude/memory-settings.json` for:
- Preset type
- File names
- Language
- Search mode

If the file is missing, tell the user to run `memory-init` first.

### 2. Inspect Memory Files

For each of the three memory files, gather:
- File exists? (yes/no)
- File size (approximate line count)
- Last modified date (via `stat` or `ls -l`)
- Number of entries:
  - Preferences: count of filled (non-empty) fields
  - Conversations: count of `### YYYY-MM-DD` entries
  - Long-term: count of `- YYYY-MM-DD:` entries

### 3. Check CLAUDE.md Integration

Verify that `CLAUDE.md` contains `<!-- ENGRAM:START -->` / `<!-- ENGRAM:END -->` markers and an `@{PREFS_FILE}` reference. This is what auto-loads preferences each session.

### 4. Display Status Report

Format:

```
Engram Memory System Status
═══════════════════════════

Configuration:
  Preset:      <preset>
  Language:    <language>
  Search mode: <strong|weak>

Memory Files:
  <preferences-file>
    Status:   <exists/missing>
    Size:     <lines> lines
    Modified: <date>
    Fields:   <filled>/<total> filled

  <conversations-file>
    Status:   <exists/missing>
    Size:     <lines> lines
    Modified: <date>
    Entries:  <count> conversations

  <longterm-file>
    Status:   <exists/missing>
    Size:     <lines> lines
    Modified: <date>
    Entries:  <count> memories

CLAUDE.md Integration:
  ENGRAM section: <present/missing>
  @-reference:    <present/missing>

Recent Conversations (last 3):
  - YYYY-MM-DD HH:MM - Topic
  - YYYY-MM-DD HH:MM - Topic
  - YYYY-MM-DD HH:MM - Topic

Health Check:
  ✓ All files present
  ✓ Preferences populated
  ✓ CLAUDE.md integration active
  ✗ No conversation summaries yet
```

### 5. Health Check Items

Check for:
- Missing memory files → warn and offer to recreate via `memory-init`
- Empty preferences file → suggest filling in
- No conversation summaries → note that this is normal for new setups
- Missing settings file → offer to run `memory-init`
- Missing CLAUDE.md ENGRAM section → preferences won't auto-load; offer to re-run `memory-init` to restore

Versions

RepositoryScoreLicence
This page · legacybridge-tech/claude-plugins100MIT
alirezarezvani/claude-skills100MIT

Database snapshot: 13.11.2026 · package version 7fc2313e7992 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100memory-init
    Initialize the Engram memory system — creates configuration, memory files, and CLAUDE.md integration. Trigger when the user sets up persistent memory for a project, or when `.claude/memory-settings.json` is missing and a memory feature is requested.
  • 95engram-memory
    Use Engram as persistent memory across sessions — search it before starting work on a project, and save decisions and their reasoning before finishing. Use whenever the user refers to earlier work, past decisions, or something discussed in a previous session.
  • 100engram-digest
    Seed or top up this project's Engram graph from the existing codebase — an explicit, user-invoked digestion of the current working tree into typed memory nodes (decisions, principles, cautions, problems, insights, intents). Use when the user says "digest this project", "ingest…
  • 100memory-recall
    Search and recall memories from the Engram files. Trigger when a topic may relate to past discussions, when the user references previous context, or when the user asks "do you remember…".
  • 100memory
    Use when you want to explicitly store or recall knowledge across sessions. Prefer engram store/recall over file-based memory for decisions, patterns, insights, and cross-project knowledge. Also use when searching memories from previous coding sessions.
  • 100status
    Memory health dashboard showing line counts, topic files, capacity, stale entries, and recommendations. Use when the user runs /si:status or asks how full or healthy the agent memory is.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.