runtime-debug-skillDiagnose and fix bugs using runtime execution traces. Use when debugging errors, analyzing failures, or finding root causes in Python, Node.js, or Java appli...
Install via ClawdBot CLI:
clawdbot install dxsup/runtime-debug-skillGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Potentially destructive shell commands in tool definitions
curl -sL https://raw.githubusercontent.com/Syncause/ts-agent-file/v1.6.0/installCalls external URL not in known-safe list
https://syn-cause:${syncause.repo.token.p1}${syncause.repo.token.p2}@maven.pkg.gUses known external API (expected, informational)
raw.githubusercontent.comAI Analysis
The skill's external calls (GitHub, Maven) are for legitimate SDK installation and are consistent with its debugging purpose. The 'UNSAFE_SHELL' signal involves a curl command to fetch an installer from a public GitHub repository, which is a common, low-risk pattern for tool installation. No evidence of credential harvesting, data exfiltration, or hidden malicious instructions was found.
Generated Mar 22, 2026
An e-commerce platform experiences intermittent order failures during checkout. The skill helps collect runtime traces from the payment service to identify whether the bug is in the payment gateway integration, database transaction logic, or inventory validation. Using the structured reproduction hierarchy, developers start from the user's checkout API call to capture the complete call chain and pinpoint the exact error node.
A banking application shows incorrect balance updates after fund transfers. The skill analyzes runtime traces from the transaction service to detect if the issue stems from race conditions, faulty audit logging, or incorrect database commits. By reproducing the bug via sidecar tests in existing test infrastructure, it ensures high-quality trace data without disrupting live systems.
A healthcare app fails to sync patient records between devices, causing data inconsistencies. The skill diagnoses the bug by tracing API calls and database operations in the sync service, identifying whether the root cause is network timeouts, concurrency issues, or schema mismatches. The reproduction script verifies the bug using assertions to compare expected versus actual output.
A SaaS platform experiences slow response times in its reporting module. The skill collects performance traces to analyze query counts and execution times, identifying N+1 query problems or inefficient algorithms. Developers use the bug type identification for performance issues, recording metrics to compare baseline and stress test traces.
An IoT device running embedded software crashes when processing sensor data. The skill helps capture runtime traces from the firmware to locate the exact exception and stack trace. By reproducing the crash from the user entry point (e.g., CLI command), it ensures the trace contains the full error chain for debugging in constrained environments.
Offer the skill as part of a monthly subscription for development teams, providing continuous runtime debugging and trace analysis. Revenue is generated through tiered pricing based on the number of projects or trace volumes, with premium support for advanced features like performance optimization.
Deploy the skill on-demand for specific debugging engagements, such as critical production outages or complex bug investigations. Revenue comes from hourly or project-based consulting fees, with additional charges for rapid response and integration assistance.
License the skill to large enterprises for internal use across multiple teams, with customization options for specific tech stacks or compliance requirements. Revenue is generated through annual licensing contracts, including training, maintenance, and dedicated support.
💬 Integration Tip
Ensure the debug-mcp-server is installed and authenticated before starting; always verify SDK installation by checking dependency files to avoid conflicts with existing setups.
Scored Apr 19, 2026
Audited Apr 17, 2026 · audit v1.0
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.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
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.