update-memory

Update a persistent cross-session memory file with agent configuration and session summaries.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/javiarmesto/CIRCE-Agent-Squad-for-Microsoft-Copilot-Studio --skill update-memory-javiarmesto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-memory
Source: https://github.com/javiarmesto/CIRCE-Agent-Squad-for-Microsoft-Copilot-Studio/tree/main/.github/skills/update-memory
Command: npx skills add https://github.com/javiarmesto/CIRCE-Agent-Squad-for-Microsoft-Copilot-Studio --skill update-memory-javiarmesto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that an agent maintains a persistent cross-session memory file, capturing agent configuration, components, knowledge sources, decisions, and session summaries.

Core Features & Use Cases

  • Persistent Memory: Stores configuration, components, knowledge sources, decisions, and session summaries in a cross-session memory file.
  • Agent Operations: Invoked by other agents after significant operations like creating topics, adding knowledge sources, or editing agent settings.
  • Use Case: For an agent managing a complex workflow, this Skill keeps track of all activities and decisions, ensuring continuity across sessions.

Quick Start

Use the update-memory skill to update the memory file after a significant operation, such as creating a new topic.

Frequently Asked Questions about update-memory

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

FAQPage Schema
How do I maintain persistent cross-session memory for an agent?

To maintain persistent cross-session memory, this Skill updates a memory file with agent configuration, components, knowledge sources, decisions, and session summaries after significant operations.

When do I need to update an agent's memory file?

You need to update an agent's memory file after significant operations, such as creating new topics, adding knowledge sources, or editing agent settings, to ensure continuity across sessions.

How does cross-session memory tracking work for agent architecture?

Cross-session memory tracking works by capturing agent configuration, components, knowledge sources, and decisions into a persistent file, invoked by other agents after significant workflow operations.

What is required to start tracking agent configuration and session summaries?

Starting session tracking requires access to the agent's configuration and its designated memory file to capture and store operational continuity data across sessions.

Can I use this memory management approach for complex agent workflows?

Yes, for an agent managing a complex workflow, this memory management approach keeps track of all activities and decisions, ensuring continuity and state persistence across sessions.