CRUX-Compress: Skill for Cursor

CRUX Skill: Memory Reference Tracker

Manages per-memory reference tracking files (.refs.yml) in the configured trackingDir. Tracker files are the single source of truth for how often, how recently, and by whom a memory was referenced. Memory frontmatter stays clean — it stores what a memory is, not how often it is used.

Config keys and defaults: see .cursor/skills/_memory-shared.md#config-reference and .crux/crux-memories.json (authoritative). This skill reads keys under cruxMemories.referenceTracking.* plus cruxMemories.unitOfWork (which determines the key name used in recent_references[] source entries).

Operations

1. Record Reference

When: An agent's output is influenced by a memory.

Steps:

1. Read config from .crux/crux-memories.json. If referenceTracking.enabled is false, skip all tracking.
2. Determine the memory slug from the memory filename (strip .memory.md or .memory.crux.md suffix and any path prefix).
3. Look for {trackingDir}/{slug}.refs.yml.
   • If it does not exist — create it (see Lazy Creation).
   • If it exists — read and update it.
4. Increment the references counter by 1.
5. Set last_referenced to today's date (YYYY-MM-DD).
6. Update recent_references (see Manage Recent References).
7. Sync strength from the memory file's frontmatter into the tracker (see Sync Strength).
8. Write the updated tracker file.
9. Check whether references now exceeds promotionToRuleThreshold (see Promotion Flag).

2. Indicate in Output

When: referenceTracking.indicateInOutput is true and an agent's output is influenced by a memory.

Instruction to agents: When your response is influenced by a loaded memory, include the configured indicator in your output. The default format is [memory:{title}], where {title} is replaced with the memory's title frontmatter field.

Example with default format: