azoth-auto

Automate Codex-driven pipeline composition and execution via Azoth's /auto workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a Codex-visible entrypoint to trigger Azoth's /auto workflow, enabling automated pipeline composition and execution from Codex.

Core Features & Use Cases

  • Codex-visible entrypoint for Azoth's /auto workflow.
  • Reads the execution contract and body source to preserve the workflow's rules and bindings.
  • Supports argument extraction and preserves agent orchestration and azoth_effect: write constraints during execution.

Quick Start

Invoke /auto in Codex with your goal to auto-compose and execute the pipeline.

Frequently Asked Questions about azoth-auto

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

FAQPage Schema
How do I automate pipeline composition and execution from Codex?

You can automate pipeline composition by triggering the /auto slash command in Codex, which orchestrates the workflow to compose and execute pipelines based on your stated goal.

What is the /auto workflow in Codex used for?

The /auto workflow serves as a Codex entrypoint to trigger automated pipeline orchestration, reading execution contracts and body sources to preserve rules, bindings, and write constraints.

How does Codex preserve command contracts and agent bindings during workflow automation?

Codex preserves command contracts and agent bindings by reading the execution contract and body source during the /auto workflow, enforcing azoth_effect write constraints across all stages.

Can I use slash commands to extract arguments and enforce write constraints in Codex pipelines?

Yes, triggering the /auto slash command supports argument extraction while preserving agent orchestration and enforcing azoth_effect write constraints throughout the pipeline execution.

Do I need any external dependencies to run the /auto workflow in Codex?

No external dependencies are required to run the /auto workflow in Codex; it functions as a standalone entrypoint that internally reads contract and body sources to execute pipelines.

Why are my pipeline stage rules not applying when I trigger automated workflows in Codex?

Pipeline stage rules may fail if the /auto workflow cannot properly read the execution contract and body source, which are required to preserve gate rules and enforce write constraints.