memory-manager

What This Skill Does

The Memory Manager is an intelligent session-end utility designed to streamline documentation for infrastructure and project management. It acts as an automated audit trail, capturing critical changes to your servers, services, and repository states while intelligently filtering out transient noise such as debugging steps or temporary test files. By maintaining a structured hierarchy of logs (Daily Logs, MEMORY.md, TOOLS.md, and PROJECTS.md), it ensures that you always have a reliable reference point for past architecture decisions, deployment configurations, and active integrations without suffering from context bloat.

Installation

To integrate the Memory Manager into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/jpj069/jpj-memory-manager

Once installed, the agent will monitor your session context and automatically prompt to update documentation when infrastructure or project-level changes are detected.

Use Cases

• Infrastructure Auditing: Keep track of server migrations, Nginx configuration changes, and Docker service deployments across multiple sessions.
• Project Lifecycle Tracking: Log status transitions such as moving a feature from a 'Prototype' stage to 'Production' as defined by your internal project schemas.
• Credential & Tool Management: Automatically index new API keys, SSH configurations, and tool integrations in a centralized, secure-friendly location for easy future retrieval.
• Architectural Documentation: Document high-level design decisions and deprecated system patterns to ensure team continuity.

Example Prompts

1. "I've finished deploying the new API gateway to the production server. Please run the memory-manager to document the deployment and the updated environment variables."
2. "We've officially moved the legacy reporting system to cold storage and archived the repository. Please update MEMORY.md and PROJECTS.md accordingly."
3. "Please scan this session, I've just integrated the Stripe API and configured a new cron job for nightly data backups."

Tips & Limitations

• Be Concise: The Memory Manager works best when you provide clear, concise summaries of your actions. Avoid dumping raw logs into the agent's context.
• Selective Triggers: The skill triggers only on significant structural changes. If you are doing minor code cleanup, the system will filter these out to keep your documentation clean.
• Refer to Schemas: Ensure your PROJECTS.md follows the schema outlined in the references/projects-guide.md file for full compatibility.
• Limitation: The agent is not a replacement for version control (git). It is intended as a high-level knowledge base and infrastructure registry rather than a commit log.