SDK Migration Guide Generation with Claude Code: SKILL.md Template
A production playbook for SDK migration guide generation in cross-industry operations using Claude Code: skill.md template, run-scoped inputs, logs, typed results, and artifacts.
Audience: Developer experience teams
The problem
Developer experience teams need SDK migration guide generation to run repeatedly against old SDK docs, new SDK docs, examples, and changelogs. 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 old SDK docs, new SDK docs, examples, and changelogs 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 SDK migration guide generation, 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 SDK migration guide generation using Claude Code.
Read only /skill/.argo/inputs.
Write artifacts to /skill/output/artifacts.
Return argo.result.v1 with body.type = "sdk_migration_guide".
Run this on Argo