debug-probeProvides a precise six-phase hypothesis-driven runtime debugging process with minimal instrumentation to identify and fix root causes of unexpected behavior.
Install via ClawdBot CLI:
clawdbot install zelixag/debug-probeGrade 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/YOUR_USERNAME/debug-probe.gitAudited May 26, 2026 · audit v1.0
Generated Oct 6, 2026
A SaaS platform experiences intermittent 500 errors only in production that cannot be reproduced locally. Engineers use Debug Probe to form falsifiable hypotheses about race conditions or connection pool exhaustion, instrument critical paths with tagged logs, and have on-call staff reproduce the issue with exported diagnostic buffers.
A fintech app occasionally crashes on Android devices during payment confirmation but the stack trace is ambiguous. The team uses Debug Probe to hypothesize state corruption versus lifecycle timing, adds minimal instrumentation, and gathers logs from affected users to pinpoint the exact sequence.
An IoT device resets unexpectedly after long uptime, and code review reveals nothing obvious. Firmware engineers apply Debug Probe to instrument memory and watchdog pathways, collect logs from deployed units, and converge on a heap fragmentation root cause before applying a minimal fix and removing all diagnostic code.
A large insurance company's new microservice fails to sync with a decades-old mainframe system under specific batch schedules. Using Debug Probe, the integration team hypothesizes encoding and timeout mismatches, adds precise logging around the boundary, and uses user-exported logs to confirm the exact failure point.
A game studio faces frame drops that occur only during certain multiplayer interactions and cannot be caught in the editor. Developers use Debug Probe to instrument network and physics loops with minimal overhead, collect player session logs, and correlate timestamps to identify a synchronization bug.
The core Debug Probe skill is free and open-source to drive adoption among individual developers and small teams. A paid enterprise tier adds team-shared diagnostic buffer storage, centralized log aggregation, and compliance-friendly audit trails.
Debug Probe is bundled as a plugin or extension inside popular IDEs (VS Code, JetBrains) or application performance monitoring platforms. The host platform charges a subscription, with the probe as a value-added feature that increases retention and upsell potential.
Offer specialized debugging workshops and on-site consulting where experts train engineering teams to adopt the 6-phase methodology, instrument legacy systems, and establish diagnostic best practices. The skill itself is freely available, but expert guidance is sold.
💬 Integration Tip
Pair Debug Probe with your existing logging or APM stack, and enforce the mandatory cleanup phase via a CI check that scans for leftover DIAG tags before merging.
Scored Oct 6, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.