swamp-troubleshooting

Diagnose swamp environment issues through tiered health checks, error inspection, tracing, and source reading.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/alvagante/agentspulse --skill swamp-troubleshooting-alvagante
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swamp-troubleshooting
Source: https://github.com/alvagante/agentspulse/tree/main/.agents/skills/swamp-troubleshooting
Command: npx skills add https://github.com/alvagante/agentspulse --skill swamp-troubleshooting-alvagante

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a diagnostic tool for identifying and resolving issues within the swamp environment, optimizing its performance and reliability.

Core Features & Use Cases

  • Diagnostic Loop: Offers a layered approach to diagnosing issues, from health checks to source reading.
  • Symptom Matching: Provides a guide to start at the correct diagnostic tier based on symptoms.
  • Error Inspection: In-depth error analysis through stderr, JSON output, and exit codes.
  • Health Checks: Runs doctor commands for specific integrations and checks.
  • Tracing: Enables OpenTelemetry tracing for detailed execution analysis.
  • Source Reading: Provides guidance on accessing and interpreting the source code for complex issues.

Quick Start

Run the 'swamp doctor audit' command to check the audit integration's health.

Frequently Asked Questions about swamp-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot swamp environment integration problems?

To troubleshoot swamp environment integration problems, run the 'swamp doctor audit' command. This initiates a diagnostic loop that performs health checks to quickly identify and resolve specific integration failures.

How do I debug performance issues in the swamp environment?

Debug swamp environment performance issues by enabling OpenTelemetry tracing. This provides detailed execution analysis within the diagnostic loop to pinpoint bottlenecks during troubleshooting.

What is the best way to diagnose swamp environment errors?

The best way to diagnose swamp environment errors is through in-depth error inspection. Analyze stderr, JSON output, and exit codes to match symptoms to the correct diagnostic tier for resolution.

Do I need the swamp CLI to use this diagnostic tool?

Yes, you need the swamp CLI installed and accessible. The diagnostic tool requires the CLI to run doctor commands and health checks, while OpenTelemetry tracing setup is optional for deeper analysis.

What should I do when swamp environment health checks pass but issues persist?

When swamp environment health checks pass but issues persist, proceed to source reading. The tool provides guidance on accessing and interpreting source code to resolve complex, deeply rooted problems.