cobalt-core

Featured

Cobalt Core infrastructure knowledge: KVM exporters, hypervisor tooling, OpenStack compute.

AI & Automation 412 stars 42 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
87
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Cobalt Core Domain skill for the [cobaltcore-dev](https://github.com/cobaltcore-dev) project family — SAP Converged Cloud infrastructure components for KVM hypervisor management, metrics collection, and compute-node tooling. ## Reference Loading Table | 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 | **Loading rule.** Read the references whose signals match the task before responding. --- ## Phase 1: IDENTIFY 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. --- ## Phase 2: RESPOND Use loaded reference knowledge to answer the user's question. The references contain: - Architecture and data flow diagrams - Complete metric catalogs w...

Details

Author
notque
Repository
notque/vexjoy-agent
Created
4 months ago
Last Updated
3 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

kotlin

Kotlin development: coroutines, Flow, Channels, testing with JUnit 5 and Kotest.

412 Updated 3 days ago
notque
Data & Documents Listed

core-data-expert

Expert Core Data guidance (iOS/macOS) covering stack setup, fetch requests & NSFetchedResultsController, saving/merge conflicts, threading & Swift Concurrency, batch operations & persistent history, migrations, performance, and NSPersistentCloudKitContainer/CloudKit sync. Use when setting up a Core Data stack, debugging threading/concurrency crashes, resolving NSMergeConflict or constraint violations, planning a schema migration, integrating CloudKit sync, or diagnosing Core Data performance/memory issues.

1 Updated today
patrickserrano
AI & Automation Listed

kg-core

Knowledge Graph — persistent memory, your twin across sessions. Memory usually arrives PRELOADED: a "KG MEMORY PRELOADED" block carrying the session_id — follow its directive (one full kg_read before substantive work). No block? Then the full read is on you: kg_read(cwd="<project root>") comes before substantive work, whatever the task. Then live in the graph while you work: recall before rediscovering — reading beats re-deriving; capture at the moment of learning — whatever cost effort to gain; connect rather than duplicate — an edge beats a new node; search below the surface — the render shows the top of a grown graph, not all of it. In a rich, long-lived graph the fact you need is often buried under fresher work; kg_search reaches every tier. Gauge by the graph's age and size: near-empty means little to find, mature means the answer is likely there, just not on the surface. And a node found when truly needed earns the usefulness credit that keeps it alive. Mechanics live in the kg_* tool descriptions; oper

4 Updated today
mironmax