kumo-skills-catalog

Iterate on a written artifact (doc, design spec, RFC, runbook) using inline `annotate:` markers as a review channel. Defines a stable protocol for first-pass replies, follow-ups, resolution, and promotion of inline answers into the document body — so the user can review by editing the doc directly and the agent's behavior is predictable across rounds.

Investigate AWS cost surges or anomalies on the Kumo SaaS account using the CUR (Cost and Usage Report) in Athena. Use when the user reports a billing spike, month-over-month cost increase, needs a "where is the money going" breakdown, or wants to track cost per customer/nodepool/environment. Read-only — never mutates AWS resources.

Walk through a GitHub PR for learning purposes — explaining code, answering inline comments, generating diagrams, and demonstrating bugs with runnable scripts.

Scaffold a new VPC/BYOC customer workspace from scratch. Creates repo structure, generates all config files, clones child repos, and registers in Notion.

Use when a coding agent needs to tune and run an end-to-end Kumo workflow with the Kumo SDK, including data connection, graph creation, predictive query validation, training, model-plan iteration, prediction, and reporting concrete outputs.

Use when a coding agent needs to use KumoRFM to translate natural-language prediction requests into valid queries, inspect relational schema, construct or repair the graph, run instant predictions or evaluations, and return concrete outputs.

Sync the workspace's Notion page content into a local notion-context/ directory so Claude Code has full customer context without needing live API access. Idempotent — safe to run repeatedly.

File a feature-request issue in the current VPC workspace repo, linked to an upstream kumo-ai/kumo issue. Use when the user wants to request a new feature, enhancement, or capability for a VPC/BYOC deployment.

Diagnose Temporal health in a BYOC cluster — query workflows by status, analyze timeouts and failures, check resource utilization, and surface performance problems. Use when the user reports workflow timeouts, failures, latency, pod restarts, or asks about Temporal cluster health.

Manage GitHub issues using the gh CLI — create, assign, and organize parent/child (sub-issue) relationships. Use when the user asks to create tickets, reparent issues, flatten hierarchies, or manage issue relationships.

This skill should be used when the user reports pod connectivity issues, timeout errors reaching external endpoints, "connection timed out", "max retries exceeded", or network problems from within Kubernetes pods.