skills.rest
yiwei79
yiwei79OFFICIAL
Explore all skills by this author →
GitHub

azoth-bootstrap

Invoke Azoth's /bootstrap workflow from Codex CLI or IDE surfaces.

Updated Apr 8, 2026
Search Tags:#workflow#codex#kernel#orchestrator#bootstrap#entrypoint#azoth
One-click install
npx skills add https://github.com/yiwei79/azoth --skill azoth-bootstrap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azoth-bootstrap
Source: https://github.com/yiwei79/azoth/tree/main/.agents/skills/azoth-bootstrap
Command: npx skills add https://github.com/yiwei79/azoth --skill azoth-bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Azoth bootstrap workflows can be brittle when triggered from ad-hoc prompts; this skill provides a Codex-native entrypoint to invoke the /bootstrap process reliably.

Core Features & Use Cases

  • Codex-native entrypoint for Azoth's /bootstrap workflow that translates Codex commands into a bootstrap execution.
  • Preserves command structure, gate rules, evaluation rules, and the agent binding (agent: orchestrator) when executing the bootstrap.
  • Enables consistent bootstrap initiation from Codex CLI/IDE and app surfaces with arguments passed after the skill name.

Quick Start

Ask Codex to run azoth-bootstrap with your desired arguments.

Frequently Asked Questions about azoth-bootstrap

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

FAQPage Schema
How do I trigger an Azoth bootstrap workflow directly from the Codex CLI?▼

You can trigger an Azoth bootstrap from the Codex CLI by running the azoth-bootstrap entrypoint with your desired arguments. It provides a Codex-native command surface that reliably initiates the bootstrap process without relying on ad-hoc prompts.

What is the best way to execute an Azoth /bootstrap process from an IDE or slash-command surface?▼

The best way to execute an Azoth /bootstrap from IDE or slash-command surfaces is using a Codex-native entrypoint. It translates Codex commands into a bootstrap execution while preserving the agent: orchestrator binding.

Does the Azoth bootstrap entrypoint preserve command structure and gate rules when invoked from Codex?▼

Yes, the Azoth bootstrap entrypoint preserves the command structure, gate rules, evaluation rules, and the agent: orchestrator binding when executing the bootstrap workflow from any Codex surface.

Why does my Azoth bootstrap workflow fail or behave inconsistently when triggered by ad-hoc prompts?▼

Azoth bootstrap workflows can be brittle when triggered from ad-hoc prompts. Using a dedicated Codex-native entrypoint ensures reliable invocation by reading .claude/commands/bootstrap.md as the source of truth.

Can I pass custom arguments when initiating the bootstrap workflow from Codex?▼

Yes, you can pass optional arguments after the azoth-bootstrap skill name when initiating the workflow. This enables consistent bootstrap initiation from Codex CLI, IDE, and app surfaces.

What source of truth does the Codex-native bootstrap entrypoint use to execute the Azoth workflow?▼

The Codex-native bootstrap entrypoint reads .claude/commands/bootstrap.md as the source of truth. This ensures the bootstrap workflow executes consistently according to defined rules and structure.

Related Skills

Explore More Software Engineering Skills→
yiwei79yiwei79

azoth-context-architect

Define the Codex-visible entrypoint for Azoth's /context-architect workflow.

Official
Advanced
yiwei79yiwei79

azoth-hookmode

Expose a Codex-native entrypoint for the /hookmode workflow.

Official
Advanced
yiwei79yiwei79

azoth-autonomous-auto

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

Official
Advanced
yiwei79yiwei79

azoth-start

Route Codex /start prompts to Azoth command.yaml and body.md workflows.

Official
Intermediate