Memory Management

1---2name: memory-management3description: 'Persist SEO/GEO campaign context across Claude sessions with automatic hot-list, active work, and archive tiers. 项目记忆/跨会话'4version: "9.0.0"5license: Apache-2.06compatibility: "Claude Code ≥1.0, skills.sh marketplace, ClawHub marketplace, Vercel Labs skills ecosystem. No system packages required. Optional: MCP network access for SEO tool integrations."7homepage: "https://github.com/aaron-he-zhu/seo-geo-claude-skills"8when_to_use: "Use when reviewing, archiving, or cleaning up campaign memory. Also when the user asks to check saved findings, manage hot cache, or archive old data."9argument-hint: "[review|archive|cleanup]"10metadata:11  author: aaron-he-zhu12  version: "9.0.0"13  geo-relevance: "low"14  tags:15    - seo16    - geo17    - project-memory18    - context-management19    - campaign-tracking20    - session-context21    - hot-cache22    - 项目记忆23    - プロジェクト記憶24    - 프로젝트메모리25    - memoria-proyecto26  triggers:27    # EN-formal28    - "remember project context"29    - "save SEO data"30    - "track campaign progress"31    - "store keyword data"32    - "manage project memory"33    - "project context"34    - "refresh wiki index"35    - "build wiki index"36    - "wiki lint"37    # EN-casual38    - "remember this for next time"39    - "save my keyword data"40    - "keep track of this campaign"41    - "what did we decide last time"42    - "what do we know so far"43    - "project status"44    # EN-question45    - "how to save project progress"46    # ZH-pro47    - "项目记忆管理"48    - "SEO数据保存"49    - "跨会话记忆"50    - "刷新wiki索引"51    - "项目状况"52    # ZH-casual53    - "保存进度"54    - "上次说了什么"55    - "记住这个"56    # JA57    - "プロジェクト記憶"58    - "プロジェクト記憶管理"59    - "SEOデータ保存"60    - "セッション間記憶"61    - "wikiインデックス更新"62    - "キャンペーン履歴"63    # KO64    - "프로젝트 메모리"65    - "프로젝트 기억 관리"66    - "세션 기억"67    - "데이터 저장"68    - "캠페인 기록"69    # ES70    - "memoria del proyecto"71    - "guardar progreso"72    - "contexto de sesión"73    - "gestión de memoria"74    # PT75    - "memória do projeto"76    - "contexto de sessão"77    - "gerenciar memória"78    # Misspellings79    - "memroy management"80    - "project memery"81    - "hot cahce"82---83 84# Memory Management85 86> **[SEO & GEO Skills Library](https://github.com/aaron-he-zhu/seo-geo-claude-skills)** · 20 skills for SEO + GEO · [ClawHub](https://clawhub.ai/u/aaron-he-zhu) · [skills.sh](https://skills.sh/aaron-he-zhu/seo-geo-claude-skills)87> **System Mode**: This cross-cutting skill is part of the protocol layer and follows the shared [Skill Contract](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/skill-contract.md) and [State Model](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/state-model.md).88 89This skill implements a three-tier memory system (HOT/WARM/COLD) for SEO and GEO projects. HOT memory (80 lines max) loads automatically every session via the SessionStart hook. WARM memory loads on demand per skill. COLD memory is archived data queried only when explicitly requested. The skill manages the full lifecycle: capture, promote, demote, and archive.90 91**System role**: Campaign Memory Loop. It defines how project context is captured, promoted, archived, and handed off across sessions. It is the sole executor of WARM-to-COLD archival and the aggregator for cross-skill project status queries.92 93## When This Must Trigger94 95Use this whenever project state should survive the current session — even if the user doesn't use memory terminology:96 97- User says "remember this", "save this", "keep track of this"98- User asks "what did we decide", "what do we know", "project status"99- Setting up memory structure for a new SEO project100- After completing audits, ranking checks, or performance reports (Stop hook reminds automatically)101- When project context needs updating (new keywords, competitors, priorities)102- When you need to look up historical data or project-specific terminology103- After 30+ days of work to clean up and archive stale data104- When open-loops.md has items older than 7 days (SessionStart hook reminds automatically)105 106## What This Skill Does107 1081. **HOT tier management**: Maintains `memory/hot-cache.md` (80 lines max) — loaded automatically every session by SessionStart hook1092. **WARM Storage**: Organizes dated findings in `memory/` subdirectories — loaded on demand by relevant skills1103. **COLD Archive**: Moves stale data (90+ days unreferenced) to `memory/archive/` with date prefix1114. **Promotion**: Elevates frequently-referenced findings from WARM to HOT (3+ refs in 7 days, or 2+ skill refs)1125. **Demotion**: Moves unreferenced HOT items to WARM (30 days), WARM to COLD (90 days)1136. **Cross-Skill Aggregation**: When user asks "what do we know", aggregates from all `memory/` subdirectories1147. **Open Loop Tracking**: Maintains `memory/open-loops.md`, reminds user of stale items via SessionStart hook1158. **Wiki Layer (Phase 1-3)**: Maintains `memory/wiki/index.md` (auto-refreshed structured index of WARM files, project-isolated), generates compiled entity/keyword/topic pages with contradiction detection, runs wiki lint for orphans/stale claims/hash mismatches, and previews WARM retirement candidates. See [references/wiki spec](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/proposal-wiki-layer-v3.md).116 117## Quick Start118 119Start with one of these prompts. Finish with a hot-cache update plan and a handoff summary using the repository format in [Skill Contract](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/skill-contract.md).120 121### Initialize Wiki Index122 123```124Refresh wiki index125```126 127```128Build wiki index for [project name]129```130 131Generates `memory/wiki/index.md` from existing WARM files. Required once to enable wiki features; subsequent refreshes happen automatically.132 133### Initialize Memory Structure134 135```136Set up SEO memory for [project name]137```138 139```140Initialize memory structure for a new [industry] website optimization project141```142 143### Update After Analysis144 145```146Update memory after ranking check for [keyword group]147```148 149```150Refresh hot cache with latest competitor analysis findings151```152 153### Query Stored Context154 155```156What are our hero keywords?157```158 159```160Show me the last ranking update date for [keyword category]161```162 163```164Look up our primary competitors and their domain authority165```166 167### Promotion and Demotion168 169```170Promote [keyword] to hot cache171```172 173```174Archive stale data that hasn't been referenced in 30+ days175```176 177### Glossary Management178 179```180Add [term] to project glossary: [definition]181```182 183```184What does [internal jargon] mean in this project?185```186 187## Skill Contract188 189**Expected output**: a memory update plan, hot-cache changes, and a short handoff summary.190 191- **Reads**: current campaign facts, new findings from other skills, approved decisions, and the shared [State Model](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/state-model.md).192- **Writes**: updates to `memory/hot-cache.md`, `memory/open-loops.md`, `memory/decisions.md`, and related `memory/` folders. Manages WARM-to-COLD archival in `memory/archive/`. Compiles `memory/wiki/index.md` (auto-refreshed) and wiki compiled pages (user-confirmed). **Sole writer of wiki (with delegated auto-refresh)**: `memory-management` owns all wiki writes semantically. For performance, two narrowly-scoped auto-refresh operations are delegated to the PostToolUse and Stop hooks in [hooks/hooks.json](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/hooks/hooks.json) — specifically, index rebuilds of `memory/wiki/index.md` and append operations on `memory/wiki/log.md`. These hooks act on behalf of `memory-management` using the schema defined in this skill; any wiki-compiled page (entity/keyword/topic) still requires explicit `memory-management` invocation. **Auditor handoff archiving** (v7.1.0+): when triggered (by the Stop hook, by a direct user request, or via an auditor's "Save these results?" yes-response), append a structured block to `memory/audits/YYYY-MM.md`. The archive is consumed by `/seo:p2-review` for the 2026-07-10 tombstone evaluation tied to [ADR-001](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/decisions/2026-04-adr-001-inline-auditor-runbook.md). See [references/examples.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/cross-cutting/memory-management/references/examples.md) for the exact archive block format and rules.193- **Promotes**: durable strategy, blockers, terminology, entity candidates, and major deltas. Applies temperature lifecycle rules: promote to HOT on high reference frequency, demote on staleness.194- **Next handoff**: use the `Next Best Skill` below when the project memory baseline is ready for active work.195 196### Handoff Summary197 198Emit this shape when finishing the skill (see [skill-contract.md §Handoff Summary Format](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/skill-contract.md) for the authoritative format):199 200- **Status**: DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_INPUT201- **Objective**: what was analyzed, created, or fixed202- **Key Findings / Output**: the highest-signal result203- **Evidence**: URLs, data points, or sections reviewed204- **Open Loops**: blockers, missing inputs, or unresolved risks205- **Recommended Next Skill**: one primary next move206 207### Temperature Lifecycle Rules208 209> See [references/promotion-demotion-rules.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/cross-cutting/memory-management/references/promotion-demotion-rules.md) for the full promotion/demotion table and action procedures.210 211### Hook Integration212 213This skill's behavior is reinforced by the library's prompt-based hooks:214- **SessionStart**: loads `memory/hot-cache.md`, reminds of stale open loops; loads `memory/wiki/<project>/index.md` (or global `index.md`) if it exists; provides light-user guidance based on Quick Status when `next_action` items are available215- **PostToolUse**: after any WARM file write, silently refreshes `memory/wiki/index.md` (Phase 1); prompts to update compiled pages (Phase 2)216- **Stop**: prompts to save session findings, auto-saves veto issues to hot-cache; appends changelog entry to index.md bottom217 218## Data Sources219 220> See [CONNECTORS.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/CONNECTORS.md) for tool category placeholders.221 222**With ~~SEO tool + ~~analytics + ~~search console connected:**223Automatically populate memory from historical data: keyword rankings over time, competitor domain authority changes, traffic metrics, conversion data, backlink profile evolution. The skill will fetch current rankings, alert on significant changes, and update both hot cache and cold storage.224 225**With manual data only:**226Ask the user to provide:2271. Current target keywords with priority levels2282. Primary competitors (3-5 domains)2293. Key performance metrics and last update date2304. Active campaigns and their status2315. Any project-specific terminology or abbreviations232 233Proceed with memory structure creation using provided data. Note in memory/hot-cache.md which data requires manual updates vs. automated refresh.234 235## Instructions236 237When a user requests SEO memory management:238 239### 1. Initialize Memory Structure240 241For new projects, create the directory structure defined in the [State Model](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/state-model.md). Key directories: `memory/` (decisions, open-loops, glossary, entities, research, content, audits, monitoring) plus `memory/wiki/` (auto-managed compiled index with optional per-project subdirectories).242 243> **Templates**: [hot-cache-template.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/cross-cutting/memory-management/references/hot-cache-template.md) · [glossary-template.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/cross-cutting/memory-management/references/glossary-template.md) · [Wiki spec](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/proposal-wiki-layer-v3.md)244 245### 2. Context Lookup Flow246 247When a user references something unclear, follow this lookup sequence:248 249**Step 1: Check `memory/hot-cache.md` (hot cache)**250- Is it in active keywords?251- Is it in primary competitors?252- Is it in current priorities or campaigns?253 254**Step 2: Check Wiki Index** (`memory/wiki/index.md` or project-level) — locate relevant WARM files255 256**Step 3: Check memory/glossary.md**257- Is it defined as project terminology?258- Is it a custom segment or shorthand?259 260**Step 4: Check Cold Storage**261- Search memory/research/keywords/ for historical keyword context262- Search memory/research/competitors/ for past analyses263- Search memory/monitoring/reports/ for archived mentions264 265**Step 5: Ask User**266- If not found in any layer, ask for clarification267- Log the new term in glossary if it's project-specific268 269- **Decision provenance (v8.0.1+)**: when loading `memory/decisions.md`, verify each entry has `approved_by: user`. Entries with `approved_by: skill_inferred` or missing field are treated as **ADVISORY** — surface to user before using as authoritative. Auditor-class skills (content-quality-auditor, domain-authority-auditor) MUST ignore non-user-approved decisions when determining verdict. See [skill-contract.md §Promotion Rules](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/skill-contract.md).270 271Example lookup: User asks "Update rankings for our hero KWs" → Step 1 finds "Hero Keywords (Priority 1)" in hot-cache → Step 2 extracts keyword list → Step 3 runs ranking check → Step 4 updates `memory/hot-cache.md` and `memory/monitoring/rank-history/YYYY-MM-DD-ranks.csv`.272 273### 3. Promotion & Demotion Logic274 275> **Reference**: See [references/promotion-demotion-rules.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/cross-cutting/memory-management/references/promotion-demotion-rules.md) for detailed promotion/demotion triggers (keywords, competitors, metrics, campaigns) and the action procedures for each.276 277### 4. Update Triggers, Archive Management & Cross-Skill Integration278 279> **Reference**: See [references/update-triggers-integration.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/cross-cutting/memory-management/references/update-triggers-integration.md) for the complete update procedures after ranking checks, competitor analyses, audits, and reports; monthly/quarterly archive routines; and integration points with all 8 connected skills (keyword-research, rank-tracker, competitor-analysis, content-gap-analysis, seo-content-writer, content-quality-auditor, domain-authority-auditor).280 281### 5. Memory Hygiene Checks282 283When invoked for review or cleanup:284 2851. **Line count check**: Count lines in `memory/hot-cache.md`. If >80, list oldest entries for archival.2862. **Byte check**: If hot-cache exceeds 25KB, warn and recommend trimming long entries.2873. **Staleness scan**: List memory files older than 30 days that have not been referenced. Recommend archival for files >90 days.2884. **Frontmatter audit**: Check that all memory files (except hot-cache.md) have `name`, `description`, and `type` in their frontmatter. Report any missing fields.289 290### 6. Save Results291 292After delivering any memory update or aggregation to the user, ask:293 294> "Save these results for future sessions?"295 296If yes, write a dated summary to the appropriate `memory/` path using filename `YYYY-MM-DD-<topic>.md` containing:297- One-line verdict or headline finding298- Top 3-5 actionable items299- Open loops or blockers300- Source data references301 302If any veto-level issue was found (CORE-EEAT T04, C01, R10 or CITE T03, T05, T09), also append a one-liner to `memory/hot-cache.md` without asking.303 304## Validation Checkpoints305 306**Structure**: memory/hot-cache.md ≤80 lines; directory matches state model; glossary.md populated; timestamped filenames.307 308**Content**: hot-cache "Last Updated" current; every keyword has rank + target + status; every competitor has DA + position; campaigns have status + ETA.309 310**Lookups**: term reference finds correct layer; promotion/demotion round-trip works; glossary covers all shorthand.311 312**Updates after events**: ranking check → `memory/monitoring/rank-history/` dated snapshot; competitor analysis → `memory/research/competitors/` dated file; audit → top action items in hot-cache; monthly report → metrics snapshot refreshed.313 314## Examples, Advanced Features & Practical Limitations315 316> **Reference**: See [references/examples.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/cross-cutting/memory-management/references/examples.md) for three complete examples (hero keyword rankings, glossary lookup, e-commerce project init), advanced features (smart context loading, memory health check, bulk promotion/demotion, memory snapshot, cross-project memory, wiki lint), and practical limitations (concurrent access, cold storage retrieval, data freshness, wiki compilation).317 318## GDPR / Privacy Compliance319 320`memory/` may store third-party personal data — entity names, founder bios, LinkedIn profiles, author/journalist names surfaced by `entity-optimizer` or research skills. Under GDPR Art 4(1) (applies to **processing of personal data of EU/EEA/UK residents** regardless of where the controller is located), these qualify as "personal data". The user is the data controller. Non-EU users without EU/EEA/UK data subjects may still face analogous obligations under CCPA/CPRA (California), PIPEDA (Canada), LGPD (Brazil), or other national regimes. **Not legal advice.**321 322### Retention policy323- WARM files: archive to `memory/archive/` after 90 days unreferenced (default lifecycle)324- COLD archive: never auto-deleted, but eligible for Art 17 erasure requests325- All files: user MUST honor Art 17 requests from data subjects (individuals named in memory)326 327### Deletion flow (Art 17 / CCPA §1798.105)328Invoke: `memory-management purge <entity-name-or-slug>`329 330This skill then:3311. Greps all files under `memory/` (including `memory/archive/`) for the entity name, slug, or domain3322. Presents matches to user for confirmation3333. Deletes matching entries from `memory/entities/<slug>.md`, `memory/entities/candidates.md`, and surfaces references in other files for manual review3344. Logs the purge to `memory/audits/gdpr-purges.md` with date + subject requested335 336### Lawful basis reminder337Before writing a third-party person to `memory/entities/`, the user must have one lawful basis per GDPR Art 6 (where GDPR applies — see scope note above): `consent`, `legitimate_interest`, `contract`, or equivalent. Advisory — this skill does not enforce, and does not substitute for legal review.338 339## Reference Materials340 341- [references/examples.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/cross-cutting/memory-management/references/examples.md) — Worked examples, advanced features, practical limitations, and the auditor handoff archive block format & rules342- [references/promotion-demotion-rules.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/cross-cutting/memory-management/references/promotion-demotion-rules.md) — Full promotion/demotion table and action procedures343- [references/update-triggers-integration.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/cross-cutting/memory-management/references/update-triggers-integration.md) — Update procedures, archive routines, and cross-skill integration points344- [CORE-EEAT Content Benchmark](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/core-eeat-benchmark.md) — Content quality scoring stored in memory345- [CITE Domain Rating](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/cite-domain-rating.md) — Domain authority scoring stored in memory346 347## Next Best Skill348 349- **Primary**: [keyword-research](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/research/keyword-research/SKILL.md) — seed or refresh campaign strategy with current demand signals.