Individual skill

using-sync

Use when an Agent needs to synchronize LWC Wiki stores across SSH hosts, resume or abort an interrupted Sync session, or resolve semantic Sync conflicts safely.

integrations/codex-lwc/skills/using-sync/SKILL.md

Read pinned source

Source commit e1be6ab30e83947e4b0dba97ba910acfe3bd9821

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 72
Repository last updated: Oct 7, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-memory-system Repository topic
ai-agents Repository topic
ai-agents-cli Repository topic
context-engineering Repository topic
knowledge-bases Repository topic
local-first-ai Repository topic
persistent-memory-tool Repository topic
proactive-memory Repository topic
claude-code Repository topic
codex Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 10,148 bytes
SKILL.mdcore · 10,148 bytes
SKILL.mdcore · 10,148 bytes
SKILL.mdcore · 10,148 bytes
agents/openai.yamlasset · 206 bytes

Read excerpt


# Using LWC Sync

Run Sync through the audited CLI only:

```text
lwc sync HOST [ABS_DIRECTORY] --mode merge|pull|push
```

Every start, resume, resolve, abort, pull, push, or merge can publish or change
durable data. Before the first execution in a bounded workflow, present a safety
notice containing the exact command, target host, absolute directory, scope, mode, affected stores, impact, risks, recovery path, and reversibility.
An explicit user instruction that already names or unambiguously accepts these facts is authorization; do not ask the human to repeat it.

One authorization covers the bounded workflow while its host, directory, scope,