Skip to content
Skills Library
AI & agents · Tool integration

memory-view

/memory-view

View and manage persistent memory - active issues, open MRs, follow-ups, environment health, recent sessions. Use when user says "view memory", "what's in memory?", or "show current work".

Repository
skills ↗
Licence
Apache-2.0
Last repository change
27.10.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
0
URLs in SKILL.md
0
Deprecation

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

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

View and manage persistent memory - active issues, open MRs, follow-ups, environment health, recent sessions. Use when user says "view memory", "what's in memory?", or "show current work".

Triggers from the description

view memorywhat, or
Original author description

View and manage persistent memory - active issues, open MRs, follow-ups, environment health, recent sessions. Use when user says "view memory", "what's in memory?", or "show current work".

How it works

  1. Inputs
  2. Workflow
  3. Key Details
Original SKILL.md headings · 73 lines, 333 words
SKILL.md preview
---
name: memory-view
description: View and manage persistent memory - active issues, open MRs, follow-ups, environment health, recent sessions. Use when user says "view memory", "what's in memory?", or "show current work".
---

# Memory View - Inspect and Manage Memory

Shows current work state, learned patterns, follow-ups, and environment status. Supports optional actions.

## Inputs

| Input | Type | Default | Purpose |
|-------|------|---------|---------|
| `section` | string | "all" | all, work, followups, environments, patterns, sessions |
| `action` | string | - | clear_completed, add_followup, clear_old_sessions |
| `followup_text` | string | - | For add_followup action |
| `followup_priority` | string | "normal" | high, medium, normal |
| `slack_format` | bool | false | Use `<url\|text>` links |

## Workflow

### 1. Load Memory via MCP
- `memory_read("state/current_work")` - active issues, open MRs, follow_ups
- `memory_read("state/environments")` - environment health
- `memory_read("learned/patterns")` - error patterns
- `memory_read("learned/runbooks")` - runbooks
- List `memory/sessions/*.yaml` - recent session logs (last 5 files)

### 2. Perform Action (if requested)
- **clear_completed:** Filter `active_issues` (remove Done/Closed/Resolved), filter `open_mrs` (remove merged). Use `memory_update` or write back.
- **add_followup:** Append to `follow_ups` with task, priority, created. Use `memory_append("state/current_work", "follow_ups", item)`.
- **clear_old_sessions:** Delete session files older than 7 days from `memory/sessions/`.

### 3. Format Output by Section

**work:** Active issues (key, summary, status, branch), Open MRs (id, title, url, needs_review, is_draft)

**followups:** List with priority emoji (🔴 high, 🟡 medium, ⚪ normal)

**environments:** Per-env status (healthy/issues/unknown), last_check, alerts, ephemeral namespaces

**patterns:** Error patterns with pattern + meaning/fix

**sessions:** Recent dates with last 5 actions each

### 4. Output Format

```markdown
# 🧠 Memory View

## 📋 Current Work
### Active Issues (N)
- **AAP-XXXXX** - summary | Status: X | Branch: `branch`
### Open MRs (N)
- !1234 - title 👀📝

## 📌 Follow-ups
- 🔴/🟡/⚪ task

## 🌐 Environment Status
### ✅/⚠️/❓ stage/production/konflux

## 💡 Learned Patterns
## 📜 Recent Sessions

---
### Available Actions
- Clear completed: skill_run("memory_view", '{"action": "clear_completed"}')
- Add follow-up: skill_run("memory_view", '{"action": "add_followup", "followup_text": "..."}')
```

## Key Details

- **Chains to:** `memory_edit`, `memory_cleanup`
- Use `memory_ask("What am I working on?")` for quick context
- Linkify Jira keys and MR IDs in output

Versions

RepositoryScoreLicence
This page · dmzoneill/skills100Apache-2.0
pinperepette/agd-memory100MIT

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

Downloads in the last 30 days: 0 · ranking

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

Similar skills

  • 100memory
    Manage the persistent memory layer in .claude/memory/ — list, search, save, update, delete, dedupe. Use to inspect what memories exist, write a new one, or clean up stale entries.
  • 90bm-orient
    Orient Claude from Basic Memory before substantial repo work by reading active tasks, open decisions, recent checkpoints, and repo conventions. Use when resuming old work or when the user asks where things stand.
  • 90mem9
    Persistent cloud memory for OpenClaw agents. Use when users say: - "install mem9" - "setup memory" - "add memory plugin" - "openclaw memory" - "mem9 onboarding" - "memory not working" - "import memories" - "upload sessions
  • 100auto-memory
    This skill should be used when the user asks to 'set up memory', 'create memory files', 'create MEMORY.md', 'set up topic files', 'improve memory organization', 'what should I remember', 'how to structure memory files', 'MEMORY.md is too long', 'what goes in memory vs topic…
  • 100agent-memory
    Give an agent persistent semantic memory with @three-ws/agent-memory. Use when code needs to remember facts across sessions, recall them by meaning, read the entity graph, or curate an agent's working context.
  • 100memory-config
    View and modify ConKeeper memory configuration settings. Use to adjust token budget, output style, and other preferences after memory initialization.

Feedback and reports

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