Archive
- 1k installs
- 1.2k repo stars
- Updated July 27, 2026
- resciencelab/opc-skills
archive is a productivity skill that persists session learnings, bug fixes, and deploy notes under `.archive/YYYY-MM-DD/` with tagged markdown and a searchable `.archive/MEMORY.md` index for the next agent run.
About
archive is an opc-skills skill that captures debugging solutions, deployment logs, and task learnings as indexed markdown after significant work completes. It writes dated folders under `.archive/yyyy-mm-dd/` and maintains a `.archive/MEMORY.md` index with searchable tags for cross-session knowledge reuse. Developers reach for archive after deploys, migrations, major features, tricky bug resolutions, or when the user says archive this. The skill also supports consulting prior archives at the start of new sessions so agents reuse prior fixes instead of rediscovering them.
- Writes dated folders `.archive/yyyy-mm-dd/` with indexed markdown and searchable tags
- Maintains `.archive/MEMORY.md` one-line category index for cross-session lookup
- Lookup workflow: grep archives and read MEMORY before infra, deploy, or CI repeats
- YAML frontmatter template with optional `related` links to prior archives
- Triggers on deploy completion, hard bugs, multi-step learnings, or user says archive this
Archive by the numbers
- 1,006 all-time installs (skills.sh)
- +18 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #467 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/resciencelab/opc-skills --skill archiveAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1k |
|---|---|
| repo stars | ★ 1.2k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | resciencelab/opc-skills ↗ |
How do you persist agent session learnings across runs?
Persist session learnings, bug fixes, and deploy notes under `.archive/YYYY-MM-DD/` with tagged markdown and a searchable `.archive/MEMORY.md` index for the next agent run.
Who is it for?
Developers using long-running agent sessions who want searchable cross-session memory for bugs, deploys, and migrations.
Skip if: Teams needing formal wiki documentation, ticket systems, or git-based ADRs instead of local agent memory files.
When should I use this skill?
User completes a significant task, resolves a tricky bug, deploys, says archive this, or starts a session needing prior learnings.
What you get
Dated `.archive/YYYY-MM-DD/` markdown files and updated `.archive/MEMORY.md` searchable index
- dated archive markdown files
- .archive/MEMORY.md index
Files
Archive Skill
Capture, index, and reuse project knowledge across sessions.
When to Archive
- After completing a significant task (deploy, migration, major feature)
- After resolving a tricky debugging session
- When the user says "archive this"
- After any multi-step process with learnings worth preserving
When to Consult Archives
- Before debugging infrastructure, deploy, or CI issues
- Before repeating a process done in a past session
- When encountering an error that may have been solved before
Search: grep -ri "keyword" .archive/ Index: .archive/MEMORY.md
Archive Workflow
1. Read .archive/MEMORY.md — check for related existing archives 2. Create .archive/YYYY-MM-DD/ directory if needed 3. Write markdown file with YAML frontmatter (see references/TEMPLATE.md) 4. Update `.archive/MEMORY.md`: add one-line entry under the right category 5. If related archives exist, add related field in frontmatter
Lookup Workflow
1. Read .archive/MEMORY.md to find relevant entries 2. Read the specific archive file for detailed context 3. Apply learnings to current task
Categories
- infrastructure — AWS, ECS, IAM, networking, secrets, CloudWatch
- release — TestFlight, versioning, Git Flow, CHANGELOG
- debugging — Bug fixes, error resolution, gotchas
- feature — Feature design, implementation notes
- design — UI/UX, icons, visual design
Rules
.archive/must be in.gitignore— local-only notes- Keep entries concise but reproducible
- Focus on problems, fixes, and exact commands
- Always update MEMORY.md after creating an archive
- Use descriptive filenames (e.g.,
cloudwatch-logging.mdnotsession.md) - Include YAML frontmatter with
tags,category, and optionalrelated
{
"name": "archive",
"description": "Archive session learnings, debugging solutions, and deployment logs. Auto-loads .archive/MEMORY.md at session start for cross-session knowledge reuse.",
"version": "1.1.0"
}
{
"description": "Load .archive/MEMORY.md into session context at startup for cross-session knowledge reuse",
"hooks": {
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "python3 \"${CLAUDE_PLUGIN_ROOT:-${DROID_PLUGIN_ROOT}}/hooks/load-memory.py\""
}
]
}
]
}
}
#!/usr/bin/env python3
import json
import os
import sys
project_dir = (
os.environ.get("FACTORY_PROJECT_DIR")
or os.environ.get("CLAUDE_PROJECT_DIR")
or os.getcwd()
)
memory_file = os.path.join(project_dir, ".archive", "MEMORY.md")
if os.path.exists(memory_file):
with open(memory_file, "r", encoding="utf-8") as f:
content = f.read()
output = {
"hookSpecificOutput": {
"hookEventName": "SessionStart",
"additionalContext": f"## Archived Project Knowledge (.archive/MEMORY.md)\n\n{content}",
}
}
print(json.dumps(output))
sys.exit(0)
Archive Template
Use this template when creating archive files.
---
tags: [keyword1, keyword2, keyword3]
category: infrastructure | release | debugging | feature | design
related: [other-archive-filename-without-ext]
---
# {Title} - {YYYY-MM-DD}
## Summary
One-line description of what was accomplished.
## Context
- **Branch**: {branch name}
- **Version**: {if applicable}
- **Related Issue**: {if applicable}
## Issues Encountered & Solutions
### 1. {Issue Title}
- {Description of the problem}
- **Fix**: {How it was resolved}
## Key Changes
{Code snippets, config changes, or commands that were critical}
## Lessons Learned
{Optional: insights for future reference}Frontmatter Fields
- tags: searchable keywords for
grep -ri "tags:.*keyword" .archive/ - category: one of
infrastructure,release,debugging,feature,design - related: filenames (without
.md) of related archives for cross-referencing
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kHow it compares
Use archive for lightweight agent-session memory in the repo; use ADR or wiki skills when organization-wide formal documentation is required.
FAQ
Where does archive store session learnings?
archive stores learnings as tagged markdown under `.archive/yyyy-mm-dd/` dated directories and updates a searchable `.archive/MEMORY.md` index. Agents can consult that index on future runs to reuse prior fixes and deploy notes.
When should archive be used?
archive should run after completing significant tasks such as deploys, migrations, or major features, after resolving tricky bugs, or when the user explicitly says archive this. It preserves knowledge worth reusing across sessions.
Is Archive safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.