Files
Brandon Martin 2232aae10c fix(plugins): remove unsupported manifest path fields (#7)
## Summary
- remove explicit `agents`, `skills`, and `commands` fields from
generated plugin manifests
- rely on Claude Code's standard auto-discovery for plugin-root
`agents/`, `skills/`, and `commands/` directories
- flatten packaged agents to `agents/*.md` so discovery does not depend
on nested-path recursion
- keep the fix minimal by only retaining the explicit `hooks` entry for
`cce-core`

## Why
A local plugin install failed with:

```text
Plugin has an invalid manifest file ... Validation errors: agents: Invalid input
```

Our packaged plugins already follow the standard directory structure, so
the extra manifest path fields were unnecessary and were the most likely
validator mismatch. Greptile also flagged that many generated plugin
agents were nested under paths like `agents/specialized/...`, which
could silently fail if discovery is non-recursive. This change aligns
the packages with the default plugin structure instead of relying on
special manifest fields or recursive discovery.

## Changes
- update `scripts/sync_plugin_packages.py` to stop emitting manifest
path overrides
- flatten generated packaged agents to plugin-root `agents/*.md`
- regenerate all packaged plugin manifests with minimal metadata-only
manifests
- regenerate all packaged plugin agent files into the flat standard
layout

## Verification
- `python3 scripts/sync_plugin_packages.py`
- `python3 -m py_compile scripts/sync_plugin_packages.py
install_extensions.py`
- validated all 19 generated plugin manifests as JSON
- confirmed no generated manifest still contains `agents`, `skills`, or
`commands`
- confirmed packaged agents are flat: `flat_agents=78 nested_agents=0`
2026-04-01 22:25:42 -05:00
..

CCE Kubernetes Plugin

Kubernetes cluster operations, health diagnostics, and operator-specific agents.

Overview

The cce-kubernetes plugin provides comprehensive Kubernetes support including dynamic cluster health diagnostics, kubectl operations, and operator-specific health checks for ArgoCD, Crossplane, cert-manager, and Prometheus.

Features

  • Dynamic Health Checks: API discovery detects installed operators and runs specialized diagnostics
  • Operator Support: ArgoCD, Crossplane, cert-manager, Prometheus Operator
  • kubectl Operations: Debugging, logs, describe, exec, port-forward
  • Resource Management: Deployments, services, configmaps, secrets, scaling, rollouts
  • Token-Efficient: Scripts use bash commands, not verbose tool output

Plugin Components

Agents (6)

Orchestrator:

  • k8s-health-orchestrator: Dynamic API discovery and health orchestration

Specialized Health Agents:

  • k8s-core-health-agent: Nodes, pods, deployments, services, PVCs
  • k8s-argocd-health-agent: Applications, AppProjects, ApplicationSets, sync status
  • k8s-crossplane-health-agent: Providers, compositions, claims, managed resources
  • k8s-certmanager-health-agent: Certificates, Issuers, certificate expiry
  • k8s-prometheus-health-agent: Prometheus instances, AlertManagers, ServiceMonitors

Skills (2)

  • kubernetes-operations: kubectl debugging and resource management scripts
  • kubernetes-health: Comprehensive cluster diagnostics

Commands (1)

  • /cce-kubernetes:health: Run complete cluster health assessment

Installation

# Add the CCE marketplace
/plugin marketplace add github:nodnarbnitram/claude-code-extensions

# Install Kubernetes plugin
/plugin install cce-kubernetes@cce-marketplace

From Local Source

git clone https://github.com/nodnarbnitram/claude-code-extensions.git
/plugin marketplace add /path/to/claude-code-extensions
/plugin install cce-kubernetes@cce-marketplace

Usage

Command

/cce-kubernetes:health
# Runs dynamic API discovery and comprehensive health checks
# Automatically detects ArgoCD, Crossplane, cert-manager, Prometheus

Skills (User-Invoked)

/kubernetes-operations
# Interactive kubectl operation menu (debug, logs, describe, exec, port-forward)

/kubernetes-health
# Full cluster health diagnostic

Agents (Automatic Activation)

> Check if my ArgoCD applications are healthy
# Uses k8s-argocd-health-agent

> Debug the failing deployment in namespace prod
# Uses kubernetes-operations skill

> Check certificate expiry dates
# Uses k8s-certmanager-health-agent

> Verify Crossplane managed resources are ready
# Uses k8s-crossplane-health-agent

Example Workflows

Complete Cluster Health:

/cce-kubernetes:health
# Output:
# ✅ Core resources healthy
# ✅ ArgoCD: 15 apps synced
# ⚠️  Crossplane: 2 managed resources degraded
# ✅ cert-manager: All certs valid

Debugging Pods:

> Show logs for failing pods in namespace my-app
# Uses kubectl logs with error filtering

Resource Scaling:

> Scale deployment api-server to 5 replicas
# Uses kubectl scale

Requirements

  • Claude Code: Latest version
  • kubectl: Configured with cluster access
  • Kubeconfig: Valid context for target cluster
  • Optional Operators: ArgoCD, Crossplane, cert-manager, Prometheus

Health Check Coverage

Core Resources:

  • Nodes (ready, disk pressure, memory pressure)
  • Pods (phase, restarts, readiness)
  • Deployments (replicas, conditions)
  • Services (endpoints, selector matching)
  • PersistentVolumeClaims (binding status)

ArgoCD:

  • Application sync status and health
  • AppProject quotas and restrictions
  • ApplicationSet generation status

Crossplane:

  • Provider installation and health
  • Composition definitions
  • Claims and managed resource status

cert-manager:

  • Certificate ready status
  • Issuer ready status
  • Certificate expiry warnings

Prometheus:

  • Prometheus instance status
  • AlertManager replicas
  • ServiceMonitor target discovery

License

MIT License - see LICENSE for details.

Support