OperationsFREEACCESS AVAILABLEFC-OPS-013
Status Claw
status-claw
v0.2.0May 22, 2026Status pages — incident communication templates, component hierarchies, and update schedules that keep users informed
Your status page is the first place customers check during an outage—and the last place you want to be caught with stale information or green dots when your payment system has been down for 20 minutes. I model your components honestly, template incident communications so you're not writing from scratch at 3 AM, and make sure your uptime history matches reality, not wishful thinking.
OpenClaw
Hermes
Claude Code
Codex
Cursor
Windsurf
Aider
OllamaPRIMARY ACTION
COMPATIBLE WITH
OpenClawHermesClaude CodeCodex+4
8 compatible tools5 output formats
When to Use
- Harden deployment and release workflows
- Improve observability and alert readiness
- Define environment standards
- Prepare operational runbooks
Compatible Frameworks
OpenClawHermesClaude CodeCodexCursorWindsurfAiderOllama8 TOOLS
Quality Gates
- Honest and timely communication
- Templates per severity level
- Componentes cubren servicios visibles
- Update frequency defined and scheduled
- Complete and structured response
5 GATES DEFINED
Expected Outputs
Status Page Component Model and Architecture MapIncident Communication Templates by SeverityUptime SLA Compliance ReportSubscriber Notification Workflow and Test ResultsStatus Page Runbook for Incident Communicators
Native exports per tool
OpenClaw10 files
openclaw/AGENTS.mdopenclaw/SOUL.mdopenclaw/TOOLS.md+7 moreHermes5 files
hermes/skills/flickclaw/status-claw/SKILL.mdhermes/skills/flickclaw/status-claw/references/workflow.mdhermes/skills/flickclaw/status-claw/references/quality-gates.md+2 moreClaude Code6 files
claude-code/CLAUDE.mdclaude-code/.claude/skills/status-claw/SKILL.mdclaude-code/.claude/skills/status-claw/references/workflow.md+3 moreCodex5 files
codex/AGENTS.mdcodex/.flickclaw/agents/status-claw/codex.mdcodex/.flickclaw/agents/status-claw/workflow.md+2 moreCursor3 files
cursor/.cursor/rules/flickclaw-status-claw.mdccursor/.cursor/rules/flickclaw-status-claw-workflow.mdccursor/.cursor/rules/flickclaw-status-claw-quality-gates.mdcWindsurf3 files
windsurf/.windsurf/rules/flickclaw-status-claw.mdwindsurf/.windsurf/rules/flickclaw-status-claw-workflow.mdwindsurf/.windsurf/rules/flickclaw-status-claw-quality-gates.mdAider3 files
aider/CONVENTIONS.mdaider/aider.mdaider/.aider.conf.ymlOllama4 files
ollama/Modelfileollama/system-prompt.mdollama/template.md+1 moreInstall Commands
Install the FlickClaw CLI, then select your AI agent framework below to get the correct install command.
Step 1: Install CLI (one-time)
npm install -g @flickclaw/cli@latestStep 2: Select Framework
OpenClaw
npm exec --yes @flickclaw/cli@latest -- install status-claw --target openclawDownload as ZIP
Example Prompt
Try this prompt with Status Claw to see what it can do:
Review the deployment pipeline and monitoring. Identify bottlenecks and single points of failure. Produce Status Page Component Model and Architecture Map, Incident Communication Templates by Severity, Uptime SLA Compliance Report.Example Output
IllustrativeWhat a typical Status Claw report looks like:
# Status Claw — Assessment Report **Project**: microservices-cluster **Context**: a Kubernetes cluster running 12 microservices with Istio and Prometheus **Generated**: 2026-07-10 ## Executive Summary The Status Claw completed its review of microservices-cluster (a Kubernetes cluster running 12 microservices with Istio and Prometheus). 3 findings were identified with concrete remediation steps. All quality gates were verified before delivery. ## Findings | # | Severity | Area | Finding | Recommended Action | |---|----------|------|---------|-------------------| | 1 | **P0** | Deployment | No rollback strategy defined for 4 services | Add Helm rollback hooks and deployment pause windows | | 2 | **P1** | Monitoring | Alert fatigue from 200+ low-priority alerts/day | Consolidate alerts, add severity routing, mute during maintenance | | 3 | **P2** | Cost | 3 dev clusters running 24/7 without downscaling | Add cron-based scaling to zero during off-hours | ## Quality Gates - [✓] Status updates posted within 15 minutes of incident declaration - [✓] Component model reflects actual system architecture - [✓] Historical uptime data accurate for SLA compliance reporting ## Outputs Generated - **Status Page Component Model and Architecture Map**: Included in the report above. - **Incident Communication Templates by Severity**: Included in the report above. - **Uptime SLA Compliance Report**: Included in the report above. - **Subscriber Notification Workflow and Test Results**: Included in the report above. - **Status Page Runbook for Incident Communicators**: Included in the report above. ## Validation - [x] All quality gates passed (3/3) - [x] 3 findings documented with severity and remediation - [x] 5 output sections generated - [x] Evidence collected and referenced --- *This is an illustrative example output from FlickClaw. Results vary based on project context.*
RELATED AGENTS