memory-keeper

Auto-save project artifacts into timestamped memory backups with recovery prompts.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/mr-phariyawit/startup --skill memory-keeper-mr-phariyawit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-keeper
Source: https://github.com/mr-phariyawit/startup/tree/main/skills/memory-keeper
Command: npx skills add https://github.com/mr-phariyawit/startup --skill memory-keeper-mr-phariyawit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures the Structural Memory of the project is preserved, artifacts are backed up, and recovery protocols are available when failures occur.

Core Features & Use Cases

  • Structural integrity checks for essential directories (agent/rules, docs, .memory)
  • Auto-save protocol that snapshots major task artifacts into timestamped memory folders
  • Recovery guidance including prompts to reset and re-import rules/workflows after failures

Quick Start

After finishing a major task, trigger memory-keeper to auto-save key artifacts into a timestamped memory folder.

Frequently Asked Questions about memory-keeper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-save project artifacts when hitting a context limit?

To auto-save artifacts during context-limit events, trigger a memory backup protocol that snapshots key project files into timestamped folders. This preserves structural memory and provides deterministic recovery prompts to restore context seamlessly.

What is the best way to back up project structure before an error scenario causes data loss?

The best way to back up project structure is using an auto-save protocol that checks essential directories like docs/ and agent/rules/, capturing timestamped memory backups of artifacts to ensure structural integrity and enable recovery after failures.

How do I recover project context after a critical task failure?

Recovering project context involves using a lightweight recovery protocol with prompts to reset and re-import rules and workflows. It leverages timestamped memory backups saved prior to the failure to restore the project state.

Does memory-keeper require any specific dependencies to manage artifact backups?

No dependencies are required to manage artifact backups. The skill independently performs structural integrity checks for essential directories like .memory/ and executes the auto-save protocol without external packages.

When should I trigger a context-management backup for my software project?

You should trigger a context-management backup at end-of-task closures, during error scenarios, or when approaching context-limit events. This ensures all major task artifacts are safely preserved in timestamped memory folders.

Can I use this auto-save protocol to verify essential project directories?

Yes, the auto-save protocol includes structural integrity checks for essential project directories such as docs/, agent/rules/, and .memory/. It validates these structures before snapshotting artifacts into memory backups.