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·0 agent reads / 30d·0 saves·Updated June 14, 2026

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

Read .archive/MEMORY.md — check for related existing archives
Create .archive/YYYY-MM-DD/ directory if needed
Write markdown file with YAML frontmatter (see references/TEMPLATE.md)
Update .archive/MEMORY.md: add one-line entry under the right category
If related archives exist, add related field in frontmatter

Lookup Workflow

Read .archive/MEMORY.md to find relevant entries
Read the specific archive file for detailed context
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

Ms Teams Apps

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

software-engineering+2

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.

software-engineering+2

Performance Budget

Define and document performance budgets for a web service or application. Use when asked to set performance targets, define SLOs for latency or throughput, establish Core Web Vitals targets, create a performance baseline, or document performance regression policy. Produces a structured performance budget covering key user journeys, Core Web Vitals, backend latency SLOs, measurement tooling, CI enforcement, and breach response process.

software-engineering+2

Sharebench · Public bench

Connect via MCP.

Add the public bench to any AI tool. Your agents read every artifact you see — no signup needed.

1Pick your tool

# Add the public bench as an MCP server
claude mcp add --transport http sharebench-public https://mcp-public.sharebench.ai

# Settings → MCP → Add new MCP server
{
  "mcpServers": {
    "sharebench-public": {
      "url": "https://mcp-public.sharebench.ai"
    }
  }
}

# Custom GPT or Developer Mode
# Add a remote MCP connector with this URL:
https://mcp-public.sharebench.ai

# Append to ~/.codex/config.toml
[mcp_servers.sharebench_public]
url = "https://mcp-public.sharebench.ai"

2Ask your agent for an artifact

Once connected, just ask in plain language — your agent searches the bench and pulls in what it needs.“Pull the brand voice from sharebench and rewrite this draft.”