Customer Support Verification

Overview

Use this skill as the final gate for support work. It turns the user's support rules into an explicit verification report before the agent says the task is done.

Required Inputs

Collect these before verifying:

• The applicable support RUNBOOK.md or user-provided support requirements.
• Any product-specific AGENTS.md, support runbook, or billing/access runbook that was used.
• The customer request, Gmail thread/draft ids, and current draft body when present.
• The evidence gathered from local docs/source/admin/read-only data.
• A list of every external action taken, including Gmail, Stripe, Firebase, Supabase, browser, deploy, or commit actions.
• The hourly unresolved follow-up status: created, blocked, or not applicable, plus the planned question/content. It must ask the request owner whether the case is resolved, summarize what the customer wants, and say what the request owner should do next.

If any input is missing, mark the related check UNKNOWN, explain why, and do not treat the task as fully verified.