survey

Collect kubectl JSON outputs into a structured infra-atlas.json for Kubernetes clusters.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Kord96/kordinate --skill survey-kord96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: survey
Source: https://github.com/Kord96/kordinate/tree/main/agents/charon/skills/survey
Command: npx skills add https://github.com/Kord96/kordinate --skill survey-kord96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cluster state is often fragmented across kubectl outputs, services, and monitoring configs, making it hard for agents and operators to get a consistent picture of what is running and what a new workload must satisfy. This Skill produces a single structured infra-atlas.json that captures nodes, namespaces, services, deployments, storage, observability, networking, and platform agent metadata so downstream tools and agents can act reliably.

Core Features & Use Cases

  • State aggregation: Collects kubectl JSON outputs for nodes, namespaces, deployments, statefulsets, services, pvcs, and optional components like kafkatopics and scaledobjects to assemble a comprehensive cluster model.
  • Change detection & efficiency: Computes a cluster state hash during preflight to skip work when nothing changed and supports a --full override to force a complete rescan.
  • Shared memory output: Writes a standardized infra-atlas.json to the agent global memory location for consumption by planning, monitoring, and deployment agents.
  • Use Case: Run the survey after infrastructure changes to update monitoring configurations, generate deployment contracts, or inform capacity planning.

Quick Start

Run the survey skill to generate or refresh infra-atlas.json in the agent global memory, adding --full to force a complete rescan.

Frequently Asked Questions about survey

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

FAQPage Schema
How do I create a single infrastructure atlas for Kubernetes cluster state?

A Kubernetes cluster inventory captures nodes, namespaces, deployments, statefulsets, services, and pvcs into a structured infra-atlas.json. This standardized model provides a single source of truth for agents and operators to understand running workloads.

How do I generate an environment inventory for k3s clusters?

You can generate a k3s environment inventory by collecting kubectl JSON outputs for resources like deployments, services, and pvcs, then writing the aggregated data as an infra-atlas.json file. This provides a comprehensive snapshot for agent awareness and deployment planning.

Does this cluster survey tool work with k3s and standard Kubernetes distributions?

Yes, this cluster survey works with k3s and similar Kubernetes clusters. It uses standard kubectl JSON outputs to collect resource data, making it compatible across environments that support these interfaces for generating the infra-atlas.json file.

What is the best way to detect infrastructure changes in a Kubernetes cluster?

The best way to detect Kubernetes infrastructure changes is by computing a RAW_STATE hash during preflight. This mechanism identifies whether cluster resources have shifted, skipping unnecessary work unless a --full override forces a complete rescan of the environment.

How do I collect Kubernetes resource data for monitoring design and deployment planning?

Collect Kubernetes resource data for monitoring and deployment planning by running a survey that aggregates kubectl JSON outputs for nodes, services, and storage. The resulting infra-atlas.json acts as a shared memory output to inform capacity planning and monitoring configurations.

When should I force a full rescan of my Kubernetes cluster resources?

Force a full rescan of Kubernetes cluster resources using the --full override when the preflight state hash indicates no changes but you need absolute certainty. This bypasses efficiency checks to completely refresh the infra-atlas.json with current cluster data.