statuspage-and-comms-ops

Draft customer-safe incident communications for AI SaaS services.

1|Updated Mar 12, 2026

Search Tags:#approval-workflow #cadence-management #status-page #outage-management #incident-communications #customer-safety #communications-ops

Ready to run

npx skills add https://github.com/XiaoPuOuO/VFactory --skill statuspage-and-comms-ops

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: statuspage-and-comms-ops
Source: https://github.com/XiaoPuOuO/VFactory/tree/main/paperclip-official/AgentSetting/skills/statuspage-and-comms-ops
Command: npx skills add https://github.com/XiaoPuOuO/VFactory --skill statuspage-and-comms-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

External incident and status communication operations for an AI SaaS company: distinguish internal and external audiences, enforce update cadence, draft status page messages safely, maintain ETA discipline, route approvals, and close incidents with recovery and customer-safe resolution messaging.

Core Features & Use Cases

Distinguish internal vs external communications and route appropriately
Enforce update cadence and ETA discipline in customer-facing messages
Draft approved, customer-safe templates for status pages and incident updates
Manage approvals and ownership for communications across outages and maintenance
Support recovery and closure messaging with clear next steps

Quick Start

Draft a customer-facing status update for a service outage following the templates and cadence rules

Frequently Asked Questions about statuspage-and-comms-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I draft incident communications for an AI SaaS outage that separate internal and external audiences?▼

Incident communications for an AI SaaS outage require strict audience separation, routing internal operational updates differently from customer-safe status page messages. This skill drafts those distinct messages while enforcing update cadence and ETA discipline for both groups.

What is the best way to maintain update cadence and ETA discipline during a service degradation event?▼

Update cadence and ETA discipline during service degradation are maintained by enforcing scheduled communication intervals and realistic recovery timelines. This skill manages approval ownership and generates cadence-compliant templates to ensure timely, accurate customer-facing updates.

Can I use this for planned maintenance and post-incident recovery messaging, or is it only for real-time outage responses?▼

Planned maintenance and post-incident recovery messaging are fully supported alongside real-time outage responses. The skill applies customer-safe wording and clear next steps to draft closure messaging, ensuring consistent communications operations across all incident types.

How do I route approvals for status page updates during an active incident?▼

Routing approvals for status page updates involves designating communication ownership and enforcing approval workflows before external publication. This skill structures the approval routing process to ensure all customer-safe templates and incident updates are reviewed by the correct stakeholders.

Why does customer-safe wording matter in incident communications, and how is it applied here?▼

Customer-safe wording in incident communications prevents panic, avoids speculative technical blame, and maintains trust during outages. This skill enforces customer-safe wording directly within its status page templates and degradation messaging drafts.

What are the limitations of using automated incident communication templates for AI service outages?▼

Automated incident communication templates cannot replace real-time engineering diagnostics or dynamic internal decision-making during complex AI service outages. This skill provides structurally safe messaging frameworks and cadence enforcement, but requires human approval ownership before external publication.