Menu

Individual skill

comet-memory

0upvotes

Use when Comet must decide whether a bounded semantic review packet contains a personal memory worth creating, updating, forgetting, or skipping.

assets/skills/comet-memory/SKILL.md

Read pinned source

Source commit 1fb0f070582714f8dd36cd01b7681a8aa0310942

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,283
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.