Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

troubleshoot-flux

Étoiles0

Forks0

Mis à jour11 juillet 2026 à 11:55

Troubleshoot Flux, HelmRelease, Kustomization, and Kubernetes deployment issues in this repository. Use when diagnosing failed reconciliation, pod errors, HelmRelease timeouts, variable substitution failures, or other GitOps deployment problems.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

alecsg77

alecsg77/elysium

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Administrateurs de réseaux et de systèmes informatiquesProfessions informatiques et mathématiques·SOC 15-1244

SKILL.md

readonly

name	troubleshoot-flux
description	Troubleshoot Flux, HelmRelease, Kustomization, and Kubernetes deployment issues in this repository. Use when diagnosing failed reconciliation, pod errors, HelmRelease timeouts, variable substitution failures, or other GitOps deployment problems.

Troubleshoot Flux

When To Use

Use this skill for on-demand diagnostics of Flux or Kubernetes deployment failures.
Use it when the user provides a failing resource, namespace, issue number, or error message.
Prefer the Troubleshooter agent when the investigation needs a dedicated diagnostic mode, multi-stage issue workflow, or follow-on coordination handoff.

Diagnostic Flow

Start from the most concrete anchor available.
Verify Flux health and identify the first failing control point.
Separate root cause from cascading symptoms.
Summarize evidence, likely cause, and the next corrective workflow.
When a GitHub issue workflow is needed, hand off to Issue Coordinator or use the documented web troubleshooting flow.

Boundaries

Stay read-only unless the user explicitly changes mode or asks for implementation.
Redact secrets, tokens, kubeconfig data, and private network details.
Prefer the smallest diagnostic snippet that proves the failure.

References

/docs/troubleshooting/web-troubleshooting.md
/docs/troubleshooting/known-issues.md
/docs/security/secure-troubleshooting.md
.github/instructions/flux.instructions.md
.github/instructions/kubernetes.instructions.md

Plus depuis ce dépôt

même dépôt

coder-templates

alecsg77/elysium

Creates and updates Coder Registry workspace templates with agent setup, infrastructure provisioning, and module consumption

2026-07-110

deploy-application

alecsg77/elysium

Deploy a new application to this Flux GitOps cluster. Use when asked to add an app, scaffold base and overlay manifests, choose a Helm chart, wire ingress, or prepare deployment validation.

2026-07-110

generate-gitops-docs

alecsg77/elysium

Generate or update GitOps documentation for this repository. Use when asked to write application READMEs, runbooks, architecture notes, troubleshooting guides, or other docs tied to apps, infrastructure, monitoring, or cluster operations.

2026-07-110

gitops-implementation-planning

alecsg77/elysium

Create implementation plans for new applications, infrastructure changes, refactors, or rollout work in this GitOps repository. Use when the user asks for a plan, architecture impact, sequencing, dependencies, validation, or rollback steps before implementation.

2026-07-110

knowledge-base-search

alecsg77/elysium

Search historical GitHub issues and local troubleshooting docs for reusable fixes. Use when asked whether an incident happened before, when looking for similar failures, or when ranking likely known fixes before deeper diagnostics.

2026-07-110

manage-sealed-secrets

alecsg77/elysium

Create, rotate, and wire Bitnami Sealed Secrets for this GitOps repository. Use when asked to add a secret, rotate credentials, seal secret values, or connect secret data to Flux and application manifests.

2026-07-110

name	troubleshoot-flux
description	Troubleshoot Flux, HelmRelease, Kustomization, and Kubernetes deployment issues in this repository. Use when diagnosing failed reconciliation, pod errors, HelmRelease timeouts, variable substitution failures, or other GitOps deployment problems.

Troubleshoot Flux

When To Use

Use this skill for on-demand diagnostics of Flux or Kubernetes deployment failures.
Use it when the user provides a failing resource, namespace, issue number, or error message.
Prefer the Troubleshooter agent when the investigation needs a dedicated diagnostic mode, multi-stage issue workflow, or follow-on coordination handoff.

Diagnostic Flow

Start from the most concrete anchor available.
Verify Flux health and identify the first failing control point.
Separate root cause from cascading symptoms.
Summarize evidence, likely cause, and the next corrective workflow.
When a GitHub issue workflow is needed, hand off to Issue Coordinator or use the documented web troubleshooting flow.

Boundaries

Stay read-only unless the user explicitly changes mode or asks for implementation.
Redact secrets, tokens, kubeconfig data, and private network details.
Prefer the smallest diagnostic snippet that proves the failure.

References

/docs/troubleshooting/web-troubleshooting.md
/docs/troubleshooting/known-issues.md
/docs/security/secure-troubleshooting.md
.github/instructions/flux.instructions.md
.github/instructions/kubernetes.instructions.md