From uptime
This skill should be used when the user asks to "create a dashboard", "set up a dashboard", "organize monitoring views", "build a dashboard", "add widgets", "monitoring dashboard", or wants to create visual overviews of their monitoring checks. Covers dashboard creation patterns and widget organization.
How this skill is triggered — by the user, by Claude, or both
Slash command
/uptime:dashboard-managementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Workflow patterns for creating and organizing monitoring dashboards.
Workflow patterns for creating and organizing monitoring dashboards.
Dashboards work best when they have a clear purpose. Common patterns:
| Pattern | Scope | Use case |
|---|---|---|
| Domain dashboard | All checks for one domain | Per-service visibility |
| Team dashboard | All checks owned by a team | Team-level overview |
| Service tier dashboard | All critical/production checks | Executive or on-call view |
| Check type dashboard | All checks of one type (e.g. SSL) | Focused monitoring (certificate expiry overview) |
Call get_account_usage to check whether dashboard or widget limits apply to the account. If limits exist and are near capacity (>80%), warn the user before creating new dashboards or widgets.
Gather checks based on the chosen scope:
list_checks with tag filter for domain/team dashboardslist_checks then filter by check type for type-specific dashboardslist_tags to discover grouping structure if scope isn't clearcreate_dashboard with:
Add widgets for the checks gathered in Step 2. Widget selection depends on what information matters for the dashboard's audience.
| Widget type | Best for | Notes |
|---|---|---|
| Check status | At-a-glance up/down | Use for overview dashboards — shows current state |
| Response time | Performance trending | Best for HTTP and TCP checks — shows latency |
| Uptime percentage | SLA reporting | Shows uptime over a time window |
| Alert history | Incident patterns | Shows when and how often alerts fired |
When adding a widget, specify:
Response time and uptime percentage widgets are most useful with longer time ranges (7d+). Check status widgets are best with short/live views.
Not all widget types make sense for all check types:
| Check type | Check status | Response time | Uptime % | Alert history |
|---|---|---|---|---|
| HTTP | Yes | Yes | Yes | Yes |
| DNS, ICMP, TCP, UDP | Yes | Yes | Yes | Yes |
| SSL, WHOIS, RDAP | Yes | No | Yes | Yes |
| Blacklist, Malware | Yes | No | No | Yes |
| Page Speed | Yes | No | No | No |
| Group | Yes | No | Yes | Yes |
| Transaction, API | Yes | Yes | Yes | Yes |
SSL, WHOIS, RDAP, Blacklist, and Malware are auto-located checks with infrequent intervals, so response time widgets add no value. Page Speed produces Lighthouse scores, not uptime data.
Domain dashboard: group widgets by check type
On-call dashboard: prioritize actionable information
Executive dashboard: focus on outcomes
Consistent dashboard names help with discovery:
{domain} monitoring — per-domain dashboards{team} overview — team dashboards{purpose} dashboard — special-purpose (e.g. "SSL expiry dashboard")When monitoring evolves, dashboards need to keep up.
get_dashboard to see current widgets.When a dashboard has drifted significantly (many stale widgets, missing checks):
list_checks with the domain tag to get the current check set.Dashboards can drift as checks are added or removed:
monitoring-optimization finds configuration issues, update widgets to reflect changesUse delete_dashboard only for permanent removal. Deletion removes all widgets. If a dashboard is temporarily unneeded, consider removing widgets instead and keeping the dashboard shell for later reuse.
Before deleting, confirm the dashboard isn't referenced by other team members or linked from external tools (e.g. Slack bookmarks, wiki pages).
When monitoring-planning creates checks for a new domain, Phase 2 creates a dashboard. This ensures every monitored domain has a corresponding dashboard from day one. The dashboard should include widgets for all checks created during setup.
npx claudepluginhub uptime-com/uptime-skills --plugin uptimeProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.