Cobalt Core infrastructure knowledge: KVM exporters, hypervisor tooling, OpenStack compute.
Domain skill for the cobaltcore-dev project family — SAP Converged Cloud infrastructure components for KVM hypervisor management, metrics collection, and compute-node tooling.
| Signal | Reference | Size |
|---|---|---|
| kvm-exporter, metrics, prometheus, libvirt, hypervisor, collector, scrape, steal time, NUMA, cgroups, cloud hypervisor | references/kvm-exporter.md | ~800 lines |
| goroutine, concurrency, semaphore, TryLock, sync.Map, race condition, socket exhaustion, scrape overlap, ClearScrapeCache | references/concurrency-patterns.md | ~200 lines |
| test, mock, moq, unit test, E2E, Kind cluster, race detector, interface_mock_gen, test-metrics.sh | references/testing-patterns.md | ~200 lines |
Load greedily. If the user's question touches any signal keyword, load the matching reference before responding. Multiple signals matching = load all matching references.
Determine which cobaltcore component the user is asking about.
| Component | Repository | Reference |
|---|---|---|
| KVM Exporter | cobaltcore-dev/kvm-exporter | references/kvm-exporter.md |
If the component is not listed, tell the user no reference exists yet and offer to analyze the repo.
Gate: Component identified. Reference loaded. Proceed to Phase 2.
Use loaded reference knowledge to answer the user's question. The references contain:
For implementation questions involving Go code, pair with the go-patterns skill for language-specific patterns. For Prometheus/Grafana questions, pair with prometheus-grafana-engineer. For Kubernetes deployment questions, pair with kubernetes-helm-engineer.
Gate: Question answered with reference-backed specifics, not generic advice.
When the user wants to add a new cobaltcore repo:
references/{repo-name}.mdFollow the structure established in references/kvm-exporter.md for consistency.