/status
When the user wants to create, optimize, or structure a status page. Also use when the user mentions "status page," "status.yourdomain.com," "uptime," "service health," "incident page," or "system status." For incident comms, use public-relations.
$ npx -y skills add kostja94/marketing-skills --skill status --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/status
Context preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to create, optimize, or structure a status page. Also use when the user mentions "status page," "status.yourdomain.com," "uptime," "service health," "incident page," or "system status." For incident comms, use public-relations.
SKILL.md
status.SKILL.mdname: status-page-generator
description: When the user wants to create, optimize, or structure a status page. Also use when the user mentions "status page," "status.yourdomain.com," "uptime," "service health," "incident page," or "system status." For incident comms, use public-relations.
metadata:
version: 1.0.1
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: 1. **Service components**: API, dashboard, billing, etc. 2. **Monitoring**: What tools feed status (PagerDuty, Datadog, etc.) 3. **Audience**: Customers, developers, internal 4. **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
Read more
name: status-page-generator description: When the user wants to create, optimize, or structure a status page. Also use when the user mentions "status page," "status.yourdomain.com," "uptime," "service health," "incident page," or "system status." For incident comms, use public-relations. metadata: version: 1.0.1
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: 1. **Service components**: API, dashboard, billing, etc. 2. **Monitoring**: What tools feed status (PagerDuty, Datadog, etc.) 3. **Audience**: Customers, developers, internal 4. **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
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
Open skill - /ai-traffic
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to
Open skill - /traffic
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel
Open skill - /tracking
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event
Open skill - /community-forum
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia,"
Open skill