[WIP] skills: Add monitoring skills (prometheus, monitoring-ops)

[harche]

Summary

• Adds monitoring/prometheus/ — Prometheus query skill using promtool, ported from cluster-version-operator/lightspeed/skills/prometheus/
• Adds monitoring/monitoring-ops/ — OpenShift monitoring stack troubleshooting skill (Prometheus, Alertmanager, Thanos), ported from cluster-monitoring-operator/lightspeed/skills/monitoring-ops/
• Adds monitoring/OWNERS and monitoring/README.md

Reviewers

These skills relate to the Cluster Monitoring Operator domain.

Test plan

• Verify prometheus SKILL.md allowed-tools includes Bash(promtool:*)
• Verify monitoring-ops SKILL.md covers Prometheus, Alertmanager, and Thanos troubleshooting flows
• Smoke-test skill loading in a Claude Code session with a live cluster

Note: These are initial drafts. They will evolve as we test and refine them based on real-world usage.

🤖 Generated with Claude Code

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: harche

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [harche]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@harche: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[falox]

CMO only seems a bit limiting. From our experience and evals, a non trivial troubleshooting skills involve multi signals and operators. IMO, the scope of the directory should be broader. The intent is more "observability", "troubleshooting", and so on.

@harche @mrunalp @iNecas @xiormeesh let me know wdyt. Then we can decide whether to expand this one or add another (to check/eval if overlapping skills will confuse the LLM...)

[iNecas]

It's not clear whether its about troubleshooting the operator, or using monitoring for troubleshooting in general. It might be worth splitting that SKILL to two:

1. troubleshooting the oprator
2. querying the in-cluster prometheus

And having something separate perhaps for wider troubleshooting scenarios (that @falox is likely referring). As of content, only evals can tell.

[harche]

@falox @iNecas thanks for this input, I don't mind closing this in favor of alternatives, I just wanted to get a conversation started around skills from individual teams.

[harche]

Also I would like to remove myself from OWNERS file, looking for the github handles from the observability team to own monitoring/observability related skills.

[falox]

I just wanted to get a conversation started around skills from individual teams.

@harche You did great, and we're happily in :) If that's okay with you, I'll clarify a couple of points using this PR thread. If necessary, I will open another PR later. Ok?

[harche]

I just wanted to get a conversation started around skills from individual teams.

@harche You did great, and we're happily in :) If that's okay with you, I'll clarify a couple of points using this PR thread. If necessary, I will open another PR later. Ok?

sounds great, again, thanks for your inputs.

[wking]

Definitely not me here 😅 Plenty of responsibilty already between the cluster-update directory and other repositories.