Email Intake Routing with Codex: SKILL.md Template
A production playbook for email intake routing in cross-industry operations using Codex: skill.md template, run-scoped inputs, logs, typed results, and artifacts.
Audience: Shared inbox and intake teams
The problem
Shared inbox and intake teams need email intake routing to run repeatedly against email bodies, attachments, sender metadata, and routing rules. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Put the operating procedure in SKILL.md, keep examples beside the skill, attach email bodies, attachments, sender metadata, and routing rules per run, and let Argo turn the folder into a repeatable Codex execution.
Tradeoffs and failure modes
A skill folder is less flexible than an open chat, but it gives the product a versioned workflow that can be tested and rolled back. For email intake routing, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
SKILL.md starter
# SKILL.md
You run email intake routing using Codex.
Read only /skill/.argo/inputs.
Write artifacts to /skill/output/artifacts.
Return argo.result.v1 with body.type = "email_intake_routing".
Run this on Argo