openstatus-theme
OpenStatus Theme
Help the user design a new theme for openstatus status pages and, if they want, contribute it back to the @openstatus/theme-store package via pull request.
A theme is a bundle of CSS custom properties (light + dark mode) that openstatus applies to the status page. Themes live as .ts files in packages/theme-store/src/, each exporting a Theme object, registered in packages/theme-store/src/index.ts.
When to Use
Trigger on any of these — even if the user doesn't say "theme" explicitly:
- "I want to create a theme for my status page"
- "Add/contribute a new theme to openstatus"
- "Customize the colors of my status page"
- "Make a Solarized / Nord / Catppuccin / theme"
- "I have a palette exported from themes.openstatus.dev — wire it up"
- "Help me match my brand colors on the status page"
- Any mention of editing files in
packages/theme-store/
Do not use this skill for:
More from openstatushq/skills
global-speed-checker
Run global performance checks on HTTP endpoints from multiple regions worldwide. Use when users want to check speed, latency, performance, or test endpoints globally.
19status-report
Write periodic status reports summarizing overall system health, uptime, incidents, and maintenance. Use when the user mentions "status report," "health report," "uptime report," "weekly status," "monthly report," "system health summary," "reliability report," or wants to publish a regular update on how their services are performing.
7maintenance
Write planned maintenance announcements for each phase (scheduled, in-progress, completed). Use when the user mentions "maintenance announcement," "scheduled maintenance," "maintenance window," "planned downtime," "maintenance notification," or needs to communicate upcoming planned work to users.
7postmortem
Write blameless postmortems after incidents with timeline, root cause analysis, impact assessment, and action items. Use when the user mentions "postmortem," "post-mortem," "incident review," "root cause analysis," "RCA," "incident retrospective," "what went wrong," or wants to document lessons from a resolved incident.
7status-page-context
Create or update the status page context document that all other status page skills reference. Use when setting up status page skills for the first time, or when the user mentions "status page context," "configure status page," "set up incident tone," or wants to define their service components, SLAs, or communication style.
7incident-communication
Write clear, empathetic incident status updates for any phase of an incident (investigating, identified, monitoring, resolved). Use when the user mentions "incident update," "status update," "outage communication," "write an incident," "investigating update," "post-incident update," or needs to communicate a service disruption to users.
7