Skip to content
Skills Library
AI & agents · Research

memory-query

/memory-query

Search project memory files for a specific topic, decision, or constraint and return matching entries with citations. Use when you need to find what was decided about X, why Y was chosen, or whether Z is a known issue. Trigger this when someone says: what do we know about X, was there a decision about Y, check memory for Z, find the memory entry for X, what did we decide about Y, look up memory for X. Do NOT use for a full memory hygiene pass — use /memory-audit instead.

Licence
MIT
Last repository change
13.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 13.10.2026, without references to retired models or APIs.

Licence

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

What it does and when to use it

Search project memory files for a specific topic, decision, or constraint and return matching entries with citations. Use when you need to find what was decided about X, why Y was chosen, or whether Z is a known issue. Trigger this when someone says: what do we know about X, was there a decision about Y, check memory for Z, find the memory entry for X, what did we decide about Y, look up memory for X. Do NOT use for a full memory hygiene pass — use /memory-audit instead.

Original author description

Search project memory files for a specific topic, decision, or constraint and return matching entries with citations. Use when you need to find what was decided about X, why Y was chosen, or whether Z is a known issue. Trigger this when someone says: what do we know about X, was there a decision about Y, check memory for Z, find the memory entry for X, what did we decide about Y, look up memory for X. Do NOT use for a full memory hygiene pass — use /memory-audit instead.

How it works

  1. 1. Discover active memory files
  2. 2. Read and match
  3. 3. Return results
  4. Gotchas
Original SKILL.md headings · 59 lines, 470 words
SKILL.md preview
---
name: memory-query
description: "Search project memory files for a specific topic, decision, or constraint and return matching entries with citations. Use when you need to find what was decided about X, why Y was chosen, or whether Z is a known issue. Trigger this when someone says: what do we know about X, was there a decision about Y, check memory for Z, find the memory entry for X, what did we decide about Y, look up memory for X. Do NOT use for a full memory hygiene pass — use /memory-audit instead."
---

# Memory Query

Search the project's `memory/` directory for entries relevant to a specific topic, decision, or constraint. Returns matching entries with file paths and direct quotes.

If `memory/` does not exist in the current project, report that and stop.

## 1. Discover active memory files

```
Glob("memory/**/*.md")
```

Filter to active files only — skip any file where the frontmatter contains `status: superseded` or `status: archived`. These are history and should not be surfaced as current answers.

## 2. Read and match

**Triage on the filename first.** Filenames follow `YYYY-MM-DD-{prefix}-brief-slug.md`, so the slug
is a usable summary of the entry and every file has one. Read the full body of any file whose slug —
or whose subdirectory — suggests relevance to the query.

`description:` is an **optional** frontmatter field present in only a minority of files. Use it as a
second signal where it happens to exist; never rely on it being there, and never skip a file because
it lacks one.

Memory-file frontmatter carries no summary-name key. One was removed on 2026-09-02 because it
duplicated the filename. (This SKILL.md's own frontmatter is skill metadata, unrelated to the
memory dialect.)

Match the file to the query if it:
- Directly names the topic, technology, module, or pattern the user asked about
- Contains a decision, rationale, or constraint related to the query
- Documents a known issue or workaround for the queried area

## 3. Return results

For each matching file, output:

```
**[memory type] — [file path]**
> "[direct quote from the most relevant section]"

Summary: [one sentence describing what this memory says about the query topic]
```

Group results by memory type (decisions, architecture, context, known-issues) if multiple files match.

If no active memory files match the query, say so explicitly:

> No active memory entries found for "[query]". If a decision was made, it may not have been recorded yet — consider running /memory-audit to identify gaps.

Never hallucinate a memory entry. If the content is not in a file, it does not exist.

## Gotchas

- **Superseded and archived files are history only:** Do not surface them as current answers, even if they are relevant to the query. If a superseded file would have answered the question, note that the topic was once addressed but is now superseded and point to the `superseded-by:` file if present. That field is sometimes prose rather than a filename, so read it before citing it as a file.
- **Partial matches:** If a file mentions the topic in passing but does not contain a decision about it, include it with a note that it is contextual rather than a direct answer.
- **Multiple conflicting active files:** If two active files at the same scope contradict each other, surface both and flag the conflict rather than picking one silently.

Versions

The database has no other skills named memory-query.

Database snapshot: 13.11.2026 · package version d1acc44fc3eb (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-audit
    Runs a memory hygiene pass on the project memory/ directory. Reviews all active memory files against the current codebase and archives or supersedes stale entries. Use before major feature work or when memory files feel out of date. Trigger this when someone says: clean up…
  • 100memory-edit
    Modify or remove entries from memory. Actions: remove (from list), update (field value). Use when user says "edit memory", "update memory", or "remove from memory".
  • 100memory-lint
    Use when saving or editing agent memory files, when MEMORY.md and the memory directory may have drifted (unindexed files, dangling index entries), when a recalled memory seems missing or duplicated, or for a periodic hygiene pass over a file-based memory store. Also use for…
  • 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.
  • 90memory
    Use when you need the Codex Copilot equivalent of Claude Copilot /memory: inspect recent cc memory entries, known references, and task progress.
  • 90memory
    This skill should be used when the user asks to record a design decision, search past project decisions, inspect the Alfred memory timeline, or work with the alfred-memory MCP server. Use it to call the namespaced MCP tools instead of inventing history.

Feedback and reports

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