514-debug

Diagnose 514/Moose deployment issues through status checks, log inspection, and ClickHouse queries.

3|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/514-labs/agent-skills --skill 514-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 514-debug
Source: https://github.com/514-labs/agent-skills/tree/main/skills/514/debug
Command: npx skills add https://github.com/514-labs/agent-skills --skill 514-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses issues in 514/Moose deployments by guiding deployment observability tasks, including status checks, log inspection, and diagnostic queries.

Core Features & Use Cases

  • Deployment status checks and health assessment
  • Log tails and query metrics for fast root-cause analysis
  • Resource inspection and ad-hoc ClickHouse diagnostics to validate deployments

Quick Start

Tell the agent to diagnose a deployment by listing status, tailing logs, and running a diagnostic ClickHouse query.

Frequently Asked Questions about 514-debug

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

FAQPage Schema
How do I diagnose issues in a Moose deployment?

Diagnose Moose deployment issues by running status checks, tailing logs, and inspecting query metrics. This workflow structures safe diagnostic routines to identify root causes across deployment health, logs, and ClickHouse queries.

What is the best way to check deployment health and inspect logs for 514 stacks?

Checking 514 deployment health involves listing status, tailing logs, and running ad-hoc ClickHouse diagnostic queries to validate resource inventories and pinpoint root causes rapidly.

Can I run diagnostic SQL queries against ClickHouse during deployment troubleshooting?

Yes, you can run diagnostic SQL queries against ClickHouse during troubleshooting. The workflow guides ad-hoc query execution to inspect metrics and validate deployment resources for root-cause analysis.

Does the diagnostic workflow require specific tools or dependencies to inspect observability data?

No specific dependencies are required. The diagnostic workflow uses tool-agnostic commands and deterministic routines to guide status checks, log inspection, and query metrics safely across deployments.

Why are my 514 deployment diagnostics not identifying the root cause?

Diagnostics may miss root causes if you skip query metrics or resource inventories. Ensure you run the full workflow: status checks, log tails, and ClickHouse diagnostic SQL to validate the deployment comprehensively.