SEO Campaign Memory Manager
v7.2.0SEO campaign memory manager: persist keyword research, audit results, and project context across Claude Code sessions with hot/warm/cold storage tiers. Part...
⭐ 1· 1.8k·21 current·23 all-time
byAaron Zhu@aaron-he-zhu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (SEO campaign memory manager) align with the instructions: creating and maintaining a hot cache (CLAUDE.md), WARM files, COLD archives, promotion/demotion rules, and wiki indexes. There are no unrelated environment variables, binaries, or install steps requested that would contradict the stated purpose.
Instruction Scope
The SKILL.md instructs the agent to read, create, update, and archive files under a local memory/ directory (CLAUDE.md, memory/wiki/, memory/research/, etc.). Many actions are automatic (SessionStart loads hot cache; PostToolUse auto-refreshes the wiki index without user confirmation). Automatic writes and rebuilds of derived artifacts (wiki/index) can modify workspace files without an explicit confirmation prompt, which may be surprising and could overwrite or surface sensitive content if memory/ contains unrelated data.
Install Mechanism
Instruction-only skill with no install spec, no download URLs, and no code files — minimal disk footprint and low install risk.
Credentials
No environment variables, credentials, or external tokens are requested. The SKILL.md mentions optional SEO tool integrations (MCP network access) but does not require keys. Requested access (reading/writing files under memory/) is proportional to the skill's purpose.
Persistence & Privilege
always:false (normal). The skill expects to be invoked by SessionStart and PostToolUse hooks and to persist state in workspace files. This is expected for a memory manager, but combined with automatic index rebuilds and cross-skill aggregation it increases the chance of unexpected modifications or cross-project data aggregation if memory/ is not isolated per project.
Assessment
This skill appears to do what it says: maintain local SEO memory files and a hot/warm/cold tier. Before installing or enabling it: 1) Verify the repository/source (the listed GitHub homepage is a helpful starting point). 2) Back up any existing memory/ directory in your workspace — the skill will create, update, and archive files there and may auto-rebuild indexes without asking. 3) If you manage multiple projects in the same workspace, ensure memory/ is project-isolated (use memory/wiki/<project>/) to avoid accidental cross-project aggregation or leakage. 4) If you prefer explicit control, ask the skill author (or edit SKILL.md locally) to require user confirmation before automatic PostToolUse/SessionStart writes (especially index rebuilds or archival). 5) Only enable optional external SEO integrations if you trust the provider and supply credentials intentionally (the skill itself does not request any secrets). If you want a stricter assessment, provide the repository code or an execution trace showing which hooks are registered and exactly what file-system APIs will be invoked.Like a lobster shell, security has layers — review code before you run it.
campaign-managementvk97csed2eatmrma22arx6y965984a29clatestvk97csed2eatmrma22arx6y965984a29cproject-memoryvk97csed2eatmrma22arx6y965984a29cseovk97csed2eatmrma22arx6y965984a29csession-contextvk97csed2eatmrma22arx6y965984a29c
License
MIT-0
Free to use, modify, and redistribute. No attribution required.