514-debug
514 Deployment Debugging
Diagnose issues in a 514/Moose deployment using the CLI's observability commands. The sections below are independent — jump to whichever is relevant.
Command shape: 514 <resource> <action> [args] [flags]
All commands accept --json for machine-readable output.
1. Deployment Status
Check whether the deployment is healthy.
List deployments:
514 deployment list --project <ORG/PROJECT> --json
More from 514-labs/agent-skills
clickhouse-best-practices-ts-py
Use when designing, implementing, reviewing, or optimizing MooseStack data models, ClickHouse schemas, queries, indexes, materialized views, or ingestion configs — including during greenfield authoring when schema-design or performance choices need guidance. When invoked, pick the 1-2 rules directly relevant to the immediate decision and apply them inline while you continue to write code. Do NOT pause to read six rule files and emit a "Rules Checked / Findings" audit template unless the user explicitly asks for a formal review or audit.
19514-cli
>
5514-perf-optimize
>
4moose-basics
>
3moosestack-clickhouse-best-practices
MUST USE when reviewing MooseStack data models, ClickHouse schemas, queries, or configurations. Contains 28 rules with MooseStack TypeScript/Python examples. Always read relevant rule files and cite specific rules in responses.
3514-production-rollout-plan
>
1