proactive-memory-judgment

Evaluates person-related conversation cues to propose, defer, or abstain from memory proposals.

2.9k|733|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/zts212653/clowder-ai --skill proactive-memory-judgment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proactive-memory-judgment
Source: https://github.com/zts212653/clowder-ai/tree/main/cat-cafe-skills/proactive-memory-judgment
Command: npx skills add https://github.com/zts212653/clowder-ai --skill proactive-memory-judgment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When an AI assistant encounters mentions of people in conversation, it must decide whether that information deserves to become persistent memory. Without a judgment policy, agents either silently store unverified personal facts or miss genuinely valuable continuity. This Skill provides a five-gate decision framework that routes each person-related cue to exactly one outcome: a rejectable proposal, a content-free deferral receipt, or an enum-only abstention.

Core Features & Use Cases

  • Five-Gate Semantic Judgment: Sequentially checks qualification (continuity value), typed evidence, timing, authorization, and de-escalation before any memory action.
  • Three Controlled Outcomes: Produces an F276 rejectable proposal, a known-person deferred delta receipt, or an enum-only abstention record — never silent writes to canonical memory.
  • Typed Evidence Discipline: Enforces source roles (owner message, third-party quote, agent inference) so evidence only supports the fields it can actually prove.
  • Use Case: During a chat, the owner mentions a colleague's new role. The Skill checks continuity value and evidence, then issues one rejectable proposal card instead of silently storing the fact, letting the owner approve exact items first.

Quick Start

Ask the agent to evaluate whether the person mentioned in this conversation should become a memory proposal, a deferred delta, or an abstention.

Frequently Asked Questions about proactive-memory-judgment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide when an AI agent should save person memories?

Use a sequential gate policy: check the person has continuity value, verify typed evidence supports each field, confirm natural timing, and require owner authorization. Only then create a rejectable proposal rather than writing memory silently.

How to handle person mentions without enough evidence in chat agents?

Record an enum-only abstention with a reason code such as insufficient_owner_evidence instead of guessing or filling gaps. Never fabricate facts the owner did not state, and never let agent inference materialize into stored memory.

What is the difference between deferring and abstaining a memory proposal?

Deferral applies when evidence is solid and the person is already registered but interrupting now is inappropriate; it stores only routing coordinates. Abstention applies when the cue fails a judgment gate and records only a reason code with no content.

Can agent inferences about people be stored as memory facts?

No. Agent inference must never materialize into canonical memory. Only owner messages can support reported facts or user assessments, and third-party quotes must remain labeled as quoted third-party content.

When should repeated mentions of a person trigger memory creation?

Repetition alone is not a trigger. A single qualified cue with continuity value is enough to enter judgment, while frequency nudges only indicate cross-thread occurrence and never prove importance or decide the memory lane.