Partner Integration Review with Claude Code: SKILL.md Template
A production playbook for partner integration review in cross-industry operations using Claude Code: skill.md template, run-scoped inputs, logs, typed results, and artifacts.
Audience: Partnership engineering teams
The problem
Partnership engineering teams need partner integration review to run repeatedly against API docs, payload samples, auth requirements, and test evidence. 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 API docs, payload samples, auth requirements, and test evidence 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 partner integration review, 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 partner integration review using Claude Code.
Read only /skill/.argo/inputs.
Write artifacts to /skill/output/artifacts.
Return argo.result.v1 with body.type = "partner_integration_review".
Run this on Argo