fix-broken-juju-k8s

Diagnose and recover wedged Juju controllers, Kubernetes clusters, or concierge environments.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/tonyandrewmeyer/cantrip --skill fix-broken-juju-k8s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-broken-juju-k8s
Source: https://github.com/tonyandrewmeyer/cantrip/tree/main/src/cantrip/skills/fix-broken-juju-k8s
Command: npx skills add https://github.com/tonyandrewmeyer/cantrip --skill fix-broken-juju-k8s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and recover a wedged Juju controller, k8s/microk8s cluster, or stuck concierge environment on a dev machine.

Core Features & Use Cases

  • Guided diagnostic sweep and reproducible recovery path for dev machines where Juju, Kubernetes, or concierge services hang or fail to respond.
  • Safe rebuild workflow using concierge restore and prepare to restore a clean, usable development environment.
  • Clear escalation steps with exact commands when destructive actions are required, reducing guesswork during outages.

Quick Start

Describe your wedged Juju or Kubernetes dev environment and trigger the recovery workflow.

Frequently Asked Questions about fix-broken-juju-k8s

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

FAQPage Schema
Why does my concierge environment get stuck and fail to respond during local development?

If your Kubernetes cluster fails to start in a concierge environment, run prerequisite checks and a diagnostic sweep to isolate the hang, then execute a controlled purge path to clear stuck services before rebuilding.

What is the best way to recover an unreachable Juju controller without manual troubleshooting guesswork?

You can safely purge and rebuild a broken microk8s cluster by following a controlled purge path with exact escalation commands, ensuring destructive actions are isolated to the stuck Kubernetes environment.

How do I fix a wedged Juju controller on my development machine?

The best way to recover an unreachable Juju controller is using a reproducible recovery path that applies diagnostic sweeps, exact escalation commands for destructive actions, and guided concierge restore workflows.

Can I safely purge and rebuild a broken microk8s cluster without losing dev machine data?

This recovery workflow targets development workstation scenarios running k8s or microk8s clusters through concierge, focusing on local dev machine environments rather than production Kubernetes deployments.

Does this recovery workflow support any Kubernetes distribution or just microk8s dev environments?

You should avoid a full purge when your wedged Juju or Kubernetes environment can be resolved by prerequisite checks or a diagnostic sweep, saving the destructive purge path for completely unresponsive clusters.