← Back to Skills Marketplace
Memory Sync Protocol
by
markisadesigner1992-eng
· GitHub ↗
· v1.0.0
565
Downloads
2
Stars
5
Active Installs
1
Versions
Install in OpenClaw
/install memory-sync-protocol
Description
Synchronize durable behavior or preference changes across TOOLS.md, MEMORY.md, AGENTS.md, and memory/YYYY-MM-DD.md with one consistent workflow. Use when use...
README (SKILL.md)
Memory Sync Protocol
When this skill is triggered, execute the following sequence strictly.
1) Classify the change
- Execution detail (tool/profile/path/routing trigger) →
TOOLS.md - Long-term stable preference (high-level) →
MEMORY.md - Governance/process rule (how to maintain) →
AGENTS.md - Event log / audit trail (what changed today) →
memory/YYYY-MM-DD.md
2) Update files with minimal duplication
- Write detailed routing/trigger logic in
TOOLS.md. - Write only high-level summary in
MEMORY.md. - Avoid copying large sections between files.
- If adding a new policy, also add short maintenance note in
AGENTS.md.
3) Append daily log
- In
memory/YYYY-MM-DD.md, record:- what changed,
- why,
- affected files.
4) Git discipline
- Before major rewrites: create a backup commit.
- After updates: commit with semantic message, e.g.
docs(routing): ...docs(memory): ...chore(memory): ...
5) Reply format
Return a concise sync report:
- Updated files
- Key rules added/changed
- Commit hash/message
Guardrails
- Do not store sensitive secrets in MEMORY/TOOLS unless user explicitly asks.
- Do not bloat MEMORY with skill inventories or transient logs.
- Prefer TOOLS for concrete calling rules; MEMORY for durable preference only.
Usage Guidance
This skill is coherent for its stated job, but it assumes the agent can write repository files and run git. Before enabling or invoking it: (1) make sure the files it edits are in a repository you control and that you have backups; (2) require a human review step for diffs/commits (don't allow blind pushes); (3) do not request the skill to sync content that contains secrets or credentials; (4) confirm the environment has git and that file permissions are intentionally granted; (5) consider testing in a sandbox repo first so you can observe the exact edits and commit messages it produces.
Capability Analysis
Type: OpenClaw Skill
Name: memory-sync-protocol
Version: 1.0.0
The memory-sync-protocol skill is a documentation management workflow designed to synchronize agent preferences and rules across standard files like MEMORY.md and TOOLS.md. The instructions in SKILL.md focus on organizational consistency, Git versioning, and basic guardrails against storing secrets, with no evidence of malicious intent or high-risk behaviors.
Capability Assessment
Purpose & Capability
The name/description (synchronizing TOOLS.md, MEMORY.md, AGENTS.md, daily memory logs) matches the SKILL.md actions. It does not request unrelated env vars, binaries, or config paths. One implicit requirement: the agent must have read/write access to the repository files and git available to follow the 'Git discipline' steps.
Instruction Scope
The SKILL.md is narrowly focused on classifying changes, editing the specified files, appending a daily log, and committing. It does not instruct reading unrelated system files or sending data externally. However, it gives the agent authority to modify repository files that govern agent/tool behavior (AGENTS.md, TOOLS.md), and it relies on the agent to avoid storing secrets (a guardrail but not an enforcement).
Install Mechanism
Instruction-only skill with no install spec and no code files; nothing will be downloaded or written at install time by the skill itself.
Credentials
The skill requests no environment variables or credentials. That is proportional. Caveat: the guardrail 'Do not store sensitive secrets...' depends on the agent following instructions—if users ask the skill to sync content that includes secrets, those secrets could be written into the repo files unless the user or agent blocks it.
Persistence & Privilege
The skill is not 'always: true' and doesn't request elevated platform privileges, but it is designed to edit global governance and tooling files (AGENTS.md, TOOLS.md). Those edits can change future agent behavior—this is consistent with its purpose but creates a meaningful persistence/privilege surface that the user should control (e.g., review commits).
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install memory-sync-protocol - After installation, invoke the skill by name or use
/memory-sync-protocol - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of memory-sync-protocol skill.
- Provides a consistent workflow for synchronizing behavior or preference changes across TOOLS.md, MEMORY.md, AGENTS.md, and memory log files.
- Outlines file responsibilities, update steps, daily logging, and commit discipline.
- Includes guardrails to avoid duplication, sensitive data exposure, and MEMORY bloat.
- Triggered when users request to remember, update, or sync rules, preferences, or conventions across files.
Metadata
Frequently Asked Questions
What is Memory Sync Protocol?
Synchronize durable behavior or preference changes across TOOLS.md, MEMORY.md, AGENTS.md, and memory/YYYY-MM-DD.md with one consistent workflow. Use when use... It is an AI Agent Skill for Claude Code / OpenClaw, with 565 downloads so far.
How do I install Memory Sync Protocol?
Run "/install memory-sync-protocol" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Memory Sync Protocol free?
Yes, Memory Sync Protocol is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Memory Sync Protocol support?
Memory Sync Protocol is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Memory Sync Protocol?
It is built and maintained by markisadesigner1992-eng (@markisadesigner1992-eng); the current version is v1.0.0.
More Skills