k8s.controller-analyzer

Cross-check k8s-controller-analyzer mappings against skill checklists and extractors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns the k8s-controller-analyzer tool with the k8s.controller-* assessment skills, ensuring every checklist item has a corresponding extractor and every extractor maps to a checklist item.

Core Features & Use Cases

  • Validate consistency between analyzer rules and skill mappings across architecture, API, lifecycle, production readiness, and orchestrator skills.
  • Detect missing mappings, orphaned constants, and gaps in analyzer integration to maintain a single source of truth.
  • Use cases include repository-wide audits during reviews or CI checks to ensure complete coverage.

Quick Start

Run the skill against the plugin repository to verify the mapping between checklist items, extractors, and rule IDs.

Frequently Asked Questions about k8s.controller-analyzer

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

FAQPage Schema
How do I verify that Kubernetes controller analyzer extractors map correctly to checklist items?

To verify Kubernetes controller analyzer mappings, cross-check constants in consts.go, data types in types.go, extractor definitions in EXTRACTORS.md, and SKILL.md mappings to ensure every checklist item has a corresponding extractor and vice versa.

What causes orphaned constants and missing mappings in k8s controller assessment skills?

Orphaned constants and missing mappings occur when checklist items, extractors, and rule IDs across architecture, API, lifecycle, and production-readiness skills fall out of sync with the analyzer-schema.md contract references and EXTRACTORS.md definitions during repository updates.

How do I audit a k8s plugin repository for analyzer integration gaps during CI checks?

Run a repository-wide audit by cross-referencing analyzer-schema.md contract references against consts.go, types.go, EXTRACTORS.md, and SKILL.md files across all k8s.controller-* skills to reveal missing mappings, orphaned constants, and integration gaps.

When do I need to align k8s-controller-analyzer rules with assessment skills?

You need to align k8s-controller-analyzer rules with assessment skills during code reviews or CI checks when inconsistencies arise between extractor definitions, checklist items, and rule IDs across architecture, API, lifecycle, production-readiness, and orchestrator skill categories.

Does k8s controller analyzer validation work across all assessment skill categories?

Yes, k8s controller analyzer validation applies across the plugin repository's architecture, API, lifecycle, production-readiness, and assessment skills, verifying that every extractor maps to a checklist item and every checklist item has a corresponding extractor.

What limitations exist when checking analyzer contracts against k8s controller skill mappings?

The validation is limited to checking alignment between defined constants, types, extractor definitions, and skill mappings within the k8s.controller-* plugin repository, and does not extend to external analyzer rules or unsupported skill categories.