# Archive

> Archive session learnings, debugging solutions, and deployment logs to .archive/yyyy-mm-dd/ as indexed markdown with searchable tags. Use when completing a significant task, resolving a tricky bug, deploying, or when the user says \"archive this\". Maintains .archive/MEMORY.md index for cross-session knowledge reuse.

Source: https://skillsagentes.com/skills/resciencelab/opc-skills/archive
Repository: https://github.com/ReScienceLab/opc-skills
Author: resciencelab
License: Apache-2.0
Updated: hace 5 meses
Context cost: 80 tok installed, 538 tok once triggered, 1.1k tok with every bundled file
Bundle: 5 files, 4 KB
Permissions requested: none declared

## Install

```bash
npx -y skills add ReScienceLab/opc-skills --skill archive --agent claude-code
```

## What it does

- Guarda aprendizajes de sesión, soluciones de debugging y logs de despliegue en `.archive/yyyy-mm-dd/` como markdown indexado
- Mantiene `.archive/MEMORY.md` como índice central con etiquetas buscables para reutilizar conocimiento entre sesiones
- Actualiza `MEMORY.md` con una línea por entrada tras crear cada archivo, incluyendo tags, category y related

## Use it when

- Al completar una tarea significativa como un deploy, migración o feature grande
- Tras resolver una sesión de debugging complicada
- Cuando el usuario dice "archive this"
- Antes de depurar infraestructura, deploy o CI, o al repetir un proceso ya hecho antes

## What triggers it

- "Archive this, por favor"
- "Guarda lo que aprendimos sobre este bug de CloudWatch"
- "Busca en el archivo si ya resolvimos este error antes"

## Before you install

- Requiere que `.archive/` esté en `.gitignore` porque son notas locales.

## Files

- .factory-plugin/plugin.json — 217 B
- SKILL.md — 2 KB
- hooks/hooks.json — 361 B
- hooks/load-memory.py — 614 B
- references/TEMPLATE.md — 963 B

## SKILL.md

Reproduced verbatim from ReScienceLab/opc-skills under Apache-2.0. This section is the upstream document and is in English.

# 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.md` not `session.md`)
- Include YAML frontmatter with `tags`, `category`, and optional `related`

---

Skills Agentes — https://skillsagentes.com/skills/resciencelab/opc-skills/archive