skills.rest
yiwei79
yiwei79OFFICIAL
Explore all skills by this author →
GitHub

azoth-sync-claude-memory

Replay deferred Claude memory mirroring from repo-local Azoth state.

Updated Apr 8, 2026
Search Tags:#automation#claude#replay#memory-sync#azoth
One-click install
npx skills add https://github.com/yiwei79/azoth --skill azoth-sync-claude-memory
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azoth-sync-claude-memory
Source: https://github.com/yiwei79/azoth/tree/main/.agents/skills/azoth-sync-claude-memory
Command: npx skills add https://github.com/yiwei79/azoth --skill azoth-sync-claude-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replays deferred Claude memory mirroring from the repo-local Azoth state to restore consistency after Codex closeouts or restricted host write access.

Core Features & Use Cases

  • Replays deferred Claude memory mirroring from the repo-local Azoth state to ensure memory parity across environments.
  • Detects pending artifacts in .azoth/claude-memory-sync-pending.json and applies them by executing the memory-sync script.
  • Reports if host write access remains blocked and guides you to obtain broader permissions while preserving repository authority.

Quick Start

Read the pending state file and run the Claude memory sync script to replay memory.

Frequently Asked Questions about azoth-sync-claude-memory

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

FAQPage Schema
How do I replay deferred Claude memory mirroring from a local repository state?▼

The Claude memory sync script replays deferred memory mirroring by reading the pending artifact in .azoth/claude-memory-sync-pending.json and executing scripts/sync_claude_memory.py to restore parity.

When do I need to restore Claude memory parity using Azoth?▼

You need to restore Claude memory parity using Azoth after Codex closeouts or when broader host write access is granted, ensuring the local repository state remains authoritative across environments.

Why does Claude memory sync fail to update when host write access is blocked?▼

Claude memory sync fails when host write access is blocked because the script cannot execute updates, prompting the Skill to report the blockage and guide you to obtain broader permissions while preserving repository authority.

Does the Claude memory sync script require any specific dependencies or components?▼

The Claude memory sync script operates without external dependencies or components, relying solely on the repo-local .azoth/claude-memory-sync-pending.json artifact and the internal sync script to restore memory state.

What is the best way to ensure memory consistency across environments after restricted host write access?▼

The best way to ensure memory consistency is to run the Azoth memory replay process, which detects pending sync artifacts and applies them to restore parity while keeping the repository state authoritative.

Related Skills

Explore More Software Engineering Skills→
yiwei79yiwei79

orientation

Documents roadmap phases and validates changes via a six-step workflow.

Official
Advanced
withkynamwithkynam
1.1k

vc-audit-vc

Audit VC harness health across Claude/Codex parity and protocol wiring.

Community
Advanced
AesopScottAesopScott
1

role

Define and manage organizational roles with authority levels and workflow automation.

Community
Advanced
yiwei79yiwei79

autonomous-auto

Automate branch-local autonomous development planning and governance for Azoth campaigns.

Official
Advanced