scout-govern

Retrieves read-only ConfigHub governance signals for unit history, impact, and fleet conformance.

14|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/confighub/cub-scout --skill scout-govern
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scout-govern
Source: https://github.com/confighub/cub-scout/tree/main/skills/scout-govern
Command: npx skills add https://github.com/confighub/cub-scout --skill scout-govern

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide read-only answers about who changed a Kubernetes-related unit, what that change will affect across the fleet, and what ConfigHub governance evidence says happened and when.

Core Features & Use Cases

  • ChangeSet history & audit trails: Trace a unit’s connected ChangeSet timeline and list governance audit entries for retroactive investigation and postmortems.
  • Impact and blast-radius analysis: Preview downstream dependencies and the cluster scope implied by a unit change, enabling safer decision-making before acting elsewhere.
  • Fleet conformance and connected summaries: Identify outlier clusters against a Hub View and retrieve structured connected summaries by cluster and time.
  • Connected Hub Views, bundles, and catalogs: Resolve Views into structured columns, inspect bundle/catalog state, and list historical snapshots that reflect connected governance data.

Quick Start

Ask: "Show me the ChangeSet history for unit payments-api in connected mode, including who applied the last changes and when."

Frequently Asked Questions about scout-govern

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

FAQPage Schema
How do I trace Kubernetes ChangeSet history and audit who applied configurations?▼

Trace Kubernetes ChangeSet history by retrieving connected unit timelines and governance audit entries. You can investigate retroactive postmortems by viewing exactly who applied changes to a unit and when the action occurred.

How do I analyze the blast radius of a Kubernetes configuration change across my fleet?▼

Analyze blast radius by previewing downstream dependencies and the implied cluster scope for a unit change. This impact analysis enables safer decision-making before acting elsewhere across your connected fleet.

Can I detect fleet conformance issues and identify outlier clusters against a Hub View?▼

Detect fleet conformance issues by identifying outlier clusters against a defined Hub View. You retrieve structured connected summaries filtered by cluster and time to pinpoint configuration drift and resolve anomalies.

Do I need ConfigHub authentication to inspect connected governance data and bundle state?▼

ConfigHub authentication is required to inspect connected governance data, bundle state, and historical snapshots. You must authenticate via cub auth login or set the CONFIGHUB_API_KEY environment variable for read-only access.

What are the limitations when using connected mode for governance history retrieval?▼

Connected mode is restricted to read-only evidence retrieval for governance history, impact analysis, and fleet conformance. It does not permit write actions, limiting use to audit inspection and blast-radius preview only.

How do I resolve connected Hub Views into structured columns for audit inspection?▼

Resolve connected Hub Views into structured columns to inspect bundle and catalog state. This allows you to list historical snapshots reflecting connected governance data for comprehensive cluster audit inspection.