ejentum-memory

Generate structured memory-sharpening workflows for implicit conversation changes.

3|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/ejentum/integrations --skill ejentum-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ejentum-memory
Source: https://github.com/ejentum/integrations/tree/main/claude-code/skills/ejentum-memory
Command: npx skills add https://github.com/ejentum/integrations --skill ejentum-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you reliably notice when a conversation has shifted in meaning, intent, or emotional state across turns—especially when changes are implicit rather than explicitly corrected.

Core Features & Use Cases

  • Multi-turn perceptual tracking: Detects tone shifts, delivery changes, omissions, and subtle pivots in state over time.
  • State-updating guidance: Produces structured observation procedures that help you update your internal model instead of clinging to stale context.
  • Perception-first workflow: Forces a two-pass approach (observe, then sharpen) to reduce projection and improve verification.
  • Use case: If a user’s earlier plan silently changes direction (e.g., streaming vs. batch priorities) or their stated mood conflicts with their communication style, use this to adjust what you believe is currently true.

Quick Start

Call this memory Skill for your next turn by describing the three most important changes you noticed (content change, delivery change, and what’s absent) and asking it to sharpen your perception.

Frequently Asked Questions about ejentum-memory

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

FAQPage Schema
How do I detect subtle tone shifts and emotional incongruence in multi-turn conversations?

To detect subtle tone shifts and emotional incongruence in multi-turn conversations, you can use a structured memory-sharpening workflow that applies a perception-first protocol to identify implicit changes. This method requires providing a raw observational query to generate a structured observation procedure.

What is implicit state tracking and when do I need it for conversation intelligence?

Implicit state tracking is a conversation intelligence mechanism that identifies when meaning, intent, or emotional state shifts across turns without explicit correction. You need it when what changed matters more than what was said, such as detecting omissions or stale-state conditions.

How do I update my internal model when a user's plan implicitly pivots across turns?

To update your internal model when a user's plan implicitly pivots, you generate a state-updating observation procedure by describing the content change, delivery change, and what is absent. This structured approach reduces projection and helps you adjust what you believe is currently true.

What's the best way to avoid clinging to stale context during multi-turn dialogue?

The best way to avoid clinging to stale context during multi-turn dialogue is to apply a two-pass perception-first workflow that forces you to observe first and then sharpen your perception. This reduces projection and improves verification of implicit plan pivots or tone shifts.

Does this multi-turn perception approach require any specific dependencies or components?

No specific dependencies or components are required to use this multi-turn perception approach. You only need to provide a raw observational query describing the changes you noticed and use the memory mode call while following the perception-first protocol.

When should I not use a memory-sharpening workflow for state tracking?

You should not use a memory-sharpening workflow for state tracking when changes in the conversation are explicitly corrected by the user, as this tool is specifically designed to detect implicit changes like subtle delivery shifts, omissions, and emotional incongruence where what changed matters more than what was said.