memory-recall

Retrieve relevant project decisions, prior prompts, style preferences, debugging notes, and past outputs with source traceability.

Skill by bl1nk42

IndexedApache-2.0★ 2

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/bl1nk42-memory-recall

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Retrieve relevant project decisions, prior prompts, style preferences, debugging notes, and past outputs with source traceability. Use when the user asks what was decided, why a design exists, or wants to reuse a known style/workflow.

Use cases: design, productivity

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/memory-recall

What's inside

Skill name: memory-recall
Description: Retrieve relevant project decisions, prior prompts, style preferences, debugging notes, and past outputs with source traceability. Use when the user asks what was decided, why a design exists, or wants to reuse a known style/workflow.
License: Apache-2.0
Instructions: 19 lines in SKILL.md · view on GitHub

Files (2)

SKILL.md
memory-contract.md · references/

SKILL.md (first lines)

# Memory Recall

## Retrieval contract
Search narrowly, retrieve multiple candidates, expand only relevant hits, and report source/date plus confidence. Never present a memory as current fact without checking the repository/config when the question concerns current code.

## Workflow
1. Form a query from the user's intent, project name, model/style, and time range if known.
2. Search the memory index or registry with top-k 5.
3. Remove generic or contradictory results.
4. Expand the strongest results and compare decisions, alternatives, and unresolved items.
5. Cross-check current files before recommending a change.
6. Return: key memory, source reference, confidence, and how it affects the current task.

## Image-system memory
Use `semantic_search`, `get_entity`, votes, and `learn_style` for image preferences. Positive examples teach only style/lighting/mood; negative examples become avoided concepts after repeated downvotes. Do not leak image bytes or private prompts into audit logs.

## Failure behavior
If no memory is found, say so. Do not fill the gap with invented history. If memories conflict, show the conflict and prefer the latest verified project state.

From bl1nk42/image-gen, Apache-2.0.

Signals

Stars: 2
Forks: 0
Open issues: 0
Last commit (this folder): Sep 25, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License: Apache-2.0
Repository: github.com/bl1nk42/image-gen
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from bl1nk42

Cite this page

memory-recall skill. Agent Mart. https://agentmart.dev/skills/bl1nk42-memory-recall (last updated 2026-10-24)