Status Page

Implement a public status page with incident management and uptime tracking.

1|Updated Sep 14, 2025
One-click install
npx skills add https://github.com/CleanExpo/DR-NRPG --skill status-page
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Status Page
Source: https://github.com/CleanExpo/DR-NRPG/tree/main/.skills/custom/status-page
Command: npx skills add https://github.com/CleanExpo/DR-NRPG --skill status-page

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a clear, public-facing status page for your service, ensuring transparency with users during incidents and downtime.

Core Features & Use Cases

  • Real-time Service Status: Displays the current operational status of all monitored services.
  • Incident Management: Logs and communicates active incidents with severity levels and updates.
  • Uptime Tracking: Calculates and displays historical uptime percentages for each service.
  • Scheduled Maintenance: Informs users about upcoming maintenance windows.
  • Use Case: A SaaS company uses this Skill to inform its customers about a service degradation, providing real-time updates and expected resolution times, thereby managing user expectations and maintaining trust.

Quick Start

Implement the status page skill to display current service health and active incidents.

Frequently Asked Questions about Status Page

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

FAQPage Schema
How do I create a public status page for incident management and uptime monitoring?

You create a public status page by codifying service status patterns that integrate with deep health endpoints, displaying real-time operational status, incident timelines, and uptime percentages for your monitored services.

What is the best way to communicate scheduled maintenance windows to SaaS users?

The best way to communicate scheduled maintenance is through a public status page that logs upcoming maintenance windows, informs users in real-time, and manages expectations during service degradation or downtime.

Does a status page skill require existing health check infrastructure to function?

Yes, implementing this status page requires integration with existing health check infrastructure and a dedicated database for logging historical health data to calculate uptime and track incidents accurately.

How do I calculate and display historical uptime percentages for monitored services?

You calculate historical uptime by logging health data to a database via deep health endpoints, then using status page patterns to process this data and display uptime percentages for each service.

Can I implement incident management workflows with severity levels using FastAPI and React?

Yes, you can implement incident management workflows using FastAPI and React components to log active incidents, assign severity levels, publish updates, and notify subscribers of service status changes.

What are the limitations of building a public service health reporting page?

Limitations include the requirement for pre-existing health check infrastructure and a database for historical health logging, meaning this approach cannot function as a standalone monitoring solution without backend integration.