Agent CLI To API Migration with Claude Code: SKILL.md Template
A production playbook for agent CLI to API migration in cross-industry operations using Claude Code: skill.md template, run-scoped inputs, logs, typed results, and artifacts.
Audience: Developer tools teams productizing a local CLI
The problem
Developer tools teams productizing a local CLI need agent CLI to API migration to run repeatedly against CLI commands, workspace files, auth, and output expectations. 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 CLI commands, workspace files, auth, and output expectations per run, and let Argo turn the folder into a repeatable Claude Code 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 agent CLI to API migration, 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 agent CLI to API migration using Claude Code.
Read only /skill/.argo/inputs.
Write artifacts to /skill/output/artifacts.
Return argo.result.v1 with body.type = "agent_cli_to_api".
Run this on Argo