cluster-intake

Evaluate component proposals for the Anton cluster against seven hard gates.

3|Updated May 13, 2025
One-click install
npx skills add https://github.com/wcygan/anton --skill cluster-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cluster-intake
Source: https://github.com/wcygan/anton/tree/main/.claude/skills/cluster-intake
Command: npx skills add https://github.com/wcygan/anton --skill cluster-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Intake gate for adding new system or infrastructure components to Anton. It ensures that every proposal declares intent (concrete need, honest learning, or both), runs a rubric-based evaluation, and returns an ADR-ready recommendation (add, defer, or reject). It is read-only by design — never scaffolds manifests or applies changes to the cluster.

Core Features & Use Cases

  • Declares intent (concrete need, honest learning, or both) to drive the appropriate rubric.
  • Applies a structured rubric that guards blast radius, reversibility, integration fit, and secrets model, then surfaces ADR-ready outcomes.
  • Hand-passes to the ADR workflow for formal decision recording and, if accepted, to the flux app scaffolding path.

Quick Start

Describe a candidate and an intent, then run through the intake rubric to determine add, defer, or reject.

Frequently Asked Questions about cluster-intake

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

FAQPage Schema
How do I evaluate whether to add a new component to a Kubernetes cluster?

Cluster intake gates evaluate new component proposals by declaring intent, applying rubric checks for blast radius and reversibility, and returning an ADR-ready summary. This ensures infrastructure changes are reviewed for containment, integration fit, and secrets before deployment.

What is an intake gate for cluster governance?

A cluster intake gate is a read-only evaluation process that frames new component proposals and enforces hard checks for containment, integration, and secrets. It outputs an ADR-ready summary recommending whether to add, defer, or reject a component.

Can I scaffold manifests directly during the cluster intake process?

No, the cluster intake gate is read-only by design and never scaffolds manifests. It evaluates proposals against hard gates and returns an ADR-ready summary, handing accepted components to a separate flux app scaffolding path.

What checks are required before adopting new infrastructure on a cluster?

Required checks include seven hard gates: five containment gates, an integration check, and a secrets check. Running these evaluations produces an ADR-ready outcome that decides whether to add, defer, or reject the component.

When should I defer adding a new component to my cluster?

Defer a component when the intake rubric identifies unresolved containment, integration, or secrets issues. The gate evaluates intent and blast radius, returning a defer recommendation in the ADR summary if risks remain unmitigated.