[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78S7CFQ26Z214JFJQFD110D":3,"skill-same:01M78S7CFQ26Z214JFJQFD110D":101},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M78S7CFQ26Z214JFJQFD110D","memory-management",null,"Persist SEO\u002FGEO project context, brand guidelines, and target keywords across sessions so your agent remembers strategy without re-explaining. Use when the user asks to \"remember project context\", \"save SEO data\", \"track campaign progress\", \"store keyword data\", \"manage project memory\", \"remember this for next time\", \"save my keyword data\", \"keep track of this campaign\". Manages a two-layer memory system (hot cache + cold storage) with intelligent promotion\u002Fdemotion.","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmemory-management\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: memory-management\nversion: \"4.0.0\"\ndescription: 'Persist SEO\u002FGEO project context, brand guidelines, and target keywords across sessions so your agent remembers strategy without re-explaining. Use when the user asks to \"remember project context\", \"save SEO data\", \"track campaign progress\", \"store keyword data\", \"manage project memory\", \"remember this for next time\", \"save my keyword data\", \"keep track of this campaign\". Manages a two-layer memory system (hot cache + cold storage) with intelligent promotion\u002Fdemotion.'\nlicense: Apache-2.0\ncompatibility: \"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.\"\nhomepage: \"https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills\"\nmetadata:\n  author: aaron-he-zhu\n  version: \"4.0.0\"\n  geo-relevance: \"low\"\n  tags:\n    - seo\n    - geo\n    - project memory\n    - context management\n    - campaign tracking\n    - data persistence\n    - keyword tracking\n    - project context\n    - context-memory\n    - project-memory\n    - seo-tracking\n    - campaign-tracking\n    - session-context\n    - hot-cache\n    - project-continuity\n  triggers:\n    - \"remember project context\"\n    - \"save SEO data\"\n    - \"track campaign progress\"\n    - \"store keyword data\"\n    - \"manage project memory\"\n    - \"save progress\"\n    - \"project context\"\n    - \"remember this for next time\"\n    - \"save my keyword data\"\n    - \"keep track of this campaign\"\n---\n\n# Memory Management\n\n\n> **[SEO & GEO Skills Library](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills)** · 20 skills for SEO + GEO · [ClawHub](https:\u002F\u002Fclawhub.ai\u002Fu\u002Faaron-he-zhu) · [skills.sh](https:\u002F\u002Fskills.sh\u002Faaron-he-zhu\u002Fseo-geo-claude-skills)\n\n\u003Cdetails>\n\u003Csummary>Browse all 20 skills\u003C\u002Fsummary>\n\n**Research** · [keyword-research](..\u002F..\u002Fresearch\u002Fkeyword-research\u002F) · [competitor-analysis](..\u002F..\u002Fresearch\u002Fcompetitor-analysis\u002F) · [serp-analysis](..\u002F..\u002Fresearch\u002Fserp-analysis\u002F) · [content-gap-analysis](..\u002F..\u002Fresearch\u002Fcontent-gap-analysis\u002F)\n\n**Build** · [seo-content-writer](..\u002F..\u002Fbuild\u002Fseo-content-writer\u002F) · [geo-content-optimizer](..\u002F..\u002Fbuild\u002Fgeo-content-optimizer\u002F) · [meta-tags-optimizer](..\u002F..\u002Fbuild\u002Fmeta-tags-optimizer\u002F) · [schema-markup-generator](..\u002F..\u002Fbuild\u002Fschema-markup-generator\u002F)\n\n**Optimize** · [on-page-seo-auditor](..\u002F..\u002Foptimize\u002Fon-page-seo-auditor\u002F) · [technical-seo-checker](..\u002F..\u002Foptimize\u002Ftechnical-seo-checker\u002F) · [internal-linking-optimizer](..\u002F..\u002Foptimize\u002Finternal-linking-optimizer\u002F) · [content-refresher](..\u002F..\u002Foptimize\u002Fcontent-refresher\u002F)\n\n**Monitor** · [rank-tracker](..\u002F..\u002Fmonitor\u002Frank-tracker\u002F) · [backlink-analyzer](..\u002F..\u002Fmonitor\u002Fbacklink-analyzer\u002F) · [performance-reporter](..\u002F..\u002Fmonitor\u002Fperformance-reporter\u002F) · [alert-manager](..\u002F..\u002Fmonitor\u002Falert-manager\u002F)\n\n**Cross-cutting** · [content-quality-auditor](..\u002Fcontent-quality-auditor\u002F) · [domain-authority-auditor](..\u002Fdomain-authority-auditor\u002F) · [entity-optimizer](..\u002Fentity-optimizer\u002F) · **memory-management**\n\n\u003C\u002Fdetails>\n\nThis skill implements a two-layer memory system for SEO and GEO projects, maintaining a hot cache for active context and cold storage for detailed historical data. It automatically promotes frequently referenced items and demotes stale data, ensuring optimal context loading and efficient project memory.\n\n## When to Use This Skill\n\n- Setting up memory structure for a new SEO project\n- After completing audits, ranking checks, or performance reports\n- When starting a new campaign or optimization initiative\n- When project context needs updating (new keywords, competitors, priorities)\n- When you need to look up historical data or project-specific terminology\n- After 30+ days of work to clean up and archive stale data\n- When context retrieval feels slow or cluttered\n\n## What This Skill Does\n\n1. **Hot Cache Management**: Maintains CLAUDE.md (~100 lines) with active context that's always loaded\n2. **Cold Storage Organization**: Structures detailed archives in memory\u002F subdirectories\n3. **Context Lookup**: Implements efficient lookup flow from hot cache to cold storage\n4. **Promotion\u002FDemotion**: Moves items between layers based on reference frequency\n5. **Glossary Maintenance**: Manages project-specific terminology and shorthand\n6. **Update Triggers**: Refreshes memory after audits, reports, or ranking checks\n7. **Archive Management**: Time-stamps and archives old data systematically\n\n## How to Use\n\n### Initialize Memory Structure\n\n```\nSet up SEO memory for [project name]\n```\n\n```\nInitialize memory structure for a new [industry] website optimization project\n```\n\n### Update After Analysis\n\n```\nUpdate memory after ranking check for [keyword group]\n```\n\n```\nRefresh hot cache with latest competitor analysis findings\n```\n\n### Query Stored Context\n\n```\nWhat are our hero keywords?\n```\n\n```\nShow me the last ranking update date for [keyword category]\n```\n\n```\nLook up our primary competitors and their domain authority\n```\n\n### Promotion and Demotion\n\n```\nPromote [keyword] to hot cache\n```\n\n```\nArchive stale data that hasn't been referenced in 30+ days\n```\n\n### Glossary Management\n\n```\nAdd [term] to project glossary: [definition]\n```\n\n```\nWhat does [internal jargon] mean in this project?\n```\n\n## Data Sources\n\n> See [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md) for tool category placeholders.\n\n**With ~~SEO tool + ~~analytics + ~~search console connected:**\nAutomatically 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.\n\n**With manual data only:**\nAsk the user to provide:\n1. Current target keywords with priority levels\n2. Primary competitors (3-5 domains)\n3. Key performance metrics and last update date\n4. Active campaigns and their status\n5. Any project-specific terminology or abbreviations\n\nProceed with memory structure creation using provided data. Note in CLAUDE.md which data requires manual updates vs. automated refresh.\n\n## Instructions\n\nWhen a user requests SEO memory management:\n\n### 1. Initialize Memory Structure\n\nFor new projects, create the following structure:\n\n```markdown\n## Directory Structure\n\nproject-root\u002F\n├── CLAUDE.md                           # Hot cache (~100 lines)\n└── memory\u002F\n    ├── glossary.md                     # Project terminology\n    ├── keywords\u002F\n    │   ├── hero-keywords.md           # Top priority keywords\n    │   ├── secondary-keywords.md      # Medium priority\n    │   ├── long-tail-keywords.md      # Long-tail opportunities\n    │   └── historical-rankings.csv    # Dated ranking data\n    ├── competitors\u002F\n    │   ├── primary-competitors.md     # Top 3-5 competitors\n    │   ├── [competitor-domain].md     # Individual reports\n    │   └── analysis-history\u002F          # Dated analyses\n    ├── audits\u002F\n    │   ├── technical\u002F                 # Technical SEO audits\n    │   ├── content\u002F                   # Content audits\n    │   ├── domain\u002F                    # Domain authority (CITE) audits\n    │   └── backlink\u002F                  # Backlink audits\n    ├── content-calendar\u002F\n    │   ├── active-calendar.md         # Current quarter\n    │   ├── published-content.md       # Performance tracking\n    │   └── archive\u002F                   # Past calendars\n    └── reports\u002F\n        ├── monthly\u002F                   # Monthly reports\n        ├── quarterly\u002F                 # Quarterly reports\n        └── campaign\u002F                  # Campaign-specific reports\n```\n\n> **Templates**: See [references\u002Fhot-cache-template.md](.\u002Freferences\u002Fhot-cache-template.md) for the complete CLAUDE.md hot cache template and [references\u002Fglossary-template.md](.\u002Freferences\u002Fglossary-template.md) for the project glossary template.\n\n### 4. Context Lookup Flow\n\nWhen a user references something unclear, follow this lookup sequence:\n\n**Step 1: Check CLAUDE.md (Hot Cache)**\n- Is it in active keywords?\n- Is it in primary competitors?\n- Is it in current priorities or campaigns?\n\n**Step 2: Check memory\u002Fglossary.md**\n- Is it defined as project terminology?\n- Is it a custom segment or shorthand?\n\n**Step 3: Check Cold Storage**\n- Search memory\u002Fkeywords\u002F for historical data\n- Search memory\u002Fcompetitors\u002F for past analyses\n- Search memory\u002Freports\u002F for archived mentions\n\n**Step 4: Ask User**\n- If not found in any layer, ask for clarification\n- Log the new term in glossary if it's project-specific\n\nExample lookup:\n\n```markdown\nUser: \"Update rankings for our hero KWs\"\n\nStep 1: Check CLAUDE.md → Found \"Hero Keywords (Priority 1)\" section\nStep 2: Extract keyword list from hot cache\nStep 3: Execute ranking check\nStep 4: Update both CLAUDE.md and memory\u002Fkeywords\u002Fhistorical-rankings.csv\n```\n\n### 5. Promotion & Demotion Logic\n\n> **Reference**: See [references\u002Fpromotion-demotion-rules.md](.\u002Freferences\u002Fpromotion-demotion-rules.md) for detailed promotion\u002Fdemotion triggers (keywords, competitors, metrics, campaigns) and the action procedures for each.\n\n### 6. Update Triggers, Archive Management & Cross-Skill Integration\n\n> **Reference**: See [references\u002Fupdate-triggers-integration.md](.\u002Freferences\u002Fupdate-triggers-integration.md) for the complete update procedures after ranking checks, competitor analyses, audits, and reports; monthly\u002Fquarterly 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).\n\n## Validation Checkpoints\n\n### Structure Validation\n- [ ] CLAUDE.md exists and is under 150 lines (aim for ~100)\n- [ ] memory\u002F directory structure matches template\n- [ ] glossary.md exists and is populated with project basics\n- [ ] All historical data files include timestamps in filename or metadata\n\n### Content Validation\n- [ ] CLAUDE.md \"Last Updated\" date is current\n- [ ] Every keyword in hot cache has current rank, target rank, and status\n- [ ] Every competitor has domain authority and position assessment\n- [ ] Every active campaign has status percentage and expected completion date\n- [ ] Key Metrics Snapshot shows \"Previous\" values for comparison\n\n### Lookup Validation\n- [ ] Test lookup flow: reference a term → verify it finds it in correct layer\n- [ ] Test promotion: manually promote item → verify it appears in CLAUDE.md\n- [ ] Test demotion: manually archive item → verify removed from CLAUDE.md\n- [ ] Glossary contains all custom segments and shorthand used in CLAUDE.md\n\n### Update Validation\n- [ ] After ranking check, historical-rankings.csv has new row with today's date\n- [ ] After competitor analysis, analysis-history\u002F has dated file\n- [ ] After audit, top action items appear in CLAUDE.md priorities\n- [ ] After monthly report, metrics snapshot reflects new data\n\n## Examples\n\n> **Reference**: See [references\u002Fexamples.md](.\u002Freferences\u002Fexamples.md) for three complete examples: (1) updating hero keyword rankings with memory refresh, (2) glossary lookup flow, and (3) initializing memory for a new e-commerce project.\n\n## Advanced Features\n\n### Smart Context Loading\n\n```\nLoad full context for [campaign name]\n```\n\nRetrieves hot cache + all cold storage files related to campaign.\n\n### Memory Health Check\n\n```\nRun memory health check\n```\n\nAudits memory structure: finds orphaned files, missing timestamps, stale hot cache items, broken references.\n\n### Bulk Promotion\u002FDemotion\n\n```\nPromote all keywords ranking in top 10 to hot cache\n```\n\n```\nDemote all completed campaigns from Q3 2024\n```\n\n### Memory Snapshot\n\n```\nCreate memory snapshot for [date\u002Fmilestone]\n```\n\nTakes point-in-time copy of entire memory structure for major milestones (site launches, algorithm updates, etc.).\n\n### Cross-Project Memory\n\n```\nCompare memory with [other project name]\n```\n\nIdentifies keyword overlaps, competitor intersections, and strategy similarities across multiple projects.\n\n## Practical Limitations\n\n- **Concurrent access**: If multiple Claude sessions update memory simultaneously, later writes may overwrite earlier ones. Mitigate by using timestamped filenames for audit reports rather than overwriting a single file.\n- **Cold storage retrieval**: Files in `memory\u002F` subdirectories are only loaded when explicitly requested. They do not appear in Claude's context automatically. The hot cache (`CLAUDE.md`) is the primary cross-session mechanism.\n- **CLAUDE.md size**: The hot cache should stay concise (\u003C200 lines). If it grows too large, archive older metrics to cold storage.\n- **Data freshness**: Memory reflects the last time each skill was run. Stale data (>90 days) should be flagged for refresh.\n\n## Tips for Success\n\n1. **Keep hot cache lean** - CLAUDE.md should never exceed 150 lines. If it grows larger, aggressively demote.\n2. **Date everything** - Every file in cold storage should have YYYY-MM-DD in filename or prominent metadata.\n3. **Update after every significant action** - Don't let memory drift from reality. Update immediately after ranking checks, audits, or reports.\n4. **Use glossary liberally** - If you find yourself explaining a term twice, add it to glossary.\n5. **Review hot cache weekly** - Quick scan to ensure everything there is still relevant and active.\n6. **Automate where possible** - If ~~SEO tool or ~~search console connected, set up automatic updates to historical-rankings.csv.\n7. **Archive aggressively** - Better to have data in cold storage and not need it than clutter hot cache.\n8. **Link between layers** - CLAUDE.md should always reference where detailed data lives (\"Full data: memory\u002Fkeywords\u002F\").\n9. **Timestamp changes** - When updating CLAUDE.md, always update \"Last Updated\" date.\n10. **Use memory for continuity** - If you switch between different analysis sessions, memory ensures nothing is forgotten.\n\n## Reference Materials\n\n- [CORE-EEAT Content Benchmark](..\u002F..\u002Freferences\u002Fcore-eeat-benchmark.md) — Content quality scoring stored in memory\n- [CITE Domain Rating](..\u002F..\u002Freferences\u002Fcite-domain-rating.md) — Domain authority scoring stored in memory\n\n## Related Skills\n\n- [rank-tracker](..\u002F..\u002Fmonitor\u002Frank-tracker\u002F) — Provides ranking data to update memory\n- [competitor-analysis](..\u002F..\u002Fresearch\u002Fcompetitor-analysis\u002F) — Generates competitor reports for storage\n- [keyword-research](..\u002F..\u002Fresearch\u002Fkeyword-research\u002F) — Discovers keywords to add to memory\n- [performance-reporter](..\u002F..\u002Fmonitor\u002Fperformance-reporter\u002F) — Creates reports that trigger memory updates\n- [content-gap-analysis](..\u002F..\u002Fresearch\u002Fcontent-gap-analysis\u002F) — Identifies optimization priorities for hot cache\n- [seo-content-writer](..\u002F..\u002Fbuild\u002Fseo-content-writer\u002F) — Logs published content to memory calendar\n- [content-quality-auditor](..\u002Fcontent-quality-auditor\u002F) — Content audit results stored in memory for tracking\n- [domain-authority-auditor](..\u002Fdomain-authority-auditor\u002F) — CITE domain audit results stored in memory for tracking\n- [entity-optimizer](..\u002Fentity-optimizer\u002F) — Store entity audit results for tracking over time\n","# Memory Management\n\n\n> **[SEO & GEO Skills Library](https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills)** · 20 skills for SEO + GEO · [ClawHub](https:\u002F\u002Fclawhub.ai\u002Fu\u002Faaron-he-zhu) · [skills.sh](https:\u002F\u002Fskills.sh\u002Faaron-he-zhu\u002Fseo-geo-claude-skills)\n\n\u003Cdetails>\n\u003Csummary>Browse all 20 skills\u003C\u002Fsummary>\n\n**Research** · [keyword-research](..\u002F..\u002Fresearch\u002Fkeyword-research\u002F) · [competitor-analysis](..\u002F..\u002Fresearch\u002Fcompetitor-analysis\u002F) · [serp-analysis](..\u002F..\u002Fresearch\u002Fserp-analysis\u002F) · [content-gap-analysis](..\u002F..\u002Fresearch\u002Fcontent-gap-analysis\u002F)\n\n**Build** · [seo-content-writer](..\u002F..\u002Fbuild\u002Fseo-content-writer\u002F) · [geo-content-optimizer](..\u002F..\u002Fbuild\u002Fgeo-content-optimizer\u002F) · [meta-tags-optimizer](..\u002F..\u002Fbuild\u002Fmeta-tags-optimizer\u002F) · [schema-markup-generator](..\u002F..\u002Fbuild\u002Fschema-markup-generator\u002F)\n\n**Optimize** · [on-page-seo-auditor](..\u002F..\u002Foptimize\u002Fon-page-seo-auditor\u002F) · [technical-seo-checker](..\u002F..\u002Foptimize\u002Ftechnical-seo-checker\u002F) · [internal-linking-optimizer](..\u002F..\u002Foptimize\u002Finternal-linking-optimizer\u002F) · [content-refresher](..\u002F..\u002Foptimize\u002Fcontent-refresher\u002F)\n\n**Monitor** · [rank-tracker](..\u002F..\u002Fmonitor\u002Frank-tracker\u002F) · [backlink-analyzer](..\u002F..\u002Fmonitor\u002Fbacklink-analyzer\u002F) · [performance-reporter](..\u002F..\u002Fmonitor\u002Fperformance-reporter\u002F) · [alert-manager](..\u002F..\u002Fmonitor\u002Falert-manager\u002F)\n\n**Cross-cutting** · [content-quality-auditor](..\u002Fcontent-quality-auditor\u002F) · [domain-authority-auditor](..\u002Fdomain-authority-auditor\u002F) · [entity-optimizer](..\u002Fentity-optimizer\u002F) · **memory-management**\n\n\u003C\u002Fdetails>\n\nThis skill implements a two-layer memory system for SEO and GEO projects, maintaining a hot cache for active context and cold storage for detailed historical data. It automatically promotes frequently referenced items and demotes stale data, ensuring optimal context loading and efficient project memory.\n\n## When to Use This Skill\n\n- Setting up memory structure for a new SEO project\n- After completing audits, ranking checks, or performance reports\n- When starting a new campaign or optimization initiative\n- When project context needs updating (new keywords, competitors, priorities)\n- When you need to look up historical data or project-specific terminology\n- After 30+ days of work to clean up and archive stale data\n- When context retrieval feels slow or cluttered\n\n## What This Skill Does\n\n1. **Hot Cache Management**: Maintains CLAUDE.md (~100 lines) with active context that's always loaded\n2. **Cold Storage Organization**: Structures detailed archives in memory\u002F subdirectories\n3. **Context Lookup**: Implements efficient lookup flow from hot cache to cold storage\n4. **Promotion\u002FDemotion**: Moves items between layers based on reference frequency\n5. **Glossary Maintenance**: Manages project-specific terminology and shorthand\n6. **Update Triggers**: Refreshes memory after audits, reports, or ranking checks\n7. **Archive Management**: Time-stamps and archives old data systematically\n\n## How to Use\n\n### Initialize Memory Structure\n\n```\nSet up SEO memory for [project name]\n```\n\n```\nInitialize memory structure for a new [industry] website optimization project\n```\n\n### Update After Analysis\n\n```\nUpdate memory after ranking check for [keyword group]\n```\n\n```\nRefresh hot cache with latest competitor analysis findings\n```\n\n### Query Stored Context\n\n```\nWhat are our hero keywords?\n```\n\n```\nShow me the last ranking update date for [keyword category]\n```\n\n```\nLook up our primary competitors and their domain authority\n```\n\n### Promotion and Demotion\n\n```\nPromote [keyword] to hot cache\n```\n\n```\nArchive stale data that hasn't been referenced in 30+ days\n```\n\n### Glossary Management\n\n```\nAdd [term] to project glossary: [definition]\n```\n\n```\nWhat does [internal jargon] mean in this project?\n```\n\n## Data Sources\n\n> See [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md) for tool category placeholders.\n\n**With ~~SEO tool + ~~analytics + ~~search console connected:**\nAutomatically 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.\n\n**With manual data only:**\nAsk the user to provide:\n1. Current target keywords with priority levels\n2. Primary competitors (3-5 domains)\n3. Key performance metrics and last update date\n4. Active campaigns and their status\n5. Any project-specific terminology or abbreviations\n\nProceed with memory structure creation using provided data. Note in CLAUDE.md which data requires manual updates vs. automated refresh.\n\n## Instructions\n\nWhen a user requests SEO memory management:\n\n### 1. Initialize Memory Structure\n\nFor new projects, create the following structure:\n\n```markdown\n## Directory Structure\n\nproject-root\u002F\n├── CLAUDE.md                           # Hot cache (~100 lines)\n└── memory\u002F\n    ├── glossary.md                     # Project terminology\n    ├── keywords\u002F\n    │   ├── hero-keywords.md           # Top priority keywords\n    │   ├── secondary-keywords.md      # Medium priority\n    │   ├── long-tail-keywords.md      # Long-tail opportunities\n    │   └── historical-rankings.csv    # Dated ranking data\n    ├── competitors\u002F\n    │   ├── primary-competitors.md     # Top 3-5 competitors\n    │   ├── [competitor-domain].md     # Individual reports\n    │   └── analysis-history\u002F          # Dated analyses\n    ├── audits\u002F\n    │   ├── technical\u002F                 # Technical SEO audits\n    │   ├── content\u002F                   # Content audits\n    │   ├── domain\u002F                    # Domain authority (CITE) audits\n    │   └── backlink\u002F                  # Backlink audits\n    ├── content-calendar\u002F\n    │   ├── active-calendar.md         # Current quarter\n    │   ├── published-content.md       # Performance tracking\n    │   └── archive\u002F                   # Past calendars\n    └── reports\u002F\n        ├── monthly\u002F                   # Monthly reports\n        ├── quarterly\u002F                 # Quarterly reports\n        └── campaign\u002F                  # Campaign-specific reports\n```\n\n> **Templates**: See [references\u002Fhot-cache-template.md](.\u002Freferences\u002Fhot-cache-template.md) for the complete CLAUDE.md hot cache template and [references\u002Fglossary-template.md](.\u002Freferences\u002Fglossary-template.md) for the project glossary template.\n\n### 4. Context Lookup Flow\n\nWhen a user references something unclear, follow this lookup sequence:\n\n**Step 1: Check CLAUDE.md (Hot Cache)**\n- Is it in active keywords?\n- Is it in primary competitors?\n- Is it in current priorities or campaigns?\n\n**Step 2: Check memory\u002Fglossary.md**\n- Is it defined as project terminology?\n- Is it a custom segment or shorthand?\n\n**Step 3: Check Cold Storage**\n- Search memory\u002Fkeywords\u002F for historical data\n- Search memory\u002Fcompetitors\u002F for past analyses\n- Search memory\u002Freports\u002F for archived mentions\n\n**Step 4: Ask User**\n- If not found in any layer, ask for clarification\n- Log the new term in glossary if it's project-specific\n\nExample lookup:\n\n```markdown\nUser: \"Update rankings for our hero KWs\"\n\nStep 1: Check CLAUDE.md → Found \"Hero Keywords (Priority 1)\" section\nStep 2: Extract keyword list from hot cache\nStep 3: Execute ranking check\nStep 4: Update both CLAUDE.md and memory\u002Fkeywords\u002Fhistorical-rankings.csv\n```\n\n### 5. Promotion & Demotion Logic\n\n> **Reference**: See [references\u002Fpromotion-demotion-rules.md](.\u002Freferences\u002Fpromotion-demotion-rules.md) for detailed promotion\u002Fdemotion triggers (keywords, competitors, metrics, campaigns) and the action procedures for each.\n\n### 6. Update Triggers, Archive Management & Cross-Skill Integration\n\n> **Reference**: See [references\u002Fupdate-triggers-integration.md](.\u002Freferences\u002Fupdate-triggers-integration.md) for the complete update procedures after ranking checks, competitor analyses, audits, and reports; monthly\u002Fquarterly 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).\n\n## Validation Checkpoints\n\n### Structure Validation\n- [ ] CLAUDE.md exists and is under 150 lines (aim for ~100)\n- [ ] memory\u002F directory structure matches template\n- [ ] glossary.md exists and is populated with project basics\n- [ ] All historical data files include timestamps in filename or metadata\n\n### Content Validation\n- [ ] CLAUDE.md \"Last Updated\" date is current\n- [ ] Every keyword in hot cache has current rank, target rank, and status\n- [ ] Every competitor has domain authority and position assessment\n- [ ] Every active campaign has status percentage and expected completion date\n- [ ] Key Metrics Snapshot shows \"Previous\" values for comparison\n\n### Lookup Validation\n- [ ] Test lookup flow: reference a term → verify it finds it in correct layer\n- [ ] Test promotion: manually promote item → verify it appears in CLAUDE.md\n- [ ] Test demotion: manually archive item → verify removed from CLAUDE.md\n- [ ] Glossary contains all custom segments and shorthand used in CLAUDE.md\n\n### Update Validation\n- [ ] After ranking check, historical-rankings.csv has new row with today's date\n- [ ] After competitor analysis, analysis-history\u002F has dated file\n- [ ] After audit, top action items appear in CLAUDE.md priorities\n- [ ] After monthly report, metrics snapshot reflects new data\n\n## Examples\n\n> **Reference**: See [references\u002Fexamples.md](.\u002Freferences\u002Fexamples.md) for three complete examples: (1) updating hero keyword rankings with memory refresh, (2) glossary lookup flow, and (3) initializing memory for a new e-commerce project.\n\n## Advanced Features\n\n### Smart Context Loading\n\n```\nLoad full context for [campaign name]\n```\n\nRetrieves hot cache + all cold storage files related to campaign.\n\n### Memory Health Check\n\n```\nRun memory health check\n```\n\nAudits memory structure: finds orphaned files, missing timestamps, stale hot cache items, broken references.\n\n### Bulk Promotion\u002FDemotion\n\n```\nPromote all keywords ranking in top 10 to hot cache\n```\n\n```\nDemote all completed campaigns from Q3 2024\n```\n\n### Memory Snapshot\n\n```\nCreate memory snapshot for [date\u002Fmilestone]\n```\n\nTakes point-in-time copy of entire memory structure for major milestones (site launches, algorithm updates, etc.).\n\n### Cross-Project Memory\n\n```\nCompare memory with [other project name]\n```\n\nIdentifies keyword overlaps, competitor intersections, and strategy similarities across multiple projects.\n\n## Practical Limitations\n\n- **Concurrent access**: If multiple Claude sessions update memory simultaneously, later writes may overwrite earlier ones. Mitigate by using timestamped filenames for audit reports rather than overwriting a single file.\n- **Cold storage retrieval**: Files in `memory\u002F` subdirectories are only loaded when explicitly requested. They do not appear in Claude's context automatically. The hot cache (`CLAUDE.md`) is the primary cross-session mechanism.\n- **CLAUDE.md size**: The hot cache should stay concise (\u003C200 lines). If it grows too large, archive older metrics to cold storage.\n- **Data freshness**: Memory reflects the last time each skill was run. Stale data (>90 days) should be flagged for refresh.\n\n## Tips for Success\n\n1. **Keep hot cache lean** - CLAUDE.md should never exceed 150 lines. If it grows larger, aggressively demote.\n2. **Date everything** - Every file in cold storage should have YYYY-MM-DD in filename or prominent metadata.\n3. **Update after every significant action** - Don't let memory drift from reality. Update immediately after ranking checks, audits, or reports.\n4. **Use glossary liberally** - If you find yourself explaining a term twice, add it to glossary.\n5. **Review hot cache weekly** - Quick scan to ensure everything there is still relevant and active.\n6. **Automate where possible** - If ~~SEO tool or ~~search console connected, set up automatic updates to historical-rankings.csv.\n7. **Archive aggressively** - Better to have data in cold storage and not need it than clutter hot cache.\n8. **Link between layers** - CLAUDE.md should always reference where detailed data lives (\"Full data: memory\u002Fkeywords\u002F\").\n9. **Timestamp changes** - When updating CLAUDE.md, always update \"Last Updated\" date.\n10. **Use memory for continuity** - If you switch between different analysis sessions, memory ensures nothing is forgotten.\n\n## Reference Materials\n\n- [CORE-EEAT Content Benchmark](..\u002F..\u002Freferences\u002Fcore-eeat-benchmark.md) — Content quality scoring stored in memory\n- [CITE Domain Rating](..\u002F..\u002Freferences\u002Fcite-domain-rating.md) — Domain authority scoring stored in memory\n\n## Related Skills\n\n- [rank-tracker](..\u002F..\u002Fmonitor\u002Frank-tracker\u002F) — Provides ranking data to update memory\n- [competitor-analysis](..\u002F..\u002Fresearch\u002Fcompetitor-analysis\u002F) — Generates competitor reports for storage\n- [keyword-research](..\u002F..\u002Fresearch\u002Fkeyword-research\u002F) — Discovers keywords to add to memory\n- [performance-reporter](..\u002F..\u002Fmonitor\u002Fperformance-reporter\u002F) — Creates reports that trigger memory updates\n- [content-gap-analysis](..\u002F..\u002Fresearch\u002Fcontent-gap-analysis\u002F) — Identifies optimization priorities for hot cache\n- [seo-content-writer](..\u002F..\u002Fbuild\u002Fseo-content-writer\u002F) — Logs published content to memory calendar\n- [content-quality-auditor](..\u002Fcontent-quality-auditor\u002F) — Content audit results stored in memory for tracking\n- [domain-authority-auditor](..\u002Fdomain-authority-auditor\u002F) — CITE domain audit results stored in memory for tracking\n- [entity-optimizer](..\u002Fentity-optimizer\u002F) — Store entity audit results for tracking over time\n",{"name":5,"license":15,"version":24,"homepage":25,"metadata":26,"description":7,"compatibility":55},"4.0.0","https:\u002F\u002Fgithub.com\u002Faaron-he-zhu\u002Fseo-geo-claude-skills",{"tags":27,"author":43,"version":24,"triggers":44,"geo-relevance":54},[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"seo","geo","project memory","context management","campaign tracking","data persistence","keyword tracking","project context","context-memory","project-memory","seo-tracking","campaign-tracking","session-context","hot-cache","project-continuity","aaron-he-zhu",[45,46,47,48,49,50,35,51,52,53],"remember project context","save SEO data","track campaign progress","store keyword data","manage project memory","save progress","remember this for next time","save my keyword data","keep track of this campaign","low","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.","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fmemory-management",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill memory-management",{"tool":71,"command":72},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill memory-management",{"tool":74,"command":75},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill memory-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmemory-management\u002FSKILL.md",true,[79,85,89,93,97],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fexamples.md","REFERENCE","参考文档",4442,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmemory-management\u002Freferences\u002Fexamples.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fglossary-template.md",1725,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmemory-management\u002Freferences\u002Fglossary-template.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fhot-cache-template.md",2816,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmemory-management\u002Freferences\u002Fhot-cache-template.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fpromotion-demotion-rules.md",1700,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmemory-management\u002Freferences\u002Fpromotion-demotion-rules.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fupdate-triggers-integration.md",3567,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmemory-management\u002Freferences\u002Fupdate-triggers-integration.md",[102,110,117,124,131,139],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]