skills.rest
confighub
confighubOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pilot-watch-alert-response

Convert cub-scout watch events into Pilot governance verdicts for Kubernetes drift and ownership changes.

14|Updated Jan 17, 2026
Search Tags:#drift detection#kubernetes#gitops#event-driven#alerting#pilot#receipt verification
One-click install
npx skills add https://github.com/confighub/cub-scout --skill pilot-watch-alert-response
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pilot-watch-alert-response
Source: https://github.com/confighub/cub-scout/tree/main/skills/pilot-watch-alert-response
Command: npx skills add https://github.com/confighub/cub-scout --skill pilot-watch-alert-response

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams handle live Kubernetes change events by turning an incoming cub-scout watch stream into a clear per-event Pilot decision (PASS/WATCH/ASK/BLOCK) with supporting evidence.

Core Features & Use Cases

  • Event-driven acceptance kernel: Consumes the real-time cub-scout watch JSONL/webhook stream and renders a verdict per event as they fire.
  • Receipt-first fast path: Preferentially uses inline receipts emitted by cub-scout watch --emit-receipt-on (e.g., drift.detected, ownership.changed) to decide quickly without synchronous follow-up calls.
  • Evidence-backed slow path: When receipts are absent or unverifiable, fetches context using cub-scout read-only commands such as compare three-way, explain, and receipt verify to reach an evidence-complete decision.
  • Operational guardrails: Expects receipt to be optionally omitted when receipt-building is suppressed or fails, and requires consumers to check key presence rather than treating null as valid evidence.
  • Best-fit scenarios: Use during real-time deployment governance and alerting where you need immediate, audit-friendly decisions from drift and ownership change signals.

Quick Start

Use the skill by wiring Pilot to receive cub-scout watch webhook events for drift and ownership changes, and then decide PASS/WATCH/ASK/BLOCK per incoming event using the inline receipt verdict when present.

Frequently Asked Questions about pilot-watch-alert-response

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

FAQPage Schema
How do I get real-time alerts for Kubernetes and GitOps configuration drift?▼

Real-time alerts for Kubernetes and GitOps drift are generated by consuming a live watch event stream and rendering a per-event governance verdict (PASS/WATCH/ASK/BLOCK) with optional inline receipts for immediate audit-friendly decisions.

How does event-driven drift detection handle missing receipt verification data?▼

Event-driven drift detection handles missing receipts by falling back to a slow path that fetches context using read-only commands like three-way compare and explain to reach an evidence-complete decision without mutating the cluster.

Can I use inline receipts to automate GitOps ownership change governance decisions?▼

You can use inline receipts emitted by watch events to automate GitOps ownership change governance by mapping the receipt predicate verdict directly to a PASS/WATCH/ASK/BLOCK decision without synchronous follow-up calls.

What is the best way to render audit-friendly verdicts for live Kubernetes deployment changes?▼

The best way to render audit-friendly verdicts for live Kubernetes changes is to wire an event-driven acceptance kernel that processes each drift or ownership change event individually and attaches fallback evidence when receipts are absent.

Does Kubernetes drift alerting require mutating actions to reach a governance decision?▼

Kubernetes drift alerting does not require mutating actions because the governance decision is reached safely using read-only evidence gathering and receipt predicate mapping to render verdicts without modifying cluster or authority systems.

Related Skills

Explore More Software Engineering Skills→
danmestasdanmestas
4

monitoring-the-operator

Live-monitor an operator's Claude Code transcript JSONL for audit-worthy events.

Community
Advanced
agentik-osagentik-os
10

observabilityaudit

Audit end-to-end telemetry coverage across logs, traces, metrics, dashboards, and runbooks.

Community
Advanced
confighubconfighub
14

pilot-fleet-conformance

Aggregate cub-scout evidence into a fleet-wide PASS/WATCH/ASK/BLOCK conformance verdict.

Official
Advanced
I194I194
9

canary

Monitor deployed apps for console errors, performance regressions, and page failures.

Community
Advanced