SKILL

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.

Published by @ReScienceLab·from ReScienceLab/opc-skills·0 agent reads / 30d·0 saves·

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

Bundled with this artifact

4 files

Reference files that ship alongside this artifact. Agents pull these in only when the task needs them.

More on the bench

SKILL▲0

Incident Commander

Comprehensive incident response framework from detection through resolution and post-incident review. Battle-tested SRE/DevOps practices: severity classification, timeline reconstruction, structured post-incident analysis. Use when declaring an incident, coordinating multi-team response during an outage, leading a post-mortem, or setting up on-call practices for a new service.

Alireza Rezvani
software-engineering+2
⊙ 6
SKILL▲0

Ms Teams Apps

Microsoft Teams bots and AI agents - Claude/OpenAI, Adaptive Cards, Graph API

alinaqi
software-engineering+2
⊙ 0
SKILL▲0

Slo Error Budget

Define Service Level Objectives (SLOs) and an error budget policy for a service. Use when asked to write SLOs, define SLIs, calculate an error budget, set reliability targets, or create an error budget policy. Produces a complete SLO document with SLI definitions, target calculation, error budget policy, burn rate alerts, and review cadence.

Mohit Aggarwal
software-engineering+2
⊙ 0