skills.rest
Qredence
QredenceOFFICIAL
Explore all skills by this author →
Website𝕏@agenticfleetGitHub

diagnostics

Diagnose runtime failures and observability issues in fleet-rlm using Daytona endpoints.

51|6|Updated Feb 7, 2026
Search Tags:#debugging#runtime#observability#diagnostics#websocket#daytona
One-click install
npx skills add https://github.com/Qredence/fleet-rlm --skill diagnostics-qredence
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnostics
Source: https://github.com/Qredence/fleet-rlm/tree/main/src/fleet_rlm/scaffold/skills/diagnostics
Command: npx skills add https://github.com/Qredence/fleet-rlm --skill diagnostics-qredence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Diagnostics skill helps operators identify and triage fleet-rlm runtime failures, API contract drift, sandbox issues, and observability gaps so that remediation can begin faster.

Core Features & Use Cases

  • Symptom-to-Cause Decision Tree: guides the user through common failure modes (sandbox start failures, websocket mismatches, escalation triggers, and missing traces) and provides concrete checks and recovery steps.
  • Environment & Connectivity Validation: verifies Daytona API keys, endpoints, and connectivity; surfaces actionable diagnostics for runtime health, sandboxes, and volume status.
  • Evidence-driven Troubleshooting: exposes runtime events, status changes, and escalation signals to help reduce mean time to repair and improve observability.

Quick Start

Run the diagnostics flow to determine why Daytona or WebSocket issues occur and apply the recommended fixes.

Frequently Asked Questions about diagnostics

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

FAQPage Schema
How do I diagnose runtime failures and missing traces in fleet-rlm?▼

To diagnose fleet-rlm runtime failures, you can run a diagnostics flow that traces missing observability data using a symptom-to-cause decision tree. It analyzes runtime events and status changes to surface actionable remediation steps.

Why does my Daytona connectivity fail when starting sandbox instances?▼

Daytona connectivity failures are often caused by invalid API keys or inaccessible endpoints. You can validate your Daytona environment variables and connectivity status to surface actionable diagnostics for sandbox and volume health.

How do I troubleshoot websocket contract drift across runtime sessions?▼

You can troubleshoot websocket contract drift by checking the runtime-status endpoints and analyzing exposed escalation signals. This process identifies mismatches and provides concrete recovery steps for the affected sessions.

Do I need specific environment variables to diagnose fleet-rlm observability issues?▼

Yes, diagnosing fleet-rlm observability issues requires Daytona API keys, accessible endpoints, and properly configured environment variables. These inputs are necessary to query runtime-status endpoints and generate accurate guidance.

What is the best way to handle escalate triggers during runtime troubleshooting?▼

The best way to handle escalate triggers is to use an evidence-driven troubleshooting approach that exposes runtime events. This reduces mean time to repair by mapping escalation signals to concrete recovery checks.

Related Skills

Explore More Software Engineering Skills→
open-thoughtsopen-thoughts
276

datagen-launch

Launch datagen trace-generation jobs on HPC clusters and upload trajectories to HuggingFace.

Official
Advanced
markuslebenmarkusleben
21

onboarding

Diagnose HA NOVA Relay onboarding, connectivity, and authentication failures.

Community
Basic
ArabelaTsoArabelaTso
142

security-sensitive-path-instrumenter

Add structured logging to authentication, authorization, and input-handling code paths.

Community
Intermediate
CarbeneAICarbeneAI
9

setup-deploy

Detect deployment platforms and write Deploy Configuration sections to CLAUDE.md.

Community
Intermediate