Skip to content
Skills Library
AI & agents · Automation

agent-memory

/agent-memory

Persist and retrieve repository-specific knowledge using AGENTS.md files. Use when you want to save important information about a codebase (build commands, code style, workflows) for future sessions.

Repository
agent ↗
Licence
MIT
Last repository change
14.10.2026

Assessment and security

92/ 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.
Content27 / 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 14.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

Persist and retrieve repository-specific knowledge using AGENTS.md files. Use when you want to save important information about a codebase (build commands, code style, workflows) for future sessions.

Original author description

Persist and retrieve repository-specific knowledge using AGENTS.md files. Use when you want to save important information about a codebase (build commands, code style, workflows) for future sessions.

How it works

SKILL.md has no level-two headings · 25 lines, 287 words

SKILL.md preview
---
name: agent-memory
description: Persist and retrieve repository-specific knowledge using AGENTS.md files. Use when you want to save important information about a codebase (build commands, code style, workflows) for future sessions.
triggers:
- /remember
---

* Repository memory: Use AGENTS.md in each repository root to store and access important information.
  - If this file exists, it will be added to your context automatically.
  - If missing, you should create it unless the user has explicitly asked you to not do so.

* Store and maintain **general knowledge** that will be helpful for most future tasks:
  1. Repository structure
  2. Common commands (build, lint, test, pre-commit, etc.)
  3. Code style preferences
  4. Workflows and best practices
  5. Any other repository-specific knowledge you learn

* IMPORTANT: ONLY LOG the information that would be helpful for different future tasks, for example, how to configure the settings, how to setup the repository. Do NOT add issue-specific information (e.g., what specific error you have ran into and how you fix it).

* When adding new information:
  - ALWAYS ask for user confirmation first by listing the exact items (numbered 1, 2, 3, etc.) you plan to save to repo.md
  - Only save the items the user approves (they may ask you to save a subset)
  - Ensure it integrates nicely with existing knowledge in repo.md
  - Reorganize the content if needed to maintain clarity and organization
  - Group related information together under appropriate sections or headings
  - If you've only explored a portion of the codebase, clearly note this limitation in the repository structure documentation
  - If you don't know the essential commands for working with the repository, such as lint or typecheck, ask the user and suggest adding them to repo.md for future reference (with permission)

When you receive this message, please review and summarize your recent actions and observations, then present a list of valuable information that should be saved in AGENTS.md to the user.

Versions

RepositoryScoreLicence
This page · HelixDevelopment/agent92MIT
TerminalSkills/skills100Apache-2.0
komluk/scaffolding100MIT
nirholas/three.ws100Apache-2.0
nimadorostkar/Claude-Skills-collection100MIT
alirezarezvani/claude-skills100MIT
norifumi3/cc-marketplace100MIT
OpenHands/extensions92MIT
VoDaiLocz/kilo-kit-mcp90Apache-2.0

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 1665d38bcec5 (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-init
    Scaffold a project-local memory directory and AGENTS.md guidance for reusable agent knowledge. Use when a user wants to initialize `.agents/memories/` or another project memory path so future agents can read and maintain durable project context.
  • 100memory-and-context
    Store, retrieve, search, and manage persistent memory across sessions. Triggers on: store memory, save this, retrieve, forget, manage memory, context, pattern.
  • 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.
  • 84memory
    Store and retrieve durable agent memory — remember decisions, preferences, and session outcomes with calibrated salience; recall prior context before acting or resuming a project. Use whenever you store a memory, search memory, retrieve prior context, or check what was learned in past sessions.
  • 100session-memory
    Manage durable working-session memory for coding agents. Use when a user asks to preserve or recover agent context across disconnects, VS Code restarts, long-running work, handoffs, or any session where important state should be written periodically under the repo's session directory.
  • 100remember-session
    Use when the user asks to save, remember, record or persist what happened in the current session to MCP Memory Service ("save this session", "store the learnings", "vermerke es im Memory"), or when a session ends having produced decisions, root causes, or open follow-ups that a…

Feedback and reports

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