ark-controller-development
Guidance for developing the Ark Kubernetes operator. Use when modifying Go types, CRDs, controllers, or webhooks. Helps with CRD generation and Helm chart sync issues.
84
83%
Does it follow best practices?
Impact
80%
2.96xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
80%
45%Configurable Health Polling for MCPServer
CRD field addition and configurable value handling
New spec field
100%
100%
Spec field used in controller
100%
100%
No package-level interval constant
0%
0%
No inline duration literals in production code
0%
100%
Test file present
100%
100%
Test-local const for durations
0%
0%
make manifests in script
0%
100%
make lint in script
0%
100%
make build in script
0%
100%
make test in script
0%
100%
Test Coverage for MCPServer Authentication Failure Handling
Controller branch test coverage and framework selection
Ginkgo import
Failed
100%
envtest setup
Failed
100%
Happy path test
Failed
100%
Auth failure mode tested
Failed
100%
Condition Reason checked
Failed
100%
No status message string-matching
Failed
70%
Idempotency test
Failed
100%
Regression guard test
Failed
100%
Test-local const for durations
Failed
100%
Gomega assertions
Failed
100%
80%
60%Status Update Retry Helper for Ark Controller
Leverage existing libraries and avoid reimplementation
Uses existing dependency
100%
100%
No hand-rolled retry loop
0%
100%
Type alias over parallel struct
0%
100%
Stdlib testing for helper
0%
100%
Table-driven tests
0%
0%
Timeout as parameter
0%
50%
No inline duration literals
0%
100%
Design decisions doc
50%
100%
- Repository
- mckinsey/agents-at-scale-ark
- Commit
fc5746e
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.