Log Analysis with Codex: SKILL.md Template
A production playbook for log analysis in cross-industry operations using Codex: skill.md template, run-scoped inputs, logs, typed results, and artifacts.
Audience: Platform and support teams
The problem
Platform and support teams need log analysis to run repeatedly against application logs, traces, metrics exports, and incident notes. 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 application logs, traces, metrics exports, and incident notes 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 log analysis, 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 log analysis using Codex.
Read only /skill/.argo/inputs.
Write artifacts to /skill/output/artifacts.
Return argo.result.v1 with body.type = "log_analysis".
Run this on Argo