aiskillstore/marketplace / skills/aaron-he-zhu/memory-management
memory-management
VerifiedUse when the user asks to "remember project context", review saved findings, initialize runtime memory, archive stale work, reconcile notes, or erase a subject; manages authorized HOT/WARM/COLD working memory across all disciplines while preserving registry event ownership and privacy controls. Not for changing canonical registry facts - route those through the owning registry. 项目记忆/跨会话
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.5 KB |
| references/consolidation-pass.md | markdown | 1.9 KB |
| references/examples.md | markdown | 4.2 KB |
| references/gdpr-purge-log-template.md | markdown | 2.5 KB |
| references/glossary-template.md | markdown | 1.3 KB |
| references/hot-cache-template.md | markdown | 2.4 KB |
| references/promotion-demotion-rules.md | markdown | 1.5 KB |
| references/update-triggers-integration.md | markdown | 3.2 KB |
| skill-report.json | config | 43.2 KB |
references/hot-cache-template.md
View on GitHub# Hot cache template (`memory/hot-cache.md`)
Use this template when initializing memory for a new SEO project. The HOT tier is the single file `memory/hot-cache.md` (auto-loaded every session via the SessionStart hook, hard limit 80 lines / 25KB). Do NOT place this content in the project root's CLAUDE.md.
```markdown
# [Project Name] - SEO Memory (hot cache)
**Last Updated**: [Date] | **Project Status**: [Active/Maintenance/Growth]
## Active Target Keywords (Top 10-20)
### Hero Keywords (Priority 1)
| Keyword | Current Rank | Target Rank | Volume | Status |
|---------|--------------|-------------|--------|--------|
| [keyword 1] | #[X] | #[Y] | [vol] | [tracking/optimizing/achieved] |
### Secondary Keywords (Priority 2)
| Keyword | Current Rank | Target Rank | Volume | Status |
|---------|--------------|-------------|--------|--------|
| [keyword 1] | #[X] | #[Y] | [vol] | [tracking/optimizing/achieved] |
_Full keyword research: memory/research/keywords/_
## Primary Competitors (Top 3-5)
1. **[Competitor 1]** (DA: [X]) — Strengths: [brief] | Position: [ahead/behind/competitive]
2. **[Competitor 2]** (DA: [X]) — Strengths: [brief] | Position: [ahead/behind/competitive]
_Detailed analyses: memory/research/competitors/_
## Current Optimization Priorities
1. **[Priority 1]** — Status: [not started/in progress/completed] | Impact: [H/M/L] | Deadline: [date]
2. **[Priority 2]** — Status: [not started/in progress/completed] | Impact: [H/M/L] | Deadline: [date]
## Key Metrics Snapshot
**Last Metrics Update**: [Date]
| Metric | Current | Previous | Change | Target |
|--------|---------|----------|--------|--------|
| Organic Traffic | [X] | [X] | [+/-X%] | [target] |
| Avg. Position | [X] | [X] | [+/-X] | [target] |
| Page 1 Rankings | [X] | [X] | [+/-X] | [target] |
| Domain Authority | [X] | [X] | [+/-X] | [target] |
| CITE Score | [X] | [X] | [+/-X] | [target] |
| Last Audit Score | [score]/100 ([rating]) — [date] | [page] |
| Total Backlinks | [X] | [X] | [+/-X%] | [target] |
_Historical data: memory/monitoring/reports/ and memory/monitoring/rank-history/_
## Active Campaigns
### [Campaign Name 1]
- **Duration**: [Start] - [End] | **Goal**: [goal] | **Status**: [planning/active/completed] | **Progress**: [X]%
- **Key activities**: [brief list]
_Campaign plans and archives: memory/content/calendar/_
## Quick Reference Notes
- [Important note 1]
- [Important note 2]
_For project terminology, see: memory/glossary.md_
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |