azoth-sync

Execute Azoth's /sync workflow via Codex using command.yaml and sync.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide Codex-driven access to Azoth's /sync workflow.

Core Features & Use Cases

  • Establishes a Codex entrypoint for Azoth's /sync workflow triggered via /skills or $azoth-sync.
  • Reads the authoritative contract at commands/sync/command.yaml and the body at .claude/commands/sync.md to ensure faithful execution.
  • Preserves the command's agent binding (agent: orchestrator) and azoth_effect: write constraints across prompts.

Quick Start

To activate, call the azoth-sync skill in Codex with your /sync request.

Frequently Asked Questions about azoth-sync

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

FAQPage Schema
How do I trigger Azoth sync workflows from Codex?

Azoth sync workflows can be triggered from Codex by calling the azoth-sync skill or using the $azoth-sync command to initiate the /sync request within your automation scenario.

What is the authoritative contract for executing Azoth sync commands?

The Azoth sync command enforces its execution contract by referencing commands/sync/command.yaml as the source of truth and reading the body from .claude/commands/sync.md to ensure faithful execution.

How do I preserve agent binding and write constraints during Codex command integration?

Codex command integration preserves agent binding (agent: orchestrator) and azoth_effect: write constraints across prompts by strictly referencing the authoritative command.yaml contract during the sync execution.

Can I use Codex skills to automate real-world Azoth /sync scenarios?

Yes, Codex skills can automate real-world Azoth /sync scenarios by providing a Codex-driven entrypoint that initiates the command surface interactions for your workflow automation.

Does Azoth sync require any dependencies to run in Codex?

Azoth sync operates with no external dependencies, relying solely on its internal command.yaml contract and sync.md body to execute the Codex-driven workflow.

Why is my Azoth /sync workflow not preserving write constraints across prompts?

Azoth /sync may fail to preserve azoth_effect: write constraints if the execution deviates from the authoritative commands/sync/command.yaml contract or the .claude/commands/sync.md body.