cursor-memory-curatorlisted

Audit, review, clean up, and prune Cursor durable context. Use when the user asks about Cursor rules, .cursor/rules, .cursorrules, User Rules, Team Rules, Cursor memory-bank artifacts, stale or noisy persistent context, rule conflicts, sensitive rule contents, or why Cursor keeps forgetting or using old guidance. Do not use for Codex memory cleanup, ordinary repo docs cleanup, generic prompt engineering, or direct implementation work without Cursor persistent context.
stark-ai-de/agent-skills · ★ 5 · AI & Automation · score 80

Install: claude install-skill stark-ai-de/agent-skills

# Cursor Memory Curator ## Goal Audit Cursor durable context as user-owned agent state: expose stale, unsafe, duplicated, ignored, conflicting, or misplaced rules; propose better destinations; and route review, planning, persistence, and cleanup through one explicit contract. Keep the subject scoped to Cursor Project Rules, legacy `.cursorrules`, `AGENTS.md`, User Rules, Team Rules, and user-maintained Cursor memory-bank artifacts. Do not treat this as a Codex memory curator. ## When to use - Use for review, placement, planning, or cleanup of the Cursor durable surfaces named in the description. - Use when those surfaces are stale, conflicting, sensitive, ignored, over-broad, or causing Cursor to forget or reuse old guidance. ## When not to use - Do not use for Codex memory, ordinary docs, or generic prompt work without Cursor durable context. - Keep review requests read-only. Keep User/Team Rules manual unless a documented file-backed artifact or explicitly approved export path is in scope. ## Workflow selection Always expose these workflows in this order. `plan-run-cleanup-file` is always first and Recommended: | Workflow | Delivery | Result | | ------------------------------------- | ------------------------------------ | ---------------------------------------------------------------------------------------- | | `plan-run-cle