status-page-generator▌
kostja94/marketing-skills · updated Apr 8, 2026
Guides status page design for communicating service health, uptime, and incidents. Typically at status.* subdomain. Reduces support during outages, builds trust.
Pages: Status Page
Guides status page design for communicating service health, uptime, and incidents. Typically at status.* subdomain. Reduces support during outages, builds trust.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product and service components.
Identify:
- Service components: API, dashboard, billing, etc.
- Monitoring: What tools feed status (PagerDuty, Datadog, etc.)
- Audience: Customers, developers, internal
- Hosting: Self-hosted vs. third-party (Statuspage, Better Uptime, etc.)
Status Page Structure
| Section | Purpose |
|---|---|
| Overall status | Operational, Degraded, Outage, Maintenance |
| Components | Per service: status, uptime % |
| Incidents | Active and past; timeline, updates |
| Subscribe | Email, SMS, RSS for notifications |
| Uptime history | 90-day or custom range (optional) |
Best Practices
Communication
- Clear status: Operational, Degraded, Partial Outage, Major Outage
- Incident updates: Timely, honest, actionable
- Post-mortem: Link to post-incident review when public
- Maintenance: Schedule ahead, notify subscribers
Design
- Scannable: Status at a glance; green/yellow/red
- Mobile: Critical for on-the-go checks
- Accessible: Color + text; don't rely on color alone
- No login required: Public status, no auth
Technical
- Independent hosting: Status page should stay up when main product is down
- Subdomain: status.yourdomain.com
- Integrations: Slack, PagerDuty, etc. for incident creation
- Historical data: Uptime %, incident count
Output Format
- Structure (components, incident format)
- Status definitions and colors
- Incident template (title, updates, resolution)
- Subscribe options
- Hosting recommendation (self vs. third-party)
Related Skills
- docs-page-generator: Link status from docs footer
- api-page-generator: Link status for developer trust
- footer-generator: Status link in footer
- 404-page-generator: Status page as utility; similar UX principles
Ratings
4.5★★★★★10 reviews- ★★★★★Shikha Mishra· Oct 10, 2024
status-page-generator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Piyush G· Sep 9, 2024
Keeps context tight: status-page-generator is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Registry listing for status-page-generator matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Sakshi Patil· Jul 7, 2024
status-page-generator reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ganesh Mohane· Jun 6, 2024
I recommend status-page-generator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Oshnikdeep· May 5, 2024
Useful defaults in status-page-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Dhruvi Jain· Apr 4, 2024
status-page-generator has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Rahul Santra· Mar 3, 2024
Solid pick for teams standardizing on skills: status-page-generator is focused, and the summary matches what you get after install.
- ★★★★★Pratham Ware· Feb 2, 2024
We added status-page-generator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Yash Thakker· Jan 1, 2024
status-page-generator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.