Service Debugging
Skill AktivStructured debugging runbook for backend services. Use when investigating production issues, API errors, performance problems, or when something broke and you need to find why.
To provide a systematic process for identifying and resolving issues in backend services, guiding users through a logical debugging workflow.
Funktionen
- Structured debugging process
- Systematic symptom gathering
- Common checks for issues
- Root cause analysis guidance
- Reproducing and fixing bugs
Anwendungsfälle
- Investigating production issues
- Resolving API errors (4xx, 5xx)
- Diagnosing performance degradation
- Finding the root cause of service breakages
Nicht-Ziele
- Replacing dedicated monitoring tools
- Automated deployment or rollback
- Performing code refactoring beyond bug fixes
Security
- warning:Secret ManagementThe 'Check the Obvious' section includes commands that print environment variables, including potential secrets, to stdout without redaction or user confirmation.
Portability
- warning:Structural AssumptionThe 'Check the Obvious' section assumes specific file paths like `logs/app.log` and environment variables like `$DB_HOST`, which might not exist in all user environments.
- warning:Runtime stabilityThe skill assumes a POSIX-like environment for bash commands and tools like `git`, `curl`, `psql`, and `jq`, which may not be universally available or function identically on all operating systems.
Execution
- warning:ValidationWhile commands like `grep` and `curl` are used, there is no explicit schema validation for file paths or URLs passed as arguments, which could lead to issues if malformed.
Code Execution
- warning:Error HandlingShell commands are used directly without explicit error handling for non-zero exit codes, meaning failures might not be reported clearly to the agent.
Errors
- warning:Actionable error messagesWhile some commands provide error output, the skill does not explicitly define user-facing error paths with remediation steps for all potential failures.
Installation
Zuerst Marketplace hinzufügen
/plugin marketplace add spartan-stratos/spartan-ai-toolkit/plugin install toolkit@spartan-marketplaceQualitätspunktzahl
Vertrauenssignale
Ähnliche Erweiterungen
Query Agent Events
99Bug-investigation tool for the Netdata agent-events ingestion namespace -- triage crashes, panics, fatals across the fleet by downloading events of interest and clustering locally. Covers the three transports (Cloud API and direct agent API are primary; ssh is operator-only), the verified AE_* field map and enum meanings, the dedup model (23h client-side per agent and event signature), the after-the-fact event timing (POST only on agent restart), and the Netdata systemd-journal plugin multi-value filter syntax (FIELD in A, B, C) AND ... Use when investigating crashes / panics / fatals; when grepping for events touching a specific function or file or version; when looking for regressions across versions; when an agent is reported crashing in a way you want to triage. Ships scripts get-events.sh and analyze-events.sh that fetch events with index-friendly filters and compute group-by stats. Defaults to last 24 hours and to the latest stable plus latest 2-3 nightlies.
Node Connect
100Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
Openclaw Debugging
100Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.
Systematic Debugging
100Systematic debugging methodology emphasizing root cause analysis over quick fixes
Troubleshooting
100Verwendet Chrome DevTools MCP und Dokumentation zur Fehlerbehebung bei Verbindungs- und Zielproblemen. Rufen Sie diese Fähigkeit auf, wenn list_pages, new_page oder navigate_page fehlschlagen oder wenn die Serverinitialisierung fehlschlägt.
Root Cause Tracing
99Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior