Read Working Memory

nowledge-co/community/nowledge-mem-cursor-plugin/skills/read-working-memory

by nowledge-co1f4d7eb61466dbfc93ce8d7a0a806c4d4a196dd0No licenseListed Oct 9, 2026Updated Oct 9, 2026

Read the user's Working Memory briefing when current priorities, recent activity, or active focus areas matter.

Instructions onlyProductivity & Workflow
AI-generated overview

Reads the user's Working Memory briefing via the read_context_bundle MCP tool to surface current priorities and focus areas.

What it does
This skill instructs an agent to obtain the user's Working Memory briefing by calling the read_context_bundle desktop MCP tool, which returns owner identity, resolved AI Identity, active scope, active rules, Working Memory, and KFS paths. It tells the agent to reuse an existing fresh Context Bundle or working-memory block instead of re-reading, and to summarize only the parts relevant to the current task. It also suggests moving into search-memory when the task is a continuation, review, regression, release, or prior-decision question.
When to use it
Use it at session start when fresh Working Memory is not already in context, when resuming work after a break, when the user asks what they are focused on now, or when the task depends on recent priorities or active initiatives.
Requirements
Requires the read_context_bundle desktop MCP tool and access to the user's Working Memory data. Ships no scripts; instructions only.

Read Working Memory

Use read_context_bundle when the session-start hook did not already provide fresh context or when a refresh is needed. It is the supported desktop MCP briefing surface and includes owner identity, resolved AI Identity, active scope, active rules, Working Memory, and KFS paths.

When To Use

  • At session start if fresh Working Memory is not already present in the session context
  • When resuming work after a break
  • When the user asks what they are focused on now
  • When the current task clearly depends on recent priorities or active initiatives

Usage Pattern

  • If a fresh Context Bundle or <nowledge_working_memory> block is already present, reuse it instead of reading again immediately.
  • Otherwise, call read_context_bundle once near the start of the session and use its Working Memory section for the current briefing.
  • If the task is clearly a continuation, review, regression, release, or prior-decision question, move into search-memory after the briefing instead of stopping there.
  • Reuse that context mentally instead of re-reading on every turn.
  • Only refresh if the session context changed materially, the user asks, or the work has gone on long enough that a fresh briefing is clearly useful.

Summarize only the parts relevant to the current task.

Source and attribution

Source:nowledge-co/communityinnowledge-mem-cursor-plugin/skills/read-working-memoryat commit1f4d7eb

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal