k8s.controller-api

Analyze Kubernetes CRD definitions and API types for API convention conformance.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/lburgazzoli/claude-plugins --skill k8s-controller-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s.controller-api
Source: https://github.com/lburgazzoli/claude-plugins/tree/main/skills/k8s.controller-api
Command: npx skills add https://github.com/lburgazzoli/claude-plugins --skill k8s-controller-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review Kubernetes CRD definitions, API types, webhooks, and kubebuilder markers for compliance with upstream Kubernetes API conventions.

Core Features & Use Cases

  • Static analysis of CRD structure, API types, markers, and webhook configurations to verify alignment with Kubernetes conventions.
  • Deterministic evaluation via the analyze_controller MCP tool to produce a structured manifest and fact set for audit.
  • Suitable for Go controllers using controller-runtime and kubebuilder patterns, across single or multi-version CRDs with webhooks.

Quick Start

Provide the repository scope and run the analyzer to generate a conformance report.

Frequently Asked Questions about k8s.controller-api

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

FAQPage Schema
How do I check my Kubernetes CRD definitions for upstream API convention compliance?

To check Kubernetes CRD definitions for API convention compliance, you can statically analyze your Go controller's API types, webhooks, and kubebuilder markers against upstream Kubernetes standards. This generates a structured manifest and fact set for audit and remediation.

Does static analysis work with multi-version CRDs built using kubebuilder?

Yes, static analysis works with multi-version CRDs built using kubebuilder patterns. The analyzer evaluates single or multi-version CRD structures and webhook configurations to verify alignment with upstream Kubernetes API conventions.

How do I audit kubebuilder markers and webhooks for Kubernetes conformance?

You audit kubebuilder markers and webhooks for Kubernetes conformance by running a deterministic static analyzer over your repository scope. This process inspects API types and webhook configurations, producing a structured evidence envelope for review.

What is the best way to verify controller-runtime API types against Kubernetes conventions?

The best way to verify controller-runtime API types against Kubernetes conventions is using a dedicated static analysis tool. It deterministically evaluates your CRD structure and markers, outputting a structured manifest and fact set for audit.