What problem does it solve? Escalating technical issues to vendors like Microsoft, ISPs, SaaS providers, or hardware manufacturers often stalls due to incomplete evidence, unclear severity mapping, and untracked communication. This Skill structures the entire vendor escalation lifecycle so internal ownership is never lost while waiting on external providers. ## Core Features & Use Cases - Evidence Package Construction: Builds minimal reproducible evidence bundles with sanitized logs, correlation IDs, environment matrices, and redacted secrets before vendor submission. - SLA and Communication Tracking: Records vendor case IDs, severity mapping, response checkpoints, and escalation thresholds so no case becomes an ownerless 'awaiting vendor' state. - Independent Closure Validation: Verifies service recovery against actual tenant, resource, and user state rather than trusting vendor closure notices. - Use Case: During a Microsoft 365 outage, use this Skill to draft a support case with redacted diagnostic logs, map internal severity to vendor severity, track SLA checkpoints, and escalate through account management when responses stall. ## Quick Start Help me build a vendor escalation case for our ongoing SaaS outage, including the evidence package, severity justification, and SLA tracking plan.
