coworkia-memory

Store and retrieve long-term project decisions and session histories.

Updated Nov 6, 2025
One-click install
npx skills add https://github.com/MarketingLabb/Coworkia-Agent --skill coworkia-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coworkia-memory
Source: https://github.com/MarketingLabb/Coworkia-Agent/tree/main/.github/skills/coworkia-memory
Command: npx skills add https://github.com/MarketingLabb/Coworkia-Agent --skill coworkia-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a centralized, long-term memory for the Coworkia Agent project, preserving decisions, session histories, and preferences so the agent can operate with full context across sessions.

Core Features & Use Cases

  • Context preservation: stores last-session summaries, flight plans, and key decisions to guide new activations.
  • Contextual retrieval: retrieves relevant history automatically at session start to reduce repetitive explanations.
  • Knowledge evolution: versioned notes and decisions to track how the project evolved and why changes were made.

Quick Start

Load this memory at the start of each session to ensure the agent has complete project context and historical guidance.

Frequently Asked Questions about coworkia-memory

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

FAQPage Schema
How do I preserve context and session history for a multi-agent workflow?

You can preserve context for a multi-agent workflow by using a structured memory store that saves long-term decisions, session histories, and preferences for seamless recall across activations. This ensures the agent operates with full project context.

What is long-term memory retrieval for AI agents and how does it work?

Long-term memory retrieval automatically fetches relevant history, last-session summaries, and architectural notes at the start of a new session. It uses versioned notes to track project evolution and reduce repetitive explanations during activations.

How do I load historical context at the start of an agent session?

To load historical context at the start of an agent session, initialize the memory skill during activation. This automatically retrieves pending plans, flight plans, and key decisions to guide the new session without manual input.

Can I track project decisions and knowledge evolution across multiple agent activations?

Yes, you can track project decisions and knowledge evolution by storing versioned notes and architectural decisions in a centralized memory. This records how the project evolved and why changes were made across multiple activations.

Does multi-agent memory retrieval work safely during execution?

Yes, multi-agent memory retrieval is designed for safe retrieval during execution. It satisfies requirements for a structured memory store, ensuring session histories and pending plans are accessed without disrupting the active workflow.

Why does my AI agent lose context and require repetitive explanations between sessions?

An agent loses context between sessions because it lacks a centralized long-term memory for preserving decisions and session histories. Implementing contextual retrieval at session start automatically restores full project context and eliminates repetitive explanations.