archive
installsforks
How to install archive?
resciencelab/opc-skills/archive
$npx -y skills add ReScienceLab/opc-skills --skill archiveArchive 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 in
SKILL.md
| 1 | # Archive Skill |
| 2 | |
| 3 | Capture, index, and reuse project knowledge across sessions. |
| 4 | |
| 5 | ## When to Archive |
| 6 | |
| 7 | - After completing a significant task (deploy, migration, major feature) |
| 8 | - After resolving a tricky debugging session |
| 9 | - When the user says "archive this" |
| 10 | - After any multi-step process with learnings worth preserving |
| 11 | |
| 12 | ## When to Consult Archives |
| 13 | |
| 14 | - Before debugging infrastructure, deploy, or CI issues |
| 15 | - Before repeating a process done in a past session |
| 16 | - When encountering an error that may have been solved before |
| 17 | |
| 18 | **Search**: `grep -ri "keyword" .archive/` |
| 19 | **Index**: `.archive/MEMORY.md` |
| 20 | |
| 21 | ## Archive Workflow |
| 22 | |
| 23 | 1. Read `.archive/MEMORY.md` — check for related existing archives |
| 24 | 2. Create `.archive/YYYY-MM-DD/` directory if needed |
| 25 | 3. Write markdown file with YAML frontmatter (see `references/TEMPLATE.md`) |
| 26 | 4. **Update `.archive/MEMORY.md`**: add one-line entry under the right category |
| 27 | 5. If related archives exist, add `related` field in frontmatter |
| 28 | |
| 29 | ## Lookup Workflow |
| 30 | |
| 31 | 1. Read `.archive/MEMORY.md` to find relevant entries |
| 32 | 2. Read the specific archive file for detailed context |
| 33 | 3. Apply learnings to current task |
| 34 | |
| 35 | ## Categories |
| 36 | |
| 37 | - **infrastructure** — AWS, ECS, IAM, networking, secrets, CloudWatch |
| 38 | - **release** — TestFlight, versioning, Git Flow, CHANGELOG |
| 39 | - **debugging** — Bug fixes, error resolution, gotchas |
| 40 | - **feature** — Feature design, implementation notes |
| 41 | - **design** — UI/UX, icons, visual design |
| 42 | |
| 43 | ## Rules |
| 44 | |
| 45 | - `.archive/` must be in `.gitignore` — local-only notes |
| 46 | - Keep entries concise but reproducible |
| 47 | - Focus on **problems, fixes, and exact commands** |
| 48 | - Always update MEMORY.md after creating an archive |
| 49 | - Use descriptive filenames (e.g., `cloudwatch-logging.md` not `session.md`) |
| 50 | - Include YAML frontmatter with `tags`, `category`, and optional `related` |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
