From memory-bank
Re-scope an existing global memory to the current project in the GCP Memory Bank. Use when a memory that was saved globally should be narrowed to only apply to the current workspace.
How this skill is triggered — by the user, by Claude, or both
Slash command
/memory-bank:memories-set-project-scopeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Re-scope a global memory to the current project.
Re-scope a global memory to the current project.
/memories-list first to find it.ls -d ~/.claude/scripts/memory-bank ~/.gemini/config/plugins/memory-bank/scripts ~/.claude/plugins/cache/*/memory-bank/*/scripts 2>/dev/null
Use the first that exists in the order listed above, not the order ls
prints — it sorts. Call it <SCRIPTS>.python3 <SCRIPTS>/set_project_scope.py "<memory_id>"
This fetches the fact, creates a project-scoped copy, and deletes the global original.✓ Re-scoped: <old_id> → <new_id> (project scope)npx claudepluginhub mlarkin00/plugins --plugin memory-bankGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.