[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"org-grafana":3,"repo-skills-v-0-3-0":184},{"org":4,"repos":57},{"slug":5,"name":6,"logoUrl":7,"githubOrg":5,"website":8,"skillCount":9,"repoCount":10,"topRepos":11,"topTags":27,"lastUpdatedAt":56},"grafana","Grafana","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fgrafana.jpg","https:\u002F\u002Fgrafana.com",80,7,[12,15,18,21,24],{"name":13,"skillCount":14},"grafana\u002Fskills",48,{"name":16,"skillCount":17},"grafana\u002Fgcx",24,{"name":19,"skillCount":20},"grafana\u002Fai-marketplace",3,{"name":22,"skillCount":23},"grafana\u002Fgrafana-infinity-datasource",2,{"name":25,"skillCount":26},"grafana\u002Ffaro-web-sdk",1,[28,29,32,35,38,41,44,47,50,53],{"slug":5,"name":6},{"slug":30,"name":31},"observability","Observability",{"slug":33,"name":34},"monitoring","Monitoring",{"slug":36,"name":37},"performance","Performance",{"slug":39,"name":40},"debugging","Debugging",{"slug":42,"name":43},"testing","Testing",{"slug":45,"name":46},"cli","CLI",{"slug":48,"name":49},"deployment","Deployment",{"slug":51,"name":52},"engineering","Engineering",{"slug":54,"name":55},"operations","Operations","2026-07-31T05:53:53.576347",[58,76,92,111,136,154,167],{"name":59,"fullName":13,"repoUrl":60,"skillCount":14,"stars":61,"forks":62,"description":63,"topics":64,"topTags":65,"topTagCount":74,"lastUpdatedAt":75},"skills","https:\u002F\u002Fgithub.com\u002Fgrafana\u002Fskills",189,16,null,[],[66,67,68,69,70,73],{"slug":5,"name":6},{"slug":30,"name":31},{"slug":36,"name":37},{"slug":33,"name":34},{"slug":71,"name":72},"metrics","Metrics",{"slug":42,"name":43},58,"2026-07-25T05:30:52.497271",{"name":77,"fullName":16,"repoUrl":78,"skillCount":17,"stars":79,"forks":80,"description":81,"topics":82,"topTags":83,"topTagCount":80,"lastUpdatedAt":56},"gcx","https:\u002F\u002Fgithub.com\u002Fgrafana\u002Fgcx",430,29,"A CLI for managing Grafana Cloud resources. Optimized for agentic usage.",[],[84,85,86,87,90,91],{"slug":5,"name":6},{"slug":30,"name":31},{"slug":33,"name":34},{"slug":88,"name":89},"agents","Agents",{"slug":45,"name":46},{"slug":39,"name":40},{"name":93,"fullName":19,"repoUrl":94,"skillCount":20,"stars":95,"forks":20,"description":63,"topics":96,"topTags":97,"topTagCount":10,"lastUpdatedAt":110},"ai-marketplace","https:\u002F\u002Fgithub.com\u002Fgrafana\u002Fai-marketplace",15,[],[98,99,102,103,106,109],{"slug":5,"name":6},{"slug":100,"name":101},"mcp","MCP",{"slug":45,"name":46},{"slug":104,"name":105},"configuration","Configuration",{"slug":107,"name":108},"docker","Docker",{"slug":33,"name":34},"2026-07-21T05:39:33.356231",{"name":112,"fullName":22,"repoUrl":113,"skillCount":23,"stars":114,"forks":115,"description":116,"topics":117,"topTags":119,"topTagCount":134,"lastUpdatedAt":135},"grafana-infinity-datasource","https:\u002F\u002Fgithub.com\u002Fgrafana\u002Fgrafana-infinity-datasource",1056,148,"API datasource for grafana. Visualize data from JSON \u002F CSV \u002F TSV \u002F XML \u002F GraphQL endpoints",[118],"group-datasources",[120,121,124,127,128,131],{"slug":5,"name":6},{"slug":122,"name":123},"api-development","API Development",{"slug":125,"name":126},"authentication","Authentication",{"slug":104,"name":105},{"slug":129,"name":130},"csv","CSV",{"slug":132,"name":133},"data-analysis","Data Analysis",8,"2026-07-15T05:34:05.773947",{"name":137,"fullName":25,"repoUrl":138,"skillCount":26,"stars":139,"forks":140,"description":141,"topics":142,"topTags":143,"topTagCount":152,"lastUpdatedAt":153},"faro-web-sdk","https:\u002F\u002Fgithub.com\u002Fgrafana\u002Ffaro-web-sdk",1103,121,"The Grafana Faro Web SDK, part of the Grafana Faro project, is a highly configurable web SDK for real user monitoring (RUM) that instruments browser frontend applications to capture observability signals. Frontend telemetry can then be correlated with backend and infrastructure data for full-stack observability.",[],[144,147,150,151],{"slug":145,"name":146},"distributed-tracing","Distributed Tracing",{"slug":148,"name":149},"frontend","Frontend",{"slug":33,"name":34},{"slug":30,"name":31},4,"2026-07-12T07:43:24.63314",{"name":155,"fullName":156,"repoUrl":157,"skillCount":26,"stars":134,"forks":158,"description":159,"topics":160,"topTags":161,"topTagCount":152,"lastUpdatedAt":166},"pyroscope-skills","grafana\u002Fpyroscope-skills","https:\u002F\u002Fgithub.com\u002Fgrafana\u002Fpyroscope-skills",0,"Claude Code plugin providing profilecli-powered performance analysis skills for Pyroscope profiling data",[],[162,163,164,165],{"slug":39,"name":40},{"slug":5,"name":6},{"slug":30,"name":31},{"slug":36,"name":37},"2026-07-12T07:45:02.369321",{"name":168,"fullName":169,"repoUrl":170,"skillCount":26,"stars":171,"forks":26,"description":172,"topics":173,"topTags":176,"topTagCount":152,"lastUpdatedAt":183},"xk6-docs","grafana\u002Fxk6-docs","https:\u002F\u002Fgithub.com\u002Fgrafana\u002Fxk6-docs",5,"User and AI agent-friendly k6 docs.",[174,175],"k6","xk6",[177,180,181,182],{"slug":178,"name":179},"documentation","Documentation",{"slug":5,"name":6},{"slug":36,"name":37},{"slug":42,"name":43},"2026-07-28T05:37:15.181243",{"items":185,"total":17},[186,198,214,226,239,256,269,282,292,304,315,330,343,355,365,376,389,400,412,423,433,444,454,465],{"slug":187,"name":187,"fn":188,"description":189,"org":190,"tags":191,"stars":79,"repoUrl":78,"updatedAt":197},"agento11y","manage Grafana Agent Observability resources","Inspects and manages Grafana Agent Observability resources via gcx: conversations, generations, evaluators, rules, scores, and templates. Use when the user wants to list or search conversations, inspect generations, manage evaluators (upsert, test, delete), set up evaluation rules, check scores, or browse evaluator templates. Trigger on phrases like \"list conversations\", \"search generations\", \"what did the agent do\", \"debug LLM conversation\", \"create evaluator\", \"set up evaluation rule\", \"test evaluator\", \"check scores\", \"evaluate generation quality\", or \"set up online evaluation\".\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[192,194,195,196],{"name":89,"slug":88,"type":193},"tag",{"name":6,"slug":5,"type":193},{"name":34,"slug":33,"type":193},{"name":31,"slug":30,"type":193},"2026-07-25T05:30:40.29622",{"slug":199,"name":199,"fn":200,"description":201,"org":202,"tags":203,"stars":79,"repoUrl":78,"updatedAt":213},"agento11y-instrument","instrument LLM apps for agent observability","Sets up and instruments a developer's own LLM app or agent to send generations and agentic workflow to Grafana Agent Observability (the Agent Observability SDKs) — greenfield setup, fixing broken instrumentation, or filling gaps in existing instrumentation. Uses gcx for the parts a static prompt can't do: `gcx login` \u002F `gcx cloud stacks` to find the stack, and `gcx agento11y agents|conversations|generations` to VERIFY that data actually lands — so it iterates (instrument → run → verify → fix) until generations arrive, not blindly. Reads the app's code, detects language\u002Fframework, classifies instrumentation state (none \u002F partial \u002F broken), then runs a fixed gap checklist whose #1 item is the silent failure no other prompt catches: the SDK emits OTel spans\u002Fmetrics but never creates a TracerProvider\u002FMeterProvider, so without them all metrics go to a no-op and are lost. Also checks agent_version (required for per-version Performance charts), set_result completeness, SYNC vs STREAM, parent_generation_ids DAG links, and workflow-step coverage. Recommends changes citing file:line and, only with explicit confirmation, applies minimal diffs that don't change app behavior. Pulls SDK reference from agento11y's llms.txt rather than restating it, and hands off to `agento11y-test-starter` once data flows. It does NOT write test suites or set up tenant evaluations, rules, or guards — offline test suites are `agento11y-test-starter`, tenant eval rules + guards are `agento11y-prod-setup`; does NOT install coding-agent telemetry plugins (that is llms.txt \"Path A\"); does NOT mint or store credentials or invent endpoints. Trigger on phrases like \"instrument my app\", \"send my agent's traces to Grafana\", \"set up AI observability for my app\", \"my generations aren't showing up\", \"why is Performance empty\", \"add Agent Observability to my code\", \"fix my instrumentation\".\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[204,205,206,209,212],{"name":89,"slug":88,"type":193},{"name":6,"slug":5,"type":193},{"name":207,"slug":208,"type":193},"Instrumentation","instrumentation",{"name":210,"slug":211,"type":193},"LLM","llm",{"name":31,"slug":30,"type":193},"2026-07-31T05:53:52.580237",{"slug":215,"name":215,"fn":216,"description":217,"org":218,"tags":219,"stars":79,"repoUrl":78,"updatedAt":56},"agento11y-prod-setup","setup production evaluation for AI agents","Sets up production evaluation and guardrails for a DEPLOYED AI agent in Grafana Agent Observability, grounded in the agent's own code and its real ingested traffic. The judgment layer on top of the `agento11y` skill: it reads the agent's source (system prompt, tools, entrypoint) AND samples its live traffic via gcx, checks what evaluators\u002Frules\u002Fguards already exist, then recommends only what's missing — online eval rules (score live conversations for regressions) and guards (warn-first request-path policies that redact \u002F tool-filter and may later be promoted to deny). It drafts reviewable YAML and, only with explicit confirmation, applies via `gcx agento11y`. New guards are drafted in warn mode (safe on live traffic — warn records but never blocks). It DOES create stack-level objects — that is the point — but every write is confirmed. It never rewrites or redeploys the agent. Trigger on phrases like \"set up production evaluation\", \"my agent is in prod what should I evaluate\", \"catch quality regressions\", \"add guardrails to my agent\", \"redact PII from my agent\", \"block dangerous tools\", \"set up online evals and guards\".\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[220,221,224,225],{"name":89,"slug":88,"type":193},{"name":222,"slug":223,"type":193},"Evals","evals",{"name":6,"slug":5,"type":193},{"name":31,"slug":30,"type":193},{"slug":227,"name":227,"fn":228,"description":229,"org":230,"tags":231,"stars":79,"repoUrl":78,"updatedAt":238},"agento11y-test-starter","build and run agent test suites","Use early in an AI-agent project — before ship, before real traffic — to build a starter test suite for the agent and run it offline. Reads the agent's own code (system prompt, tools, task), writes a labeled draft suite of test cases (happy\u002Fedge\u002Fadversarial) grounded in real lines, and recommends how to score each case (the evaluators\u002Fjudges the offline runner uses). Assesses how runnable the agent is: for an easily-invoked agent it generates a runner stub (run_experiment.py) with two holes to fill and can optionally run it (only with permission, only against the endpoint the developer configured); for agents needing a harness or full runtime it points to the existing eval infra. It runs OFFLINE and never creates tenant-level evaluators, rules, or guards — that is `agento11y-prod-setup`, for a deployed agent with real traffic. Trigger on phrases like \"how do I test my agent before shipping\", \"write test cases for my agent\", \"set up tests for my agent\", \"check my agent before prod\", \"I have no traffic yet, how do I evaluate it\", \"test my agent offline\".\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[232,233,234,237],{"name":89,"slug":88,"type":193},{"name":6,"slug":5,"type":193},{"name":235,"slug":236,"type":193},"QA","qa",{"name":43,"slug":42,"type":193},"2026-07-31T05:53:51.62785",{"slug":240,"name":240,"fn":241,"description":242,"org":243,"tags":244,"stars":79,"repoUrl":78,"updatedAt":255},"create-dashboard","create Grafana dashboards with gcx","Designs and creates Grafana dashboards with gcx, using `gcx dashboards snapshot` as a visual feedback loop. Use when the user wants to create a new Grafana dashboard, add panels, variables, or annotations to an existing dashboard, design dashboard panels, variables, queries, or layout, or make a material visual redesign. Triggers on \"create dashboard\", \"new dashboard\", \"build dashboard\", \"dashboard for \u003Cservice>\", \"add panels\", \"add variable\", \"add annotation\", \"improve this dashboard\", or \"iterate on a dashboard\".\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[245,248,251,254],{"name":246,"slug":247,"type":193},"Dashboards","dashboards",{"name":249,"slug":250,"type":193},"Data Visualization","data-visualization",{"name":252,"slug":253,"type":193},"Design","design",{"name":6,"slug":5,"type":193},"2026-07-25T05:30:46.289717",{"slug":257,"name":257,"fn":258,"description":259,"org":260,"tags":261,"stars":79,"repoUrl":78,"updatedAt":268},"debug-with-grafana","investigate application issues with Grafana","Structured workflow for investigating application problems with Grafana observability data (metrics, logs, traces) via gcx. Covers live firefighting AND retrospective incident analysis: incident triage, root-cause analysis, blast-radius checks (did an incident spill into other services), verifying whether a deployment or rollout triggered an incident, finding which service, endpoint, or path owns the most errors or slow requests, checking whether retries or queue backlogs piled up, and quantifying error or latency shares over a time window. Trigger on: \"my API is returning 500 errors\", \"latency is spiking\", \"investigate why requests are failing\", \"triage the incident\", \"blast radius\", \"root cause\", \"did the rollout cause it\", \"which endpoint owns the most 5xx\", \"did retries pile up\", or any request to analyse an earlier incident window using telemetry. For authoring dashboards use create-dashboard; for dashboard inventory use manage-dashboards.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[262,263,264,267],{"name":40,"slug":39,"type":193},{"name":6,"slug":5,"type":193},{"name":265,"slug":266,"type":193},"Incident Response","incident-response",{"name":31,"slug":30,"type":193},"2026-07-18T05:11:10.445428",{"slug":270,"name":270,"fn":271,"description":272,"org":273,"tags":274,"stars":79,"repoUrl":78,"updatedAt":281},"diagnose-entity-graph","diagnose Grafana Entity Graph issues","Diagnose Entity Graph problems: missing entities, missing edges, disconnected clusters, or filtering issues. Use when the user reports that Entity Graph doesn't look right, services are missing, edges aren't appearing, or environments can't be filtered. Triggers for: \"entity graph is empty\", \"services missing from entity graph\", \"no edges in entity graph\", \"disconnected services\", \"can't filter entity graph\", \"entity graph not working\", \"diagnose entity graph\", \"debug knowledge graph\".\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[275,276,277,280],{"name":40,"slug":39,"type":193},{"name":6,"slug":5,"type":193},{"name":278,"slug":279,"type":193},"Graph Analysis","graph-analysis",{"name":31,"slug":30,"type":193},"2026-07-25T05:30:39.380934",{"slug":77,"name":77,"fn":283,"description":284,"org":285,"tags":286,"stars":79,"repoUrl":78,"updatedAt":291},"manage Grafana Cloud resources via gcx","Manages Grafana Cloud resources via the gcx CLI. Trigger when the user wants to inspect, create, update, delete, query, or automate any Grafana resource - dashboards, datasources, alerts, SLOs, synthetic checks, oncall, incidents, fleet, k6, knowledge graph, or adaptive telemetry.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[287,288,289,290],{"name":46,"slug":45,"type":193},{"name":6,"slug":5,"type":193},{"name":34,"slug":33,"type":193},{"name":55,"slug":54,"type":193},"2026-07-31T05:53:50.587304",{"slug":293,"name":293,"fn":294,"description":295,"org":296,"tags":297,"stars":79,"repoUrl":78,"updatedAt":303},"gcx-demo","present gcx demo tours","Run a narrated, read-only demo tour of gcx for customer or colleague presentations. Showcases the breadth of gcx across every Grafana Cloud product area — resources, datasources, metrics, logs, traces, SLOs, alerts, synthetic monitoring, IRM, k6, fleet, and more. All commands are strictly read-only. Trigger when the user says \"demo gcx\", \"show off gcx\", \"customer demo\", \"gcx tour\", or \"\u002Fgcx-demo\".\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[298,299,300],{"name":46,"slug":45,"type":193},{"name":6,"slug":5,"type":193},{"name":301,"slug":302,"type":193},"Presentations","presentations","2026-07-25T05:30:45.282458",{"slug":305,"name":305,"fn":306,"description":307,"org":308,"tags":309,"stars":79,"repoUrl":78,"updatedAt":314},"gcx-observability","setup Grafana Cloud observability","(Experimental) End-to-end observability setup for Grafana Cloud using gcx. Covers instrumentation, SLOs, alerting, synthetic monitoring, k6 load testing, IRM on-call, dashboards, cost optimization, and GitOps export. Use when the user wants to set up observability for an application from scratch or run a full observability rollout - phrases like \"set up monitoring\", \"instrument my app\", \"add observability\", or \"onboard my service to Grafana Cloud\".\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[310,311,312,313],{"name":49,"slug":48,"type":193},{"name":6,"slug":5,"type":193},{"name":34,"slug":33,"type":193},{"name":31,"slug":30,"type":193},"2026-07-25T05:30:38.282611",{"slug":316,"name":316,"fn":317,"description":318,"org":319,"tags":320,"stars":79,"repoUrl":78,"updatedAt":329},"generate-resource-stubs","generate Go resource stubs","Generates typed Go stub files and grafana-foundation-sdk builder boilerplate for dashboards and alert rules. Use only when the user explicitly asks for stubs, generated resource skeletons, or builder boilerplate. This is scaffolding only; for designing or creating a usable dashboard with datasource discovery and snapshot iteration, use the create-dashboard skill instead. Triggers on \"generate stub\", \"dashboard stub\", \"create alert rule stub\", \"foundation-sdk builder\", or \"builder boilerplate\".\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[321,322,325,326],{"name":52,"slug":51,"type":193},{"name":323,"slug":324,"type":193},"Go","go",{"name":6,"slug":5,"type":193},{"name":327,"slug":328,"type":193},"SDK","sdk","2026-07-15T05:34:16.92703",{"slug":331,"name":331,"fn":332,"description":333,"org":334,"tags":335,"stars":79,"repoUrl":78,"updatedAt":342},"import-dashboards","import Grafana dashboards as Go code","Imports existing Grafana dashboards as Go builder code via gcx. Use when the user wants to convert live dashboards to builder code, migrate dashboards to code, or reverse-engineer a dashboard from a Grafana instance. Triggers on \"import dashboard\", \"convert to code\", \"dashboard as code\", \"export dashboard\". For pulling dashboards as YAML\u002FJSON resource files rather than Go code, use manage-dashboards instead.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[336,339,340,341],{"name":337,"slug":338,"type":193},"Code Analysis","code-analysis",{"name":246,"slug":247,"type":193},{"name":323,"slug":324,"type":193},{"name":6,"slug":5,"type":193},"2026-07-15T05:34:10.690161",{"slug":344,"name":344,"fn":345,"description":346,"org":347,"tags":348,"stars":79,"repoUrl":78,"updatedAt":354},"investigate-alert","investigate Grafana alert firing and impact","Investigate Grafana alerts to determine why they are firing, their scope, and impact. Use when the user asks about a specific alert, wants to understand alert behavior, or needs to diagnose why an alert is in a firing or pending state. Trigger on phrases like \"why is this alert firing\", \"investigate this alert\", \"what is this alert rule doing\", or a named alert rule. For triaging what is actively paging in OnCall (alert groups, ack\u002Fsilence\u002Fresolve) use oncall-triage instead.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[349,352,353],{"name":350,"slug":351,"type":193},"Alerting","alerting",{"name":6,"slug":5,"type":193},{"name":31,"slug":30,"type":193},"2026-07-12T07:43:39.959325",{"slug":356,"name":356,"fn":357,"description":358,"org":359,"tags":360,"stars":79,"repoUrl":78,"updatedAt":364},"manage-dashboards","manage Grafana dashboards via gcx","Manages and inspects existing Grafana dashboards via gcx: list, get, search, audit what a saved dashboard actually contains (its panels and their types, the queries and expressions as saved, which datasource each panel uses, variables and what they are wired to), create or update from an already-authored manifest, delete, inspect and restore versions, pull\u002Fpush\u002Fvalidate\u002Fpromote dashboard resource files, manage dashboard folders, or render PNG snapshots. Trigger on \"what's on dashboard X\", \"what is each panel querying\", \"audit this dashboard\", \"which datasource does each panel use\", \"does the dashboard have a service dropdown\". Do NOT use when the task involves adding new panels, variables, or annotations - those require discovering real metrics or log schema, so use create-dashboard instead. For designing or creating a new dashboard, or for material visual\u002Fdashboard UX changes, also use create-dashboard.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[361,362,363],{"name":246,"slug":247,"type":193},{"name":6,"slug":5,"type":193},{"name":55,"slug":54,"type":193},"2026-07-25T05:30:41.303337",{"slug":366,"name":366,"fn":367,"description":368,"org":369,"tags":370,"stars":79,"repoUrl":78,"updatedAt":375},"oncall-triage","triage Grafana OnCall alert groups","Triages active Grafana OnCall alert groups via gcx - list, inspect, acknowledge, silence, resolve. Use when the user is triaging what is actively paging in Grafana OnCall, or asks about active alert groups, acknowledging or silencing or resolving fires, on-call queue, or \"what's paging right now\". Trigger on phrases like \"what's paging\", \"on-call alerts\", \"ack this\", \"silence the page\", \"what's firing in OnCall\", \"show me active pages\", or any reference to OnCall alert groups. For root cause of why a Grafana alert rule is evaluating (rule-side, pre-routing) use investigate-alert. For schedules, integrations, or escalation chains use the gcx skill.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[371,372,373,374],{"name":350,"slug":351,"type":193},{"name":6,"slug":5,"type":193},{"name":265,"slug":266,"type":193},{"name":34,"slug":33,"type":193},"2026-07-15T05:34:09.423253",{"slug":377,"name":377,"fn":378,"description":379,"org":380,"tags":381,"stars":79,"repoUrl":78,"updatedAt":388},"scaffold-project","scaffold Grafana resources-as-code projects","Scaffolds a new Go project for managing Grafana resources as code via gcx dev scaffold. Use when the user wants to create a new Grafana resources-as-code project, start a new dashboards-as-code repo, scaffold a gcx project, or asks \"how do I get started with gcx\". Triggers on phrases like \"new project\", \"scaffold\", \"bootstrap\", \"create project\", \"get started\".\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[382,383,384,385],{"name":46,"slug":45,"type":193},{"name":52,"slug":51,"type":193},{"name":6,"slug":5,"type":193},{"name":386,"slug":387,"type":193},"Infrastructure as Code","infrastructure-as-code","2026-07-25T05:30:44.288245",{"slug":390,"name":390,"fn":391,"description":392,"org":393,"tags":394,"stars":79,"repoUrl":78,"updatedAt":399},"setup-gcx","configure gcx for Grafana instances","Sets up gcx: installation, context creation, authentication, and connection to a Grafana instance. Covers Grafana Cloud and on-premise deployments, environment variable overrides for CI\u002FCD, default datasource configuration, and troubleshooting connection and authentication problems. Use when installing gcx, connecting gcx to a Grafana instance for the first time, or when gcx commands fail with auth or connectivity errors (401, 403, connection refused, missing namespace).\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[395,396,397,398],{"name":46,"slug":45,"type":193},{"name":105,"slug":104,"type":193},{"name":49,"slug":48,"type":193},{"name":6,"slug":5,"type":193},"2026-07-25T05:30:43.279807",{"slug":401,"name":401,"fn":402,"description":403,"org":404,"tags":405,"stars":79,"repoUrl":78,"updatedAt":411},"slo-check-status","check Grafana SLO health status","Checks Grafana SLO health, error budget, and burn rate via gcx, with timeline graphs for trends. Use when the user asks about SLO health, wants an overview of all SLOs, or needs status of a specific SLO. Trigger on phrases like \"how are my SLOs doing\", \"SLO status\", \"check my SLOs\", \"is my SLO healthy\", \"SLO budget\", \"SLO burn rate\". For investigating breaching SLOs use slo-investigate. For optimization suggestions use slo-optimize. For creating or modifying SLO definitions use slo-manage.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[406,409,410],{"name":407,"slug":408,"type":193},"Analytics","analytics",{"name":6,"slug":5,"type":193},{"name":34,"slug":33,"type":193},"2026-07-15T05:34:21.848756",{"slug":413,"name":413,"fn":414,"description":415,"org":416,"tags":417,"stars":79,"repoUrl":78,"updatedAt":422},"slo-investigate","diagnose breaching Grafana SLOs","Diagnoses breaching Grafana SLOs via gcx - root cause analysis, dimensional breakdown, alert rule correlation, runbook access. Use when a specific SLO is breaching or alerting and the user needs to understand why. Trigger on phrases like \"investigate SLO\", \"why is my SLO breaching\", \"SLO error budget burning\", \"SLO alerting\". For SLO status overview use slo-check-status. For creating or modifying SLOs use slo-manage. For optimization suggestions use slo-optimize.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[418,419,420,421],{"name":40,"slug":39,"type":193},{"name":6,"slug":5,"type":193},{"name":34,"slug":33,"type":193},{"name":31,"slug":30,"type":193},"2026-07-15T05:34:19.396839",{"slug":424,"name":424,"fn":425,"description":426,"org":427,"tags":428,"stars":79,"repoUrl":78,"updatedAt":432},"slo-manage","manage Grafana SLO definitions","Creates, updates, syncs, and deletes Grafana SLO definitions via gcx with dry-run validation and GitOps pull\u002Fpush workflows. Use when the user wants to create, update, pull, push, or delete SLO definitions. Trigger on phrases like \"create an SLO\", \"update SLO objective\", \"push SLO\", \"pull SLOs\", \"delete SLO\", or \"GitOps sync SLOs\". For checking SLO health or status, use slo-check-status instead. For investigating a breaching SLO, use slo-investigate instead.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[429,430,431],{"name":6,"slug":5,"type":193},{"name":31,"slug":30,"type":193},{"name":55,"slug":54,"type":193},"2026-07-12T07:43:37.279043",{"slug":434,"name":434,"fn":435,"description":436,"org":437,"tags":438,"stars":79,"repoUrl":78,"updatedAt":443},"slo-optimize","optimize Grafana SLO timeline trends","Analyzes Grafana SLO timeline trends via gcx and produces data-backed advisory recommendations:\nobjective tuning, alerting sensitivity review, label visibility, or window adjustments.\nUse when the user wants to analyze SLO performance trends and receive improvement suggestions.\nTrigger on phrases like \"optimize my SLO\", \"SLO improvement suggestions\", \"tune my SLO\",\n\"SLO performance analysis\", or \"should I change my SLO objective\".\nFor SLO status overview use slo-check-status.\nFor investigating breaching SLOs use slo-investigate.\nFor creating or modifying SLO definitions use slo-manage.\n",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[439,440,441,442],{"name":407,"slug":408,"type":193},{"name":6,"slug":5,"type":193},{"name":31,"slug":30,"type":193},{"name":37,"slug":36,"type":193},"2026-07-12T07:43:38.690627",{"slug":445,"name":445,"fn":446,"description":447,"org":448,"tags":449,"stars":79,"repoUrl":78,"updatedAt":453},"synth-check-status","monitor Synthetic Monitoring check health","Shows Synthetic Monitoring check health - check inventory, per-check pass\u002Ffail status with success rates, and success-rate timelines as terminal graphs. Use when the user asks about Synthetic Monitoring check health, status, or trends. Trigger on phrases like \"are my checks healthy\", \"check status\", \"synth check\", \"probe status\", or when users mention specific check names or IDs. For investigating failing checks use synth-investigate-check. For creating or managing checks use synth-manage-checks.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[450,451,452],{"name":6,"slug":5,"type":193},{"name":34,"slug":33,"type":193},{"name":31,"slug":30,"type":193},"2026-07-12T07:43:41.272793",{"slug":455,"name":455,"fn":456,"description":457,"org":458,"tags":459,"stars":79,"repoUrl":78,"updatedAt":464},"synth-investigate-check","diagnose Synthetic Monitoring check failures","Diagnoses why a Synthetic Monitoring check is failing - triages probe failures, classifies failure scope, runs per-probe breakdown, and identifies root cause. Use when the user wants to investigate a failing check. Trigger on phrases like \"why is my check failing\", \"investigate synthetic check\", \"probe failures\", \"check is down\". For check status overview use synth-check-status. For creating or managing checks use synth-manage-checks.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[460,461,462,463],{"name":40,"slug":39,"type":193},{"name":6,"slug":5,"type":193},{"name":34,"slug":33,"type":193},{"name":31,"slug":30,"type":193},"2026-07-12T07:43:47.1811",{"slug":466,"name":466,"fn":467,"description":468,"org":469,"tags":470,"stars":79,"repoUrl":78,"updatedAt":476},"synth-manage-checks","manage Synthetic Monitoring checks via YAML","Creates, updates, exports, and deletes Synthetic Monitoring checks from YAML definitions via gcx. Use when the user wants to create, update, pull, push, or delete Synthetic Monitoring checks. Trigger on phrases like \"create a check\", \"add a synthetic check\", \"update check\", \"pull my SM checks\", \"push checks\", \"delete check\", or when the user provides a target URL\u002Fhostname\u002Fdomain for monitoring. For check status overview use synth-check-status. For investigating failing checks use synth-investigate-check.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[471,472,473],{"name":6,"slug":5,"type":193},{"name":34,"slug":33,"type":193},{"name":474,"slug":475,"type":193},"YAML","yaml","2026-07-12T07:43:45.864457"]