grafana
Skill0 starsChanged 4 months agoMITView on GitHub
Grafana Cloud + IRM/OnCall access for the <org> stack. Covers token resolution, stack/IRM/OnCall API auth, and recipes for listing alert groups, alert payloads, and plugin settings. Use when working with Grafana Cloud, IRM, OnCall, alert groups, or anything under <stack>.grafana.net.
- Sends data out
8 other projects use a version of this.
Adopted by
Most recently taken up by
- chenwei791129/agent-skillstheir own version, first seen Oct 19, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- NVIDIA/AI-Factory-Operations-Agenttheir own version, first seen Oct 13, 2026
- mattstruble/skillstheir own version, first seen Jul 22, 2026
- magnus919/agent-skillstheir own version, first seen Jul 21, 2026
- addxai/enterprise-harness-engineeringtheir own version, first seen Apr 17, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- magnus919/agent-skills★ 177same name
- addxai/enterprise-harness-engineering★ 44same name
- NVIDIA/AI-Factory-Operations-Agent★ 41same name
- G1Joshi/Agent-Skills★ 15same name
- koderover/devops-skills★ 7same name
- mattstruble/skills★ 3same name
- ffsshhttiikk/opencode-agents-skills★ 2same name
- chenwei791129/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- atddSkill
- brainstormingSkill
- ghSkill
- issueSkill
- linearSkill
- matter-cliSkill
- obsidianSkill
- ponytailSkill
- skill-creatorSkill
- slack-cliSkill
- slack-styleSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- tuxedoSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 44
Always curl -sS -o <file> ...
- Very specific: line 108
Use Bearer SA token vs $STACK_URL/api/...:
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Grafana Cloud / IRM / OnCall Access
Active stack: <stack>.grafana.net (instance ID <INSTANCE_ID>).
Old stack terraform/grafana/<org>/ is deprecated — never modify.
SoT for tokens/IDs: terraform/grafana/<stack>-monitoring/ outputs.
Token Selection
| Need | Token | Header |
Grafana stack API (/api/... on <stack>.grafana.net) | grafana_sa_token (TF output) | Authorization: Bearer <token> |
OnCall API (<oncall-host>.grafana.net) | grafana_sa_token | Authorization: <token> (no Bearer) + X-Grafana-Instance-ID: <INSTANCE_ID> |
| Cloud Provider/Stack mgmt (rare) | GRAFANA_CLOUD_ACCESS_POLICY_TOKEN (env, set by zshrc) | Authorization: Bearer <token> |
Pitfall: GRAFANA_CLOUD_ACCESS_POLICY_TOKEN returns 401 on stack/IRM/OnCall API. Always use SA token from TF output for those.
Bootstrap (every session)
cd /path/to/terraform/infrastructure/terraform/grafana/<stack>-monitoring
terraform init -input=false -backend=true >/dev/null # first time only
SA_TOKEN=$(terraform output -raw grafana_sa_token)
INSTANCE_ID=$(terraform output -raw grafana_instance_id) # <INSTANCE_ID>
STACK_URL=$(terraform output -raw stack_url) # https://<stack>.grafana.net
ONCALL_URL=$(terraform output -raw oncall_api_url) # https://<oncall-host>.grafana.net/oncallOther useful outputs:
service_account_cicd_id— CI/CD SA idfolder_uids— Applications / Infrastructure / On-Callteam_ids— engineering / platformgmp_datasource_uid,vm_prometheus_datasource_uid,vlogs_datasource_uidoncall_webhook_url/oncall_test_webhook_url(sensitive)
Curl Pitfalls
rtktee truncates large bodies in stdout — write to file with-o /tmp/x.json, thenjqthe file.- Always
curl -sS -o <file> ...for JSON > ~5KB. - OnCall:
Authorization: <token>(noBearer). - Stack:
Authorization: Bearer <token>.
Recipes
Verify IRM plugin enabled
curl -sS -H "Authorization: Bearer $SA_TOKEN" "$STACK_URL/api/plugins/grafana-irm-app/settings" -o /tmp/irm.json
jq '{id, enabled, version: .info.version}' /tmp/irm.jsonList firing alert groups (state=new)
OnCall states: new (firing), acknowledged, resolved, silenced. There is no firing value — use new.
curl -sS -o /tmp/ag.json \
-H "Authorization: $SA_TOKEN" -H "X-Grafana-Instance-ID: $INSTANCE_ID" \
"$ONCALL_URL/api/v1/alert_groups/?state=new&per_page=100"
jq '{count, results: [.results[] | {id, title, alerts_count, created_at, integration_id, route_id}]}' /tmp/ag.jsonAll alert groups (paginated)
curl -sS -o /tmp/ag.json \
-H "Authorization: $SA_TOKEN" -H "X-Grafana-Instance-ID: $INSTANCE_ID" \
"$ONCALL_URL/api/v1/alert_groups/?per_page=50"Response: {count, next, previous, results: [...]}. Follow next until null.
Alert payload for a group
AG_ID=IQR1MC88VE2RY
curl -sS -o /tmp/al.json \
-H "Authorization: $SA_TOKEN" -H "X-Grafana-Instance-ID: $INSTANCE_ID" \
"$ONCALL_URL/api/v1/alerts/?alert_group_id=$AG_ID"
jq '.results[0].payload | {alertname: .labels.alertname, summary: (.commonAnnotations.summary // .annotations.summary // .summary), status, labels}' /tmp/al.jsonAcknowledge / Resolve / Silence
# Ack
curl -sS -X POST -H "Authorization: $SA_TOKEN" -H "X-Grafana-Instance-ID: $INSTANCE_ID" \
"$ONCALL_URL/api/v1/alert_groups/$AG_ID/acknowledge/"
# Resolve
curl -sS -X POST -H "Authorization: $SA_TOKEN" -H "X-Grafana-Instance-ID: $INSTANCE_ID" \
"$ONCALL_URL/api/v1/alert_groups/$AG_ID/resolve/"
# Silence (e.g. 3600s)
curl -sS -X POST -H "Authorization: $SA_TOKEN" -H "X-Grafana-Instance-ID: $INSTANCE_ID" \
-H "Content-Type: application/json" -d '{"delay":3600}' \
"$ONCALL_URL/api/v1/alert_groups/$AG_ID/silence/"List integrations / routes / escalation chains
curl -sS -H "Authorization: $SA_TOKEN" -H "X-Grafana-Instance-ID: $INSTANCE_ID" \
"$ONCALL_URL/api/v1/integrations/?per_page=100" -o /tmp/int.json
jq '.results[] | {id, name, type, team_id}' /tmp/int.json
curl -sS -H "Authorization: $SA_TOKEN" -H "X-Grafana-Instance-ID: $INSTANCE_ID" \
"$ONCALL_URL/api/v1/escalation_chains/?per_page=100" -o /tmp/esc.jsonStack-side (managed alerting / contact points / dashboards)
Use Bearer SA token vs $STACK_URL/api/...:
# Folders
curl -sS -H "Authorization: Bearer $SA_TOKEN" "$STACK_URL/api/folders" -o /tmp/f.json
# Datasources
curl -sS -H "Authorization: Bearer $SA_TOKEN" "$STACK_URL/api/datasources" -o /tmp/ds.json
# Provisioned alert rules
curl -sS -H "Authorization: Bearer $SA_TOKEN" "$STACK_URL/api/v1/provisioning/alert-rules" -o /tmp/rules.json
# Contact points
curl -sS -H "Authorization: Bearer $SA_TOKEN" "$STACK_URL/api/v1/provisioning/contact-points" -o /tmp/cp.jsonNote: Per repo memory, Grafana Cloud has 0 native managed alert rules / 0 contact points — all alerting flows through Alertmanager → OnCall integrations (gke_alerts C1AFKGSBQ3ELV, eks_common_alerts CPFY985N3P8UQ).
Known Integration IDs
| Integration | ID | Cloud |
gke_alerts | C1AFKGSBQ3ELV | GCP |
eks_common_alerts | CPFY985N3P8UQ | AWS |
UI Links
- Stack: https://
<stack>.grafana.net - IRM Alert Groups: https://
<stack>.grafana.net/a/grafana-irm-app/alert-groups - OnCall (legacy app path): https://
<stack>.grafana.net/a/grafana-oncall-app/
Layer Map
terraform/grafana/<stack>-monitoring/— active Mumbai stack (dashboards, datasources, OnCall, SAs, folders, teams, SSO).terraform/grafana/<org>/— deprecated/broken, do not modify.- Decomposition plan:
context/plans/2026-03-05-alerting-decomposition.md(per-cluster monitoring + per-app layers).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

