progressive-memory

Included with Lifetime

$97 forever

# Progressive Memory

General

What this skill does

# Progressive Memory

Token-efficient memory system for AI agents. Scan an index first, fetch details on demand. Based on progressive disclosure principles from claude-mem.

## The Problem

Traditional memory dumps everything into context:
- Load 3500 tokens of history
- 94% is irrelevant to current task
- Wastes attention budget, causes context rot

## The Solution

**Progressive disclosure:** Show what exists first, let the agent decide what to fetch.

```
Before: 3500 tokens loaded → 200 relevant (6%)
After:  100 token index → fetch 200 needed (100%)
```

## Memory Format

### Daily Files (`memory/YYYY-MM-DD.md`)

```markdown
# 2026-02-01 (AgentName)

## Index (~70 tokens to scan)
| # | Type | Summary | ~Tok |
|---|------|---------|------|
| 1 | 🔴 | Auth bug - use browser not CLI | 80 |
| 2 | 🟢 | Deployed SEO fixes to 5 pages | 120 |
| 3 | 🟤 | Decided to split content by account | 60 |

---

### #1 | 🔴 Auth Bug | ~80 tokens
**Context:** Publishing via CLI
**Issue:** "Unauthorized" even with fresh tokens
**Workaround:** Use browser import instead
**Status:** Unresolved
```

### Long-Term Memory (`MEMORY.md`)

```markdown
## 📋 Index (~100 tokens)
| ID | Type | Category | Summary | ~Tok |
|----|------|----------|---------|------|
| R1 | 🚨 | Rules | Twitter posting protocol | 150 |
| G1 | 🔴 | Gotcha | CLI auth broken | 60 |
| D1 | 🟤 | Decision | Content split by account | 60 |

---

### R1 | Twitter Posting Protocol | ~150 tokens
- POST ALL tweets in ONE session
- NEVER post hook without full thread
- VERIFY everything before reporting done
```

## Observation Types

| Icon | Type | When to Use |
|------|------|-------------|
| 🚨 | rule | Critical rule, must follow |
| 🔴 | gotcha | Pitfall, don't repeat this |
| 🟡 | fix | Bug fix, workaround |
| 🔵 | how | Technical explanation |
| 🟢 | change | What changed, deployed |
| 🟣 | discovery | Learning, insight |
| 🟠 | why | Design rationale |
| 🟤 | decision | Architecture decision |
| ⚖️ | tradeoff | Deliberate compromise |

## Token Estimation

| Content Type | Tokens |
|--------------|--------|
| Simple fact | ~30-50 |
| Short explanation | ~80-150 |
| Detailed context | ~200-400 |
| Full summary | ~500-1000 |

## How It Works

1. **Session starts** → Agent scans index tables (~100-200 tokens)
2. **Agent sees types** → Prioritizes 🔴 gotchas over 🟢 changes
3. **Agent sees costs** → Decides if 400-token entry is worth it
4. **Fetch on demand** → Only load what's relevant to current task

## Benefits

- **Token savings:** ~65,000 tokens/day with 20 memory checks
- **Faster scanning:** Icons enable visual pattern recognition
- **Precise references:** IDs like #1, G3, D5 for exact lookup
- **Cost awareness:** Token counts for ROI decisions

## Integration

Works with any markdown-based memory system. No database required.

For Clawdbot users:
1. Update `AGENTS.md` with format instructions
2. Restructure `MEMORY.md` with index
3. Use format in daily `memory/YYYY-MM-DD.md` files

---

**Built by [LXGIC Studios](https://lxgicstudios.com)**

🔗 [GitHub](https://github.com/lxgicstudios/progressive-memory) · [Twitter](https://x.com/lxgicstudios)

Files: 3

Size: 3.4 KB

Complexity: 7/100

Category: General

Source: https://github.com/boomsystel-code/openclaw-workspace/tree/main/skills/progressive-memory

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts