azoth-autonomous-auto

Execute the autonomous-auto Codex workflow with argument capture and contract preservation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explicit Codex entrypoint for Azoth's /autonomous-auto workflow. Use when the user wants to run /autonomous-auto in Codex via /skills or $azoth-autonomous-auto.

Core Features & Use Cases

  • Unified Codex entrypoint for the /autonomous-auto workflow.
  • Preserves the command's contract, body source, and agent bindings to ensure predictable execution.
  • Enables Codex-based activation from slash commands or CLI prompts.

Quick Start

Invoke the autonomous-auto workflow in Codex by typing /autonomous-auto.

Frequently Asked Questions about azoth-autonomous-auto

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

FAQPage Schema
How do I trigger the autonomous-auto workflow in Codex?▼

To trigger the autonomous-auto workflow in Codex, invoke the unified entrypoint by typing /autonomous-auto or using the explicit command, which preserves execution contracts and agent bindings.

What does an autonomous Codex orchestrator workflow do?▼

An autonomous Codex orchestrator workflow automates execution by acting as the command surface, capturing arguments, and preserving gate and evaluation rules to ensure predictable agent-bound task processing.

Can I run autonomous-auto workflows from CLI scripts and prompts?▼

Yes, you can run autonomous-auto workflows from CLI scripts or explicit prompts. The command surface captures arguments and preserves gate rules across Codex interfaces for consistent execution.

Does the autonomous-auto command preserve contract paths and gate rules?▼

Yes, the autonomous-auto command preserves contract paths, body source references, agent bindings to the orchestrator, and azoth_effect write semantics to satisfy strict execution contracts.

Are there limitations when triggering Azoth workflows via Codex?▼

The primary limitation is that execution depends on Codex interfaces. The workflow requires proper agent binding to the orchestrator and azoth_effect write semantics to satisfy its execution contracts.