Tenant Isolation Review with Claude Code: SKILL.md Template
A production playbook for tenant isolation review in cross-industry operations using Claude Code: skill.md template, run-scoped inputs, logs, typed results, and artifacts.
Audience: B2B SaaS security teams
The problem
B2B SaaS security teams need tenant isolation review to run repeatedly against tenant IDs, storage paths, logs, credentials, and auth checks. 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 tenant IDs, storage paths, logs, credentials, and auth checks 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 tenant isolation 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 tenant isolation review using Claude Code.
Read only /skill/.argo/inputs.
Write artifacts to /skill/output/artifacts.
Return argo.result.v1 with body.type = "tenant_isolation_review".
Run this on Argo