cobalt-core
FeaturedCobalt Core infrastructure knowledge: KVM exporters, hypervisor tooling, OpenStack compute.
Install
Quality Score: 96/100
Skill Content
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
kotlin
Kotlin development: coroutines, Flow, Channels, testing with JUnit 5 and Kotest.
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.
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