>
statuspage
Configure and manage status pages for incident communication and service health transparency. Use when a user needs to set up Atlassian Statuspage or open-source alternatives, manage components and incidents, automate status updates, or integrate with monitoring and alerting tools.
#statuspage#incident-communication#status-page#uptime#components
terminal-skillsv1.0.0
Works with:claude-codeopenai-codexgemini-clicursor
Usage
$
✓ Installed statuspage v1.0.0
Getting Started
- Install the skill using the command above
- Open your AI coding agent (Claude Code, Codex, Gemini CLI, or Cursor)
- Reference the skill in your prompt
- The AI will use the skill's capabilities automatically
Example Prompts
- "Deploy the latest build to the staging environment and run smoke tests"
- "Check the CI pipeline status and summarize any recent failures"
Documentation
Overview
Set up and manage status pages for communicating service health to users and stakeholders. Covers Atlassian Statuspage API usage, component management, incident lifecycle, scheduled maintenance, and automation with monitoring tools.
Instructions
Task A: Manage Components
bash
# List all components
curl -s "https://api.statuspage.io/v1/pages/${PAGE_ID}/components" \
-H "Authorization: OAuth ${STATUSPAGE_API_KEY}" | \
jq '.[] | {id: .id, name: .name, status: .status}'
bash
# Create a component
curl -X POST "https://api.statuspage.io/v1/pages/${PAGE_ID}/components" \
-H "Authorization: OAuth ${STATUSPAGE_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"component": {
"name": "Payment API",
"description": "Handles payment processing and billing",
"status": "operational",
"showcase": true,
"group_id": "api-services-group-id"
}
}'
bash
# Update component status (operational, degraded_performance, partial_outage, major_outage)
curl -X PATCH "https://api.statuspage.io/v1/pages/${PAGE_ID}/components/${COMPONENT_ID}" \
-H "Authorization: OAuth ${STATUSPAGE_API_KEY}" \
-H "Content-Type: application/json" \
-d '{ "component": { "status": "degraded_performance" } }'
Task B: Create and Manage Incidents
bash
# Create a new incident
curl -X POST "https://api.statuspage.io/v1/pages/${PAGE_ID}/incidents" \
-H "Authorization: OAuth ${STATUSPAGE_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"incident": {
"name": "Elevated error rates on Payment API",
"status": "investigating",
"impact_override": "minor",
"body": "We are investigating elevated error rates affecting payment processing. Some transactions may fail temporarily.",
"component_ids": ["payment-api-component-id"],
"components": {
"payment-api-component-id": "degraded_performance"
}
}
}'
bash
# Update incident with progress
curl -X PATCH "https://api.statuspage.io/v1/pages/${PAGE_ID}/incidents/${INCIDENT_ID}" \
-H "Authorization: OAuth ${STATUSPAGE_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"incident": {
"status": "identified",
"body": "The issue has been identified as a misconfigured connection pool in the payment gateway. A fix is being deployed."
}
}'
bash
# Resolve incident and restore component status
curl -X PATCH "https://api.statuspage.io/v1/pages/${PAGE_ID}/incidents/${INCIDENT_ID}" \
-H "Authorization: OAuth ${STATUSPAGE_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"incident": {
"status": "resolved",
"body": "The connection pool has been reconfigured and payment processing has returned to normal. We will continue monitoring.",
"components": {
"payment-api-component-id": "operational"
}
}
}'
Task C: Scheduled Maintenance
bash
# Create a scheduled maintenance window
curl -X POST "https://api.statuspage.io/v1/pages/${PAGE_ID}/incidents" \
-H "Authorization: OAuth ${STATUSPAGE_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"incident": {
"name": "Database maintenance - Read-only mode",
"status": "scheduled",
"scheduled_for": "2026-02-22T02:00:00Z",
"scheduled_until": "2026-02-22T04:00:00Z",
"body": "We will perform database maintenance that requires a 2-hour read-only window. Write operations will be unavailable during this time.",
"component_ids": ["database-component-id"],
"components": {
"database-component-id": "operational"
}
}
}'
Task D: Automation Script
python
# statuspage_automation.py — Auto-update status page from monitoring alerts
import requests
import os
STATUSPAGE_API = "https://api.statuspage.io/v1"
PAGE_ID = os.environ["STATUSPAGE_PAGE_ID"]
API_KEY = os.environ["STATUSPAGE_API_KEY"]
HEADERS = {
"Authorization": f"OAuth {API_KEY}",
"Content-Type": "application/json",
}
COMPONENT_MAP = {
"payment-service": "component-id-payment",
"order-service": "component-id-orders",
"api-gateway": "component-id-gateway",
}
def create_incident(service: str, severity: str, description: str) -> str:
"""Create a statuspage incident from an alert."""
component_id = COMPONENT_MAP.get(service)
impact = "major" if severity == "critical" else "minor"
component_status = "major_outage" if severity == "critical" else "degraded_performance"
resp = requests.post(
f"{STATUSPAGE_API}/pages/{PAGE_ID}/incidents",
headers=HEADERS,
json={
"incident": {
"name": f"{service}: {description[:80]}",
"status": "investigating",
"impact_override": impact,
"body": f"We are investigating an issue with {service}. Details: {description}",
"component_ids": [component_id] if component_id else [],
"components": {component_id: component_status} if component_id else {},
}
},
)
resp.raise_for_status()
incident = resp.json()
return incident["id"]
def resolve_incident(incident_id: str, service: str):
"""Resolve an incident and restore component status."""
component_id = COMPONENT_MAP.get(service)
requests.patch(
f"{STATUSPAGE_API}/pages/{PAGE_ID}/incidents/{incident_id}",
headers=HEADERS,
json={
"incident": {
"status": "resolved",
"body": f"The issue with {service} has been resolved. Service is operating normally.",
"components": {component_id: "operational"} if component_id else {},
}
},
).raise_for_status()
Task E: Open-Source Alternative (Cachet)
yaml
# docker-compose.yml — Cachet self-hosted status page
services:
cachet:
image: cachethq/docker:latest
environment:
- DB_DRIVER=pgsql
- DB_HOST=postgres
- DB_PORT=5432
- DB_DATABASE=cachet
- DB_USERNAME=cachet
- DB_PASSWORD=cachet_password
- APP_KEY=base64:generated_key_here
- APP_URL=https://status.example.com
ports:
- "8000:8000"
depends_on:
- postgres
postgres:
image: postgres:16-alpine
environment:
- POSTGRES_USER=cachet
- POSTGRES_PASSWORD=cachet_password
- POSTGRES_DB=cachet
volumes:
- pg_data:/var/lib/postgresql/data
volumes:
pg_data:
Best Practices
- Update status pages within 5 minutes of detecting an incident — speed builds trust
- Use clear, non-technical language in incident updates aimed at end users
- Follow the incident lifecycle: investigating → identified → monitoring → resolved
- Group related components (API, Web App, Database) for clearer status communication
- Automate component status updates from monitoring alerts to reduce response time
- Schedule maintenance windows at least 48 hours in advance with clear scope descriptions
Information
- Version
- 1.0.0
- Author
- terminal-skills
- Category
- DevOps
- License
- Apache-2.0