archive

Archive dated Markdown notes with YAML frontmatter and update the MEMORY.md index.

10|2|Updated Mar 2, 2026

Search Tags:#workflow #documentation #memory #notes #archive #knowledge-management

Ready to run

npx skills add https://github.com/ReScienceLab/agent-world-network --skill archive-resciencelab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: archive
Source: https://github.com/ReScienceLab/agent-world-network/tree/main/.agents/skills/archive
Command: npx skills add https://github.com/ReScienceLab/agent-world-network --skill archive-resciencelab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Archive and index knowledge from tasks, debugging, and deployments to a centralized, searchable archive for cross-session reuse.

Core Features & Use Cases

Persistent memory: writes notes to .archive/YYYY-MM-DD and updates the .archive/MEMORY.md index.
Structured documentation: uses YAML frontmatter for tags and metadata to enable quick retrieval.
Workflow enablement: supports post-mortems, deployment logs, and major task summaries across sessions.

Quick Start

Create a new archive entry describing your latest task and save it under .archive with an updated MEMORY.md index.

Frequently Asked Questions about archive

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

FAQPage Schema

How do I archive debugging notes and deployment logs for cross-session retrieval?▼

Archive debugging notes and deployment logs by writing entries to dated Markdown files under .archive/YYYY-MM-DD with mandatory YAML frontmatter, then updating a centralized .archive/MEMORY.md index for cross-session retrieval.

What is the best way to maintain persistent memory across multiple project sessions?▼

Maintain persistent memory by storing task learnings and post-incident reviews in a structured Markdown repository with YAML frontmatter tags and a MEMORY.md index, ensuring knowledge is searchable across sessions.

Does this knowledge management workflow require any external dependencies?▼

This knowledge management workflow requires no external dependencies, relying solely on standard Markdown files, YAML frontmatter for metadata, and a local .archive directory structure for indexing.

How do I structure post-incident reviews for fast reuse in future tasks?▼

Structure post-incident reviews by creating an archive entry with descriptive tags and a description in YAML frontmatter, saving it under .archive/YYYY-MM-DD, and updating the MEMORY.md index for fast reuse.

Can I use Markdown with YAML frontmatter for project handoff documentation?▼

Markdown with YAML frontmatter is used for project handoff documentation by assigning descriptive tags and metadata to dated entries, enabling structured storage and quick retrieval from the indexed repository.

When should I not use a dated Markdown repository for knowledge management?▼

A dated Markdown repository for knowledge management is not suited for real-time collaborative editing or non-text-heavy data storage, as it enforces a static file-based index and YAML frontmatter structure without concurrent multi-user support.