AGENT SKILL

crossplane-specialist

Deep-dive Crossplane platform review: XRD design, Composition correctness, provider config audit, managed resource health, and GitOps integration. Use for structured investigations of stuck Claims, composition pipeline bugs, and credential injection patterns. Triggers on: "Crossplane audit", "XRD review", "Composition debug", "stuck Claim", "managed resource stuck", "provider config review", "Crossplane GitOps".

使用场景视觉设计
License 许可
MIT
最近更新
2026-10-26
Stars
★ 0
Forks
0

01 前言 Front Matter

name
crossplane-specialist
description
Deep-dive Crossplane platform review: XRD design, Composition correctness, provider config audit, managed resource health, and GitOps integration. Use for structured investigations of stuck Claims, composition pipeline bugs, and credential injection patterns. Triggers on: "Crossplane audit", "XRD review", "Composition debug", "stuck Claim", "managed resource stuck", "provider config review", "Crossplane GitOps".
allowed-tools
Read Grep Glob Bash
argument-hint
<XRD name, Claim name, or problem description>

02 资源文件 5

03 SKILL.md 正文

Crossplane Specialist

Structured investigation for Crossplane-based infrastructure platforms. Five phases: gather context, diagnose, design, recommend, verify.

Arguments

  • $0 — XRD name, Claim name, or problem description. Required.

Phase 1: Context Gathering

  1. List installed providers and packages:
    kubectl get providers
    kubectl get configurations
    kubectl get functions
    
  2. List XRDs and their ready status:
    kubectl get xrd
    
  3. List Claims and Composites:
    kubectl get composite --all-namespaces
    kubectl get claim --all-namespaces
    
  4. Glob for Crossplane manifests in the working directory:
    find . -name "*.yaml" | xargs grep -l "apiVersion: apiextensions.crossplane.io" | sort
    

Phase 2: Diagnosis

Stuck Claim / Composite trace:

kubectl describe claim <name> -n <namespace>
kubectl describe composite <name>
kubectl get managed --all-namespaces | grep -v "True"
kubectl describe <managed-resource-kind> <name>

Provider health:

kubectl describe provider <name>
kubectl get providerconfig
kubectl describe providerconfig <name>

Composition pipeline:

kubectl get composition <name> -o yaml
kubectl get function --all-namespaces

Phase 3: Design / Root-Cause Analysis

Map symptoms to causes:

Symptom Common Causes Check
Claim stuck Waiting Composite not ready, no matching Composition kubectl describe composite → events
Managed resource NotFound Wrong external-name annotation, ID mismatch Provider docs for external-name format
Provider Unhealthy Bad credentials, missing ProviderConfig kubectl describe provider events
Composition patch fails Wrong fromFieldPath, type mismatch kubectl get composite -o yaml patched fields
Function pipeline error Function pod crash, malformed FunctionIO kubectl logs -n crossplane-system function
Deletion stuck (finalizer) Managed resource Delete policy, cloud resource busy Check deletion policy + cloud console

Cite kind:name or file:line for every finding.


Phase 4: Recommendations

Output findings in priority order:

[CRITICAL] <title>
Resource: <kind:name or file:line>
Issue: <one sentence>
Evidence: <kubectl output or config snippet>
Fix: <specific change, with YAML diff if applicable>
Trade-off: <alternative and its downside, if meaningful>

Order: CRITICAL → WARNING → INFO.


Phase 5: Verification

After fixes are applied:

  1. kubectl get composite <name> — READY: True, SYNCED: True.
  2. kubectl get managed — all managed resources show READY: True.
  3. kubectl describe claim <name> — no error events.
  4. kubectl apply --dry-run=server -f composition.yaml — no schema errors.
  5. If deletion policy changed: confirm behavior by deleting a test Claim in a non-prod environment.

Reference Docs

File When to use
xrd-design.md XRD schema design, versioning, validation rules
compositions.md Composition patch-and-transform, pipeline mode, Functions
provider-configs.md Credential injection, ProviderConfig patterns
managed-resources.md External-name, deletion policy, resource lifecycle
gitops-integration.md Argo CD / Flux health checks, package management

04 同仓库更多 Skills

kaiohenricunha
kaiohenricunha/dotbabel

yolo

Start temporary autonomy for the current task or an explicit scope with a required --for expiry. Codex permits scoped pushes, merges, deploys, and releases after strict testing and validation; Full access is a separate runtime setting. Claude Code uses a session permission hook with a protected-action denylist.

开发工程师
★ 0
kaiohenricunha
kaiohenricunha/dotbabel

veracity-audit

Audit a data pipeline for Veracity and Value. Dispatches data-scientist, compliance-auditor, and data-engineer agents with project context injected at dispatch time. All source paths are supplied via flags — no defaults, no project assumptions. Subcommands: audit (full pipeline walk), score-check (scoring math only), gate-check (gate coverage only), source-trace <label> (single source end-to-end). Invoke when: "audit pipeline", "veracity check", "scoring math correct?", "check gates", "trace source", "verify quality gates", "formula correct?".

律师与法务Skill与智能体开发
★ 0
kaiohenricunha
kaiohenricunha/dotbabel

validate-spec

Audit an already-implemented spec against the codebase. Walks each constraint (ARCH-N, PERF-N, KD-N, etc.) and acceptance criterion, grounds findings in file:line evidence, runs the spec.json acceptance_commands, and writes a single audit doc to docs/audits/. Use whenever the user asks to "validate a spec", "audit a spec", "check if spec is implemented", "verify the spec is done", "is this spec really done", or otherwise wants closure on spec-driven work. Read-only against the spec — produces an audit, never modifies the spec itself.

★ 0
kaiohenricunha
kaiohenricunha/dotbabel

terragrunt-specialist

Deep-dive Terragrunt hierarchy review, DRY pattern audits, and run-all orchestration analysis. Use for structured investigations of multi-environment Terragrunt layouts, dependency graphs, remote state config, and hook correctness. Triggers on: "Terragrunt audit", "run-all review", "dependency block", "DRY pattern review", "env hierarchy audit", "mock_outputs", "terragrunt hooks".

运维与部署
★ 0
kaiohenricunha
kaiohenricunha/dotbabel

terraform-specialist

Deep-dive Terraform architecture review, module design, state management, and migration. Use for structured investigations of Terraform workspaces, provider configuration, module coupling, import workflows, and test coverage. Triggers on: "Terraform audit", "module review", "state management", "Terraform import", "workspace design", "provider config review", "Terraform testing".

测试与质量运维与部署
★ 0
kaiohenricunha
kaiohenricunha/dotbabel

spec

Create structured engineering specs through interactive pairing. Use when the user wants to create a spec, design doc, technical specification, architecture document, RFC, or engineering plan. Triggers on "let's spec this out", "create a spec", "design doc", "write a technical plan", "plan the architecture". Works for greenfield and brownfield projects. Outputs to docs/specs/.

设计师视觉设计
★ 0