Usage Anomaly Investigation with Codex: SKILL.md Template
A production playbook for usage anomaly investigation in cross-industry operations using Codex: skill.md template, run-scoped inputs, logs, typed results, and artifacts.
Audience: Growth and infra teams
The problem
Growth and infra teams need usage anomaly investigation to run repeatedly against usage exports, logs, billing events, and customer metadata. 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 usage exports, logs, billing events, and customer metadata 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 usage anomaly investigation, 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 usage anomaly investigation using Codex.
Read only /skill/.argo/inputs.
Write artifacts to /skill/output/artifacts.
Return argo.result.v1 with body.type = "usage_anomaly_investigation".
Run this on Argo