memory-managementPersist SEO/GEO campaign context across Claude sessions with automatic hot-list, active work, and archive tiers. 项目记忆/跨会话
Install via ClawdBot CLI:
clawdbot install aaron-he-zhu/memory-managementGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://skills.sh/aaron-he-zhu/seo-geo-claude-skillsAudited Apr 17, 2026 · audit v1.0
Generated Mar 1, 2026
A digital marketing agency starts a new SEO campaign for a client in the e-commerce sector. They use this skill to initialize memory structure, storing target keywords, competitor domains, and performance metrics in the hot cache and cold storage, ensuring all team members have consistent project context from day one.
An in-house SEO team at a SaaS company tracks an ongoing content optimization campaign. They update memory after monthly ranking checks, promoting frequently referenced keywords to the hot cache and archiving stale data to maintain efficient context retrieval and monitor progress over time.
A freelance SEO consultant revisits a past project for a local business client after six months. They query stored context to recall hero keywords, competitor analysis findings, and campaign status from cold storage, enabling quick resumption without re-researching.
A large enterprise with multiple SEO teams uses this skill to manage project-specific terminology and abbreviations. They add new terms to the glossary as campaigns evolve, ensuring all members understand internal jargon and reducing miscommunication during audits and reports.
An SEO agency conducts a quarterly review for a long-term client in the travel industry. They archive data not referenced in over 30 days from the hot cache to cold storage, optimizing memory performance and keeping the active context focused on current priorities.
Agencies managing multiple client SEO campaigns use this skill to maintain separate memory structures per project, tracking keywords, competitors, and metrics. It enhances efficiency by reducing context-switching and ensuring data persistence across team handoffs, supporting retainer-based or project-based revenue models.
Companies with dedicated SEO teams integrate this skill to streamline internal project management, storing campaign progress and historical data. It improves collaboration by providing a centralized memory system, aiding in reporting and strategy adjustments, typically funded through departmental budgets.
Independent consultants leverage this skill to manage memory for diverse clients across industries, from setup to ongoing tracking. It helps organize project contexts efficiently, enabling quick recalls and professional updates, often charging hourly rates or fixed project fees.
💬 Integration Tip
Connect this skill with SEO tools like rank trackers or analytics platforms to automate data population; for manual setups, prompt users to provide keywords, competitors, and metrics during initialization.
Scored Apr 19, 2026
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Transform AI agents from task-followers into proactive partners with memory architecture, reverse prompting, and self-healing patterns. Lightweight version f...
Persistent memory for AI agents to store facts, learn from actions, recall information, and track entities across sessions.
Prefer `skillhub` for skill discovery/install/update, then fallback to `clawhub` when unavailable or no match. Use when users ask about skills, 插件, or capabi...
Search and discover OpenClaw skills from various sources. Use when: user wants to find available skills, search for specific functionality, or discover new s...
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.