archive

Archive session learnings into dated markdown entries with YAML frontmatter.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/daanteijema-beep/ai-gids-platform --skill archive-daanteijema-beep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archive
Source: https://github.com/daanteijema-beep/ai-gids-platform/tree/main/.agents/skills/archive
Command: npx skills add https://github.com/daanteijema-beep/ai-gids-platform --skill archive-daanteijema-beep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents valuable debugging, deployment, and decision history from being lost between sessions by organizing it into a searchable archive.

Core Features & Use Cases

  • Session Knowledge Capture: Archives significant work (deployments, migrations, tricky bug fixes) into dated markdown entries.
  • Cross-Session Reuse: Maintains a centralized .archive/MEMORY.md index and loads it automatically on session start for quicker recall.
  • Structured Discovery: Uses YAML frontmatter with tags and categories so past solutions can be found via keyword search.

Quick Start

Use the archive skill to write a new dated entry under .archive/ capturing what went wrong, how it was fixed, and the exact commands or config changes that resolved it.

Frequently Asked Questions about archive

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

FAQPage Schema
How do I preserve debugging solutions and deployment logs for cross-session reuse?

You can preserve debugging solutions and deployment logs for cross-session reuse by creating a dated markdown entry with YAML frontmatter in a .archive directory and updating a centralized MEMORY.md index for searchable retrieval.

What is the best way to index session learnings using markdown and YAML frontmatter?

Indexing session learnings using markdown and YAML frontmatter involves storing entries under a dated .archive/YYYY-MM-DD/ folder structure and maintaining a master .archive/MEMORY.md file to enable keyword search across past work.

Can I use knowledge management archiving to track multi-step operational knowledge like migrations?

Yes, knowledge management archiving supports tracking multi-step operational knowledge like migrations by capturing what went wrong, how it was fixed, and the exact commands or config changes in structured markdown entries.

Does archiving session learnings require updating a memory index manually?

Archiving session learnings requires updating a .archive/MEMORY.md index manually after creating a dated markdown entry, ensuring the centralized index loads automatically on session start for quicker recall of past solutions.

When do I need to create a dated markdown entry for archiving tricky bug fixes?

You need to create a dated markdown entry for archiving tricky bug fixes whenever you complete significant work like resolving complex bugs, shipping releases, or completing migrations to prevent valuable history from being lost between sessions.