Comet Memory
Use when Comet must decide whether a bounded semantic review packet contains a personal memory worth creating, updating, forgetting, or skipping.
Install
npx skills add rpamis/comet --skill comet-memorygit clone --depth 1 https://github.com/rpamis/comet.git /tmp/comet
mkdir -p ~/.claude/skills
cp -r /tmp/comet/assets/skills/comet-memory ~/.claude/skills/comet-memoryPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Comet Semantic Memory Review You are a fixed first-party memory reviewer. You only filter meaning. Do not write files, call tools, scan repositories, or modify any Skill, rule, or agent instruction. ## Input boundary Read only the Runtime-provided `comet.memory.review.v1` `MemoryReviewPacket`: configured language, project identity, workflow/change, trusted checkpoint, small user evidence, relevant memories, evidence, and budget. Do not request or infer the full conversation, logs, diff, repository contents, or hidden reasoning. ## Decision order 1. Handle explicit user requests first: “remember”, “always do this”, “change it to”, or “forget”. Explicit memory wins and cannot be overwritten by inferred behavior; preserve direct user text without translation. 2. Keep only reusable personal preferences, collaboration habits, output preferences, or verified personal experience that is not easy to rediscover from the repository. 3. Skip one-off commands, test/commit/Issue/PR summaries, activity logs, ordinary source facts, guesses, raw logs, complete diffs, complete transcripts, and content with no future value. 4. The entire `actions` collection must use one scope: all real actions must be either `global` or `project`, never a mixture; if a single scope cannot be maintained, return the one `skip`. Automatic behavior defaults to `project`; choose `global` only when the packet provides consistent successful evidence across projects. Never invent evidence or project identity.
Details
- Skill name
comet-memory- Repository
- rpamis/comet
- Path
assets/skills/comet-memory/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Comet Memory skill do?
Use when Comet must decide whether a bounded semantic review packet contains a personal memory worth creating, updating, forgetting, or skipping.
How do I install the Comet Memory skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add rpamis/comet --skill comet-memory. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Comet Memory popular?
It lives in rpamis/comet, which has 3,306 GitHub stars and 317 forks.
Related skills
Brainstorming
3.3krpamis/comet
Transforms rough ideas into fully-formed designs. Structure your brainstorming sessions and develop ideas systematically.
Dispatching Parallel Agents
3.3krpamis/comet
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Finishing a Development Branch
3.3krpamis/comet
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Comet Open
3.3krpamis/comet
Comet Phase 1: Open. Invoke with /comet-open. Explore ideas through OpenSpec, confirm requirements clarification, then create change structure (proposal + design + tasks).
Comet Hotfix
3.3krpamis/comet
Use when 用户要修复已有行为 bug,且不新增 capability、不需要完整设计;也用于恢复 hotfix workflow。
Comet Open
3.3krpamis/comet
Use when Comet 需要创建新的 OpenSpec change,或 active change 缺少 proposal/design/tasks/.comet.yaml 初始化产物。
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.