diagnoseUse when the user reports a hard bug, unexpected failure, or performance regression that needs root-cause analysis.
Install via ClawdBot CLI:
clawdbot install genortg/diagnoseGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/open-gsd/gsd-coreAudited Jun 2, 2026 · audit v1.0
Generated Oct 6, 2026
A checkout service intermittently fails card authorization under peak load, causing revenue loss. The on-call engineer uses the diagnose loop to build a fast curl/HTTP feedback loop, reproduce at a higher rate, and safely instrument the exact failure seam. The fix is locked down with a regression test before deploying.
After upgrading a major dependency, a B2B analytics dashboard shows subtle wrong totals in reports. The team uses differential and snapshot loops to isolate the behavioral change, generates ranked falsifiable hypotheses, and confirms the root cause with targeted instrumentation rather than guesswork.
A core library's test suite is 8% flaky, blocking releases and eroding trust in CI. The skill's non-deterministic bug strategy raises reproduction rate through parallel loops and stress, then tags debug logs to pinpoint the shared-state race. A deterministic regression test is added at the right seam.
A mobile commerce app's product page load time jumped 400ms after a release, hurting conversion. Following the perf branch, the team baselines timing with a profiler, bisects candidate changes, and measures before fixing. The regression is locked with a performance test.
A nightly ETL job occasionally drops records for a subset of patients, creating compliance risk. The engineer replays captured event logs through an isolated harness, ranks hypotheses with predictions, and uses tagged logs to find the boundary condition. The absence of a correct test seam is flagged for architecture follow-up.
A product that bundles the diagnose skill as part of an AI pair-programmer for engineering teams. Users invoke diagnose on failing tests, errors, or regressions directly from the IDE or CLI, and the agent runs the disciplined loop to find root causes. Teams pay monthly per seat for faster mean-time-to-resolution.
A service where AI agents equipped with diagnose continuously watch production, reproduce failures in sandboxed environments, and deliver root-cause reports and patches to customer teams. This reduces MTTR and on-call burden for companies without deep debugging expertise. Pricing is based on monitored services and incident volume.
The diagnose skill is offered as an open-source agent capability, while the vendor sells enterprise support, private deployment, and integrations with proprietary observability stacks. Customers pay for SLAs, security reviews, and custom connectors. This drives adoption through community contributions and converts large organizations to paid contracts.
💬 Integration Tip
Wire diagnose into your existing CI and observability stack so the Phase 1 feedback loop can pull real traces, logs, and test harnesses automatically. Provide the agent with repo-specific domain glossaries and ADR locations to accelerate hypothesis quality and prevent shallow-seam regression tests.
Scored Oct 6, 2026
Firecrawl CLI for web scraping, crawling, and search. Scrape single pages or entire websites, map site URLs, and search the web with full content extraction. Returns clean markdown optimized for LLM context. Use for research, documentation extraction, competitive intelligence, and content monitoring.
Incident Commander Skill
Monitors OpenClaw cron job health, identifies failures, timeouts, and delivery issues.
Observability Designer (POWERFUL)
Use when defining SLIs/SLOs, managing error budgets, or building reliable systems at scale. Invoke for incident management, chaos engineering, toil reduction, capacity planning.
QQ bot integration for OpenClaw with session isolation, logging, and AI auto-reply. Supports private chat and group @messages.