Spreadsheet Validation with Claude Code: API Runtime Pattern
A production playbook for spreadsheet validation in cross-industry operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Operations teams that live in Excel
The problem
Operations teams that live in Excel need spreadsheet validation to run repeatedly against workbooks, CSVs, mappings, and validation rules. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the spreadsheet validation instructions as a skill, send workbooks, CSVs, mappings, and validation rules as run-scoped inputs, execute with Claude Code, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For spreadsheet validation, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=claude-code
workflow=spreadsheet-validation
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo