azoth-deliver

Name: azoth-deliver
Availability: InStock
Author: yiwei79

Execute Azoth's deliver workflow by reading command.yaml and deliver.md.

Updated Apr 8, 2026

Search Tags:#workflow #codex #orchestrator #deliver #azoth #command-reading

Ready to run

npx skills add https://github.com/yiwei79/azoth --skill azoth-deliver

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: azoth-deliver
Source: https://github.com/yiwei79/azoth/tree/main/.agents/skills/azoth-deliver
Command: npx skills add https://github.com/yiwei79/azoth --skill azoth-deliver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a Codex-visible entrypoint to run Azoth's /deliver workflow, bridging Codex commands with Azoth's execution engine and ensuring consistent workflow triggering.

Core Features & Use Cases

Codex-visible entrypoint for Azoth's /deliver workflow.
Contract-driven execution reads the command contract at commands/deliver/command.yaml and the body source at .claude/commands/deliver.md.
Workflow preservation maintains stage structure, gate rules, evaluation rules, and the azoth_effect: write contract, and supports triggering via either the slash command or the literal prompt.

Quick Start

Invoke the skill by typing /deliver in Codex to run the deliver workflow.

Frequently Asked Questions about azoth-deliver

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

FAQPage Schema

How do I run the Azoth deliver workflow inside Codex?▼

To run the Azoth deliver workflow inside Codex, invoke the primary entrypoint by typing /deliver. The skill parses user arguments after the trigger and reads the command contract to ensure consistent workflow execution.

What is the /deliver command in Codex used for?▼

The /deliver command in Codex serves as a Codex-native entrypoint for Azoth's deliver workflow. It bridges Codex commands with Azoth's execution engine, reading the command contract and body source to preserve stage structure and gate rules.

How does Codex read the Azoth deliver command contract?▼

Codex reads the Azoth deliver command contract by accessing commands/deliver/command.yaml and the body source at .claude/commands/deliver.md. This allows the orchestrator to preserve evaluation rules and the azoth_effect: write binding.

Can I use the deliver workflow without installing additional dependencies?▼

Yes, you can use the deliver workflow without installing additional dependencies. The skill requires no external dependencies, relying solely on reading the specified command paths and parsing the user arguments after the trigger.

Does the Azoth deliver workflow support triggering via natural language prompts?▼

Yes, the Azoth deliver workflow supports triggering via either the slash command or the literal prompt. This ensures flexible initiation while preserving the workflow's stage structure, gate rules, and evaluation rules.

Why is my Codex deliver workflow not enforcing the orchestrator binding?▼

Your Codex deliver workflow might not enforce the orchestrator binding if the command contract at commands/deliver/command.yaml is missing. The skill enforces the azoth_effect: write binding by explicitly reading this contract and the body source.