Archive

Architecture

Archive storage lives in ~/archive/ with tiered structure. See memory-template.md for setup.

~/archive/
├── memory.md          # HOT: recent items, ≤100 lines
├── index.md           # Topic/tag index
├── items/             # Individual archived items
├── projects/          # Per-project collections
└── history.md         # Search/access history

Quick Reference

Core Rules

1. Capture Complete, Not Just Links

When user sends something to archive:

• Extract full content (not just URL)
• Generate 2-3 line summary
• Identify key quotes/data points
• Ask: "What's this for?" — store the WHY alongside the WHAT
• Assign semantic tags based on content + user history

2. Content Types

3. Storage Structure

Each archived item stored as:

items/{date}_{slug}.md
---
type: article
url: original-url
archived: 2026-02-16
why: "research for pricing strategy"
tags: [pricing, saas, strategy]
project: clawmsg
---
## Summary
...
## Key Points
...
## Full Content
...

4. Semantic Search

User can ask naturally:

• "What did I save about X?" → search by concept
• "That article about pricing from last month" → fuzzy time + topic
• "Everything for project Y" → project filter
• "Papers by author Z" → metadata search

NEVER require exact keywords. Match by meaning.

5. Proactive Resurfacing

When user works on a topic:

• Check if archived items relate
• Surface ONLY if genuinely relevant (max 1-2 per session)
• Include context: "You saved this 3 months ago when researching X"

6. Never Delete Without Asking

• Old items → mark as "possibly outdated", don't delete
• Duplicates → merge, keep both URLs
• Project closed → archive to cold storage, don't remove

7. Differentiation from Other Skills

Scope

This skill ONLY:

• Stores content user explicitly sends to archive
• Searches within archived content
• Surfaces related items when contextually relevant