Service outage notice

Write resident-facing outage notices covering impact, interim actions, and restoration estimates.

49|11|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/vstorm-co/agenticos --skill service-outage-notice-vstorm-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Service outage notice
Source: https://github.com/vstorm-co/agenticos/tree/main/backend/app/core/catalog/skill_gallery/public-sector/service-outage-notice
Command: npx skills add https://github.com/vstorm-co/agenticos --skill service-outage-notice-vstorm-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? During a utility or service outage, residents need clear, fast information, but notices often bury critical facts under internal jargon, vague area boundaries, and missing update times. This Skill structures outage communications so the three facts residents actually need come first. ## Core Features & Use Cases - Three-fact lead structure: States what is affected by area and street, what residents should do now, and when service is expected back with a committed next-update time. - Vulnerable-customer prioritization: Places the priority-register route in the first paragraph so supply-dependent residents see it immediately. - Estimate discipline: Enforces labeling restoration times as estimates and updating them on the promised schedule to preserve trust. - Use Case: A water utility loses pressure across three streets. Use this Skill to draft a notice that names the affected streets, gives the bottled-water pickup point and priority-register contact, and commits to a 14:00 update. ## Quick Start Write a service outage notice for a power cut affecting Elm Street and Oak Avenue, with restoration estimated at 18:00 and a priority line for medically dependent customers.

Frequently Asked Questions about Service outage notice

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

FAQPage Schema
How do I write a service outage notice for residents?▼

Lead with three facts: what is affected by area and street, what residents should do now including alternatives, and when service is expected back with a committed next-update time. Everything else is secondary during an active outage.

What should a utility outage communication include first?▼

The priority-register route for vulnerable customers goes in the first paragraph, not the footer. Anyone dependent on the supply needs that contact before they need the cause of the outage.

Should outage notices include restoration time estimates?▼

Yes, give one estimate, label it clearly as an estimate, and update on the promised schedule even if nothing changes. A missed update destroys more trust than a slipped restoration time.

How much detail about the outage cause should be published?▼

One plain sentence, or nothing at all. Detailed cause explanations invite argument and delay the notice, and residents are not waiting for that information during the outage.

What mistakes should be avoided in outage communications?▼

Never use internal terminology, publish area boundaries residents cannot map to their own street, or let an estimate expire without issuing a new one. These errors erode trust and generate avoidable contact volume.