azoth-intake

Route user prompts into Azoth's intake workflow via the Codex entrypoint.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Azoth's intake workflow requires a clean Codex-visible entrypoint to trigger the intake sequence and route user prompts into the governed protocol. This skill provides that entrypoint and preserves the command's contracts, bindings, and ARGUMENTS handling.

Core Features & Use Cases

  • Codex-visible entrypoint for Azoth's /intake workflow.
  • Preserves the command's stage structure, gate rules, evaluation rules, and agent bindings.
  • Reads the intake specification from .claude/commands/intake.md and applies it to incoming prompts.
  • Use Case: enqueue insights from .azoth/inbox and process them through the intake protocol.

Quick Start

Invoke /azoth-intake in Codex and supply your intake prompt to begin processing.

Frequently Asked Questions about azoth-intake

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

FAQPage Schema
How do I route user prompts to an intake workflow using Codex?

To route user prompts to an intake workflow using Codex, invoke the entrypoint to translate prompts into ARGUMENTS. It applies the governed intake protocol by reading the intake specification, preserving stage structure, gate rules, and evaluation rules.

What is the best way to trigger the Azoth intake protocol from a prompt?

Triggering the Azoth intake protocol requires calling the Codex entrypoint, which reads the intake source of truth. It applies the defined agent bindings and azoth_effect contracts to process your prompt through the governed sequence.

How does prompt routing preserve command stage structure and gate rules?

Prompt routing preserves command stage structure and gate rules by reading the intake specification directly. It translates incoming prompts into ARGUMENTS while respecting the original command's evaluation rules and referenced orchestrator agents.

Can I use this intake workflow to process insights from an inbox directory?

Yes, you can use this intake workflow to process insights from an inbox directory. You enqueue insights from the directory and process them through the governed intake protocol by supplying your prompt at the entrypoint.

Do I need an orchestrator agent contract to run the intake protocol?

Yes, you need an orchestrator agent contract to run the intake protocol. The workflow respects the command's agent bindings and azoth_effect write contracts, ensuring the intake sequence executes under the governed protocol.

Why does my intake prompt not translate correctly into ARGUMENTS?

An intake prompt may not translate correctly into ARGUMENTS if the intake specification is missing or misconfigured. The workflow relies on reading the intake source of truth to properly map prompts while preserving stage structure and gate rules.