[{"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":14},[186,200,215,231,246,262,278,289,299,313,326,342,360,373,383,395,413,429,443,454,464,479,494,505],{"slug":187,"name":187,"fn":188,"description":189,"org":190,"tags":191,"stars":61,"repoUrl":60,"updatedAt":199},"adaptive-metrics","optimize Grafana Cloud metrics costs","Cut Grafana Cloud Metrics cost by shrinking active-series count with Adaptive Metrics aggregation rules — auto-recommendations from query history, custom exact\u002Fregex rules, label-drop config, unused-metric detection, and Alloy remote_write fallback. Use when investigating a high Mimir\u002FGrafana Cloud bill, hunting high-cardinality labels (`pod_uid`, `service_instance_id`, `version`), pre-aggregating counters\u002Fgauges, dropping unused metrics, or measuring `grafanacloud_instance_active_series` before\u002Fafter — even when the user says \"reduce cardinality\", \"too many series\", \"metrics spend\", \"active series count is exploding\", or \"drop the version label\" without naming Adaptive Metrics.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[192,196,197,198],{"name":193,"slug":194,"type":195},"Cost Optimization","cost-optimization","tag",{"name":6,"slug":5,"type":195},{"name":72,"slug":71,"type":195},{"name":31,"slug":30,"type":195},"2026-07-12T07:44:27.451068",{"slug":201,"name":201,"fn":202,"description":203,"org":204,"tags":205,"stars":61,"repoUrl":60,"updatedAt":214},"admin","manage Grafana Cloud accounts and RBAC","Manage Grafana Cloud accounts — organizations, stacks, RBAC roles and assignments, SSO\u002FSAML\u002FOAuth\u002FGitHub auth, service accounts for CI\u002FCD, user invites, team membership, and API-driven provisioning. Creates stacks via the Cloud API, mints service-account tokens, applies role assignments, configures SSO providers, and provisions teams\u002Ffolders\u002Fdashboards via Terraform. Use when managing Grafana Cloud access, configuring SSO\u002FSAML\u002FOAuth, setting up service accounts for Terraform\u002FCI\u002FCD, assigning RBAC roles, inviting users, managing multiple stacks or organizations, provisioning cloud resources via API or Terraform, or auditing admin actions — even when the user says \"set up SSO\", \"create a stack\", \"make a service account\", or \"onboard a team\" without explicitly saying \"admin\".",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[206,209,212,213],{"name":207,"slug":208,"type":195},"Access Control","access-control",{"name":210,"slug":211,"type":195},"Auth","auth",{"name":6,"slug":5,"type":195},{"name":55,"slug":54,"type":195},"2026-07-12T07:44:12.078436",{"slug":216,"name":216,"fn":217,"description":218,"org":219,"tags":220,"stars":61,"repoUrl":60,"updatedAt":230},"admission-control","implement admission control webhooks","Use when the user asks to \"write a validator\", \"add validation\", \"implement admission control\", \"write a mutating webhook\", \"add a mutation handler\", \"validate incoming resources\", \"implement admission logic\", \"add admission webhooks\", \"write ingress validation\", or asks how to validate or mutate resources before they are persisted in a grafana-app-sdk app. Provides guidance on implementing validation and mutation admission handlers for grafana-app-sdk apps.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[221,224,227],{"name":222,"slug":223,"type":195},"Architecture","architecture",{"name":225,"slug":226,"type":195},"Security","security",{"name":228,"slug":229,"type":195},"Validation","validation","2026-07-12T07:45:06.148973",{"slug":232,"name":232,"fn":233,"description":234,"org":235,"tags":236,"stars":61,"repoUrl":60,"updatedAt":245},"alerting-irm","configure Grafana Alerting and Incident Management","Configure Grafana Alerting, Incident Response Management (IRM), and SLOs end-to-end — provisions Grafana-managed and data-source-managed alert rules, contact points (Slack\u002FPagerDuty\u002Femail\u002Fwebhook), notification policies with hierarchical matchers, silences, mute timings, on-call schedules and escalation chains, incident-management integrations, and SLOs with multi-window burn-rate alerts. Use when configuring alerts, debugging notification routing, setting up on-call rotations, declaring or managing incidents, defining SLOs, provisioning alerting via YAML or API, picking matchers for a notification policy, building a PagerDuty\u002FSlack webhook receiver, or troubleshooting why an alert isn't firing — even when the user says \"page me on errors\", \"alert me when X happens\", \"route this to the platform team\", or \"set up an SLO\" without naming Alerting or IRM.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[237,240,241,244],{"name":238,"slug":239,"type":195},"Alerting","alerting",{"name":6,"slug":5,"type":195},{"name":242,"slug":243,"type":195},"Incident Response","incident-response",{"name":34,"slug":33,"type":195},"2026-07-12T07:44:02.393397",{"slug":247,"name":247,"fn":248,"description":249,"org":250,"tags":251,"stars":61,"repoUrl":60,"updatedAt":261},"alloy","build unified telemetry pipelines with Grafana Alloy","Build a unified telemetry pipeline with Grafana Alloy — one OpenTelemetry-compatible binary that collects metrics, logs, traces, and profiles and ships to Grafana Cloud \u002F Prometheus \u002F Loki \u002F Tempo \u002F Pyroscope. Covers the Alloy config language (blocks, `sys.env`, component refs), `prometheus.scrape` → `remote_write`, `loki.source.file` + `loki.process` → `loki.write`, `otelcol.receiver.otlp` → `otelcol.exporter.otlp`, `pyroscope.scrape`, K8s \u002F Docker \u002F EC2 discovery, relabeling, modules (`import.file\u002Fgit\u002Fhttp`), clustering, Fleet Management `remotecfg`, the Alloy UI at `:12345`, and `alloy fmt` \u002F `alloy validate`. Use when writing a `config.alloy`, replacing Grafana Agent \u002F OTel Collector, scraping K8s pods, parsing logs, ingesting OTLP, or debugging \"Alloy isn't sending anything\" — even when the user says \"set up the agent\", \"write me a scrape config\", \"drop these logs before sending\", or \"OTel collector config\" without naming Alloy.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[252,253,256,257,258],{"name":6,"slug":5,"type":195},{"name":254,"slug":255,"type":195},"Logs","logs",{"name":72,"slug":71,"type":195},{"name":31,"slug":30,"type":195},{"name":259,"slug":260,"type":195},"OpenTelemetry","opentelemetry","2026-07-12T07:43:54.817139",{"slug":263,"name":263,"fn":264,"description":265,"org":266,"tags":267,"stars":61,"repoUrl":60,"updatedAt":277},"app-observability","monitor application performance in Grafana Cloud","Get RED metrics + service maps + frontend RUM + AI\u002FLLM monitoring out of Grafana Cloud — Application Observability (`traces_spanmetrics_*` from OTel traces, p50\u002Fp95\u002Fp99 latency, exemplar-to-trace, traces-to-logs \u002F profiles), Frontend Observability with the Faro Web SDK (Core Web Vitals, session replay, `pushError`, React + router integration, `TracingInstrumentation` for browser → backend trace correlation), and AI Observability via OpenLIT (token \u002F cost \u002F latency, GPU, hallucination + toxicity evals). Use when standing up APM for a service, wiring an Alloy OTLP receiver + forwarding to Cloud, instrumenting a React frontend for RUM, debugging why service-map edges are missing, monitoring LLM cost drift, or correlating a frontend error to its backend trace — even when the user says \"set up APM\", \"show service map\", \"monitor browser perf\", \"session replay\", \"RUM SDK\", or \"watch our OpenAI bill\" without naming App \u002F Frontend \u002F AI Observability.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[268,271,272,273,276],{"name":269,"slug":270,"type":195},"APM","apm",{"name":146,"slug":145,"type":195},{"name":6,"slug":5,"type":195},{"name":274,"slug":275,"type":195},"LLM","llm",{"name":31,"slug":30,"type":195},"2026-07-12T07:44:34.500406",{"slug":279,"name":279,"fn":280,"description":281,"org":282,"tags":283,"stars":61,"repoUrl":60,"updatedAt":288},"app-sdk-concepts","scaffold and configure Grafana apps","Use when starting any grafana-app-sdk work — scaffolding a Grafana app, initializing a Grafana App Platform app, picking a deployment mode (standalone operator \u002F grafana\u002Fapps \u002F frontend-only), wiring app-specific config, or onboarding to the SDK. Covers `grafana-app-sdk` CLI install, `project init` per deployment mode, project layout, the schema-centric workflow (CUE kinds → generated code → reconciler\u002Fadmission logic), and `SpecificConfig` for env-driven app configuration. Use even if the user just says \"make a new app\", \"Grafana app platform\", \"kinds and watchers\", \"operator scaffold\", or asks about `apps\u002F` inside the Grafana repo, without naming the SDK explicitly.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[284,285,286,287],{"name":222,"slug":223,"type":195},{"name":49,"slug":48,"type":195},{"name":52,"slug":51,"type":195},{"name":6,"slug":5,"type":195},"2026-07-12T07:45:08.595757",{"slug":290,"name":290,"fn":291,"description":292,"org":293,"tags":294,"stars":61,"repoUrl":60,"updatedAt":298},"assistant-mcp","connect coding agents to Grafana Cloud","Connect AI coding agents (Claude Code, Cursor, VS Code, OpenAI Codex) to Grafana Cloud via the `mcp-grafana` Model Context Protocol server. Installs the server with `go install`, generates a Grafana service-account token, wires `~\u002F.claude\u002Fsettings.json` or `~\u002F.cursor\u002Fmcp.json` with the `command` + `env` block, runs `--disable-write` for safer read-only sessions, switches to SSE transport for team-shared \u002F VS Code setups, and verifies with `\u002Fmcp` + a `list_datasources` round-trip. Use when connecting Claude Code to Grafana, setting up MCP for Grafana, configuring the Grafana MCP server, using Grafana tools in Cursor\u002FVS Code, querying Grafana from an AI agent, sharing the MCP server across a team — even when the user says \"give my agent Grafana access\", \"let Claude see my metrics\", or \"Cursor + Grafana\" without saying \"MCP\".",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[295,296,297],{"name":89,"slug":88,"type":195},{"name":6,"slug":5,"type":195},{"name":101,"slug":100,"type":195},"2026-07-12T07:44:20.615856",{"slug":300,"name":300,"fn":301,"description":302,"org":303,"tags":304,"stars":61,"repoUrl":60,"updatedAt":312},"audit-and-reduce-dependencies","reduce JavaScript dependency footprint","Reduces JavaScript dependency footprint with pnpm while preserving lockfile, workspace layout, and dependency range style. Runs \u002Fcheck-npm first, then removes unused deps, dedupes versions, ranks transitive closure, and reports Keep\u002FReplace\u002FRemove triage. Use when cleaning up pnpm dependencies, reducing lockfile size, or shrinking node_modules in Grafana plugins; not for Go modules or full GitHub Actions workflow audits.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[305,308,309,311],{"name":306,"slug":307,"type":195},"Code Analysis","code-analysis",{"name":52,"slug":51,"type":195},{"name":310,"slug":310,"type":195},"npm",{"name":37,"slug":36,"type":195},"2026-07-12T07:44:59.939525",{"slug":314,"name":314,"fn":315,"description":316,"org":317,"tags":318,"stars":61,"repoUrl":60,"updatedAt":325},"beyla","auto-instrument applications with Grafana Beyla","Auto-instrument an application's HTTP \u002F gRPC \u002F DB traffic with Grafana Beyla eBPF — no code changes, no SDK, no restart. Covers requirements (Linux 5.8+ with BTF, CAP_SYS_ADMIN, host PID), language matrix (Go \u002F Java \u002F Python \u002F Ruby \u002F Node \u002F .NET \u002F Rust \u002F C++ \u002F PHP), Docker + Helm + DaemonSet install, port- \u002F process- \u002F Kubernetes-metadata discovery, OTLP traces + Prometheus metrics export, routes decorator (cardinality control), trace sampling, and Grafana Cloud via Alloy. Use when adding observability to a service you can't recompile, instrumenting a closed-source binary, getting RED metrics + spans onto Tempo\u002FMimir without touching the app, or rolling Beyla as a cluster-wide DaemonSet — even when the user says \"zero-code APM\", \"instrument legacy app\", \"trace this binary\", \"eBPF observability\", or \"no SDK\" without naming Beyla.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[319,322,323,324],{"name":320,"slug":321,"type":195},"eBPF","ebpf",{"name":6,"slug":5,"type":195},{"name":34,"slug":33,"type":195},{"name":31,"slug":30,"type":195},"2026-07-12T07:43:56.154331",{"slug":327,"name":327,"fn":328,"description":329,"org":330,"tags":331,"stars":61,"repoUrl":60,"updatedAt":341},"check-npm","audit npm configuration for security","Audit a JavaScript\u002FTypeScript repo's npm, yarn, or pnpm configuration for supply-chain hardening: tool version, lifecycle scripts, unsafe dependency protocols, and minimum release age ≥3 days. Use when the user invokes \u002Fcheck-npm or asks to audit package manager security, lifecycle scripts, git dependencies, ignore-scripts, min-release-age, allow-git, approvedGitRepositories, strictDepBuilds, or blockExoticSubdeps in a Grafana plugin or JS\u002FTS project.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[332,333,336,337,338],{"name":306,"slug":307,"type":195},{"name":334,"slug":335,"type":195},"JavaScript","javascript",{"name":310,"slug":310,"type":195},{"name":225,"slug":226,"type":195},{"name":339,"slug":340,"type":195},"TypeScript","typescript","2026-07-12T07:44:55.106314",{"slug":343,"name":343,"fn":344,"description":345,"org":346,"tags":347,"stars":61,"repoUrl":60,"updatedAt":359},"cloud-integrations","configure Grafana Cloud integrations for cloud providers","Set up, configure, and troubleshoot Grafana Cloud integrations for AWS, Azure, and other cloud providers. Use when the user asks to connect AWS CloudWatch, set up Azure Monitor, configure Confluent Cloud observability, install a Grafana integration, set up hosted exporters, use AWS Firehose for CloudWatch logs, or troubleshoot a cloud integration. Triggers on phrases like \"AWS CloudWatch\", \"Azure Monitor\", \"Confluent integration\", \"cloud integration\", \"hosted exporter\", \"AWS Firehose\", \"install integration\", \"cloud metrics\", or \"cloud logs\".",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[348,351,354,355,358],{"name":349,"slug":350,"type":195},"AWS","aws",{"name":352,"slug":353,"type":195},"Azure","azure",{"name":6,"slug":5,"type":195},{"name":356,"slug":357,"type":195},"Integrations","integrations",{"name":34,"slug":33,"type":195},"2026-07-12T07:44:18.424139",{"slug":361,"name":361,"fn":362,"description":363,"org":364,"tags":365,"stars":61,"repoUrl":60,"updatedAt":372},"cost-management","optimize Grafana Cloud billing and spend","Cut your Grafana Cloud bill by attributing spend to teams and reducing telemetry volume. Covers FOCUS-compliant billing dashboards, cost-attribution labels in Alloy, Adaptive Metrics (cardinality reduction), Adaptive Logs (drop\u002Fsample), Adaptive Traces (tail sampling), usage alerts, and an optimization checklist. Use when investigating a high Grafana Cloud bill, attributing observability cost to a team or service, reducing active series \u002F log bytes \u002F trace spans, or setting up usage \u002F quota alerts — even when the user says \"our Grafana bill is too high\", \"who's burning the most metrics\", \"drop debug logs\", \"sample our traces\", or \"alert me before we hit quota\" without naming Cost Management.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[366,367,368,369],{"name":193,"slug":194,"type":195},{"name":6,"slug":5,"type":195},{"name":37,"slug":36,"type":195},{"name":370,"slug":371,"type":195},"Reporting","reporting","2026-07-12T07:44:30.569533",{"slug":374,"name":374,"fn":375,"description":376,"org":377,"tags":378,"stars":61,"repoUrl":60,"updatedAt":382},"cue-kind-definition","author CUE kind definitions for Grafana","Author CUE kind definitions for grafana-app-sdk apps - schemas, versioning, field constraints, named type definitions, custom routes, and codegen configuration. Scaffolds kinds via `grafana-app-sdk project kind add`, writes spec\u002Fstatus schemas with type constraints (regex, enum, range), defines `#`-prefixed named types for reusable structs, registers versions in the app manifest, and runs `grafana-app-sdk generate` with explicit error recovery. Use when working with CUE kinds, adding a new resource type, adding a version to an existing kind, writing schema field constraints, defining `#Definition` types, adding custom routes, editing files under `kinds\u002F`, or when the user asks to \"model a resource\", \"add a CUE schema\", or \"write a kind\" — even without saying \"CUE\" explicitly.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[379,380,381],{"name":123,"slug":122,"type":195},{"name":105,"slug":104,"type":195},{"name":52,"slug":51,"type":195},"2026-07-12T07:45:07.374612",{"slug":384,"name":384,"fn":385,"description":386,"org":387,"tags":388,"stars":61,"repoUrl":60,"updatedAt":394},"dashboarding","build and ship Grafana dashboards","Build, modify, and ship Grafana dashboards as JSON via the HTTP API — panel types (timeseries \u002F stat \u002F gauge \u002F table \u002F heatmap \u002F logs \u002F traces \u002F node-graph), `gridPos` 24-column layout, units, thresholds, template + datasource + chained variables, transformations (`organize` \u002F `calculateField` \u002F `filterByValue`), panel + dashboard links with `${__field.labels.x}` \u002F `${__from}`, and Loki\u002FPrometheus annotations. Use when scripting dashboard creation, writing the dashboard JSON for a new service, adding a `$job` dropdown variable, computing an \"Error %\" column with a transformation, overlaying deploys as annotations, or pushing a dashboard via `POST \u002Fapi\u002Fdashboards\u002Fdb` — even when the user says \"create a dashboard for this metric\", \"add a service dropdown\", \"show errors as percentage\", \"overlay our deploys\", or \"export the dashboard JSON\" without naming the API or schema. After every API push, verify with the returned `version` plus a GET on the dashboard UID.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[389,392,393],{"name":390,"slug":391,"type":195},"Dashboards","dashboards",{"name":6,"slug":5,"type":195},{"name":31,"slug":30,"type":195},"2026-07-12T07:44:01.119317",{"slug":396,"name":396,"fn":397,"description":398,"org":399,"tags":400,"stars":61,"repoUrl":60,"updatedAt":412},"database-observability","monitor MySQL and PostgreSQL with Grafana","Set up Grafana Cloud Database Observability for MySQL and PostgreSQL — enables `pg_stat_statements` \u002F Performance Schema, creates a least-privilege monitoring user, configures the `database_observability.postgres` \u002F `database_observability.mysql` Alloy components, ships query samples + visual explain plans + RED metrics + schema details to Grafana Cloud, and correlates slow queries with application traces via `db.statement` \u002F `db.system` OTel attributes. Use when monitoring database performance, diagnosing slow queries, setting up DB observability for RDS \u002F Aurora \u002F Cloud SQL \u002F Azure Database \u002F self-managed instances, correlating DB metrics with APM, or alerting on query latency — even when the user says \"my database is slow\", \"find the slow queries\", or \"monitor RDS\" without saying \"observability\".",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[401,404,405,408,409],{"name":402,"slug":403,"type":195},"Database","database",{"name":6,"slug":5,"type":195},{"name":406,"slug":407,"type":195},"MySQL","mysql",{"name":31,"slug":30,"type":195},{"name":410,"slug":411,"type":195},"PostgreSQL","postgresql","2026-07-12T07:44:35.785302",{"slug":414,"name":414,"fn":415,"description":416,"org":417,"tags":418,"stars":61,"repoUrl":60,"updatedAt":428},"datasources-provisioning","provision Grafana data sources","Generate a copy-paste Grafana data source provisioning file (YAML or Terraform) for any plugin from its standardized settings schema on the plugins CDN. Use when the user wants to provision or configure a data source as code — e.g. \"provision infinity\", \"datasource yaml for clickhouse\", \"terraform for the github datasource\" — even when they only name the plugin and not the word \"provisioning\".",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[419,420,421,422,425],{"name":105,"slug":104,"type":195},{"name":49,"slug":48,"type":195},{"name":6,"slug":5,"type":195},{"name":423,"slug":424,"type":195},"Terraform","terraform",{"name":426,"slug":427,"type":195},"YAML","yaml","2026-07-12T07:45:03.633244",{"slug":430,"name":430,"fn":431,"description":432,"org":433,"tags":434,"stars":61,"repoUrl":60,"updatedAt":442},"dpm-finder","analyze Prometheus metrics for billing","Find the Prometheus metrics that drive your Grafana Cloud bill. `dpm-finder` is a Grafana Professional Services CLI that ranks metrics by Data Points per Minute (DPM) with per-label-set breakdown, optional `--cost-per-1000-series` pricing, and a Prometheus-exporter mode. Use when investigating high Grafana Cloud spend, hunting noisy \u002F high-cardinality metrics, comparing pre\u002Fpost recording-rule cardinality, or feeding cost data into dashboards — even when the user says \"why is my Mimir bill so high?\", \"find the biggest metrics\", \"cardinality offenders\", or \"optimize Prometheus cost\" without naming dpm-finder.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[435,438,439,440,441],{"name":436,"slug":437,"type":195},"Analytics","analytics",{"name":46,"slug":45,"type":195},{"name":193,"slug":194,"type":195},{"name":6,"slug":5,"type":195},{"name":37,"slug":36,"type":195},"2026-07-12T07:44:15.870474",{"slug":444,"name":444,"fn":445,"description":446,"org":447,"tags":448,"stars":61,"repoUrl":60,"updatedAt":453},"fleet-management","manage Grafana Alloy collector fleets","Manage a fleet of Grafana Alloy collectors with Fleet Management — author Alloy pipelines once, target them via attribute matchers (`env=\"production\"`, regex `region=~\"us-.*\"`), push remotely via OpAMP without restarting collectors. Covers pipeline create \u002F update \u002F matcher RPCs, collector attribute API, `remotecfg` bootstrap block (standalone + Helm), pre-deploy `alloy fmt` validation, the local Alloy UI at port 12345 for component health, and post-deploy `REMOTE_CONFIG_STATUS_APPLIED` verification. Use when standing up a Cloud Alloy fleet, pushing a config change to 200 collectors, hunting why one collector shows `REMOTE_CONFIG_STATUS_FAILED`, validating River syntax before saving, or wiring `discovery.kubernetes` → `prometheus.remote_write` — even when the user says \"configure Alloy\", \"remote config the collectors\", \"push pipeline\", \"OpAMP\", \"collector is unhealthy\", or \"manage agent config centrally\" without naming Fleet Management.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[449,450,451,452],{"name":49,"slug":48,"type":195},{"name":6,"slug":5,"type":195},{"name":31,"slug":30,"type":195},{"name":55,"slug":54,"type":195},"2026-07-12T07:44:31.863936",{"slug":455,"name":455,"fn":456,"description":457,"org":458,"tags":459,"stars":61,"repoUrl":60,"updatedAt":463},"grafana-oss","configure Grafana OSS dashboards and datasources","Configure Grafana OSS — provisions dashboards from YAML, sets up data sources (Prometheus \u002F Loki \u002F Tempo \u002F Pyroscope), writes dashboard JSON with template variables, builds panel queries, assigns built-in roles (Viewer \u002F Editor \u002F Admin \u002F GrafanaAdmin), mints service-account tokens, edits grafana.ini server config, creates annotations, installs plugins via provisioning, and validates each step with a health-check curl. Use when building dashboards, configuring data sources, setting up provisioning YAML, picking a panel type, writing template variables, managing users and roles, configuring SMTP\u002FOAuth in grafana.ini, creating annotations via API, troubleshooting why a provisioned dashboard isn't showing up, or running Grafana OSS locally — even when the user says \"set up a Prometheus data source\", \"provision dashboards from git\", \"make a service account\", or \"configure SSO in OSS\" without saying \"Grafana OSS\".",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[460,461,462],{"name":390,"slug":391,"type":195},{"name":6,"slug":5,"type":195},{"name":31,"slug":30,"type":195},"2026-07-12T07:43:59.859886",{"slug":465,"name":465,"fn":466,"description":467,"org":468,"tags":469,"stars":61,"repoUrl":60,"updatedAt":478},"grafana-scenes","build Grafana plugin pages","Build Grafana plugin pages using the @grafana\u002Fscenes framework. Use when creating new scene pages, adding panels\u002Fvisualizations, setting up drilldown navigation, defining variables, configuring query runners, building table\u002Ftimeseries\u002Fstat panels, or extending SceneObjectBase for custom scene objects. Triggers on any work involving SceneApp, SceneAppPage, EmbeddedScene, SceneQueryRunner, SceneDataTransformer, PanelBuilders, SceneFlexLayout, QueryVariable, or drilldown\u002Ftab configuration in Grafana plugins.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[470,471,472,475],{"name":149,"slug":148,"type":195},{"name":6,"slug":5,"type":195},{"name":473,"slug":474,"type":195},"React","react",{"name":476,"slug":477,"type":195},"UI Components","ui-components","2026-07-12T07:44:53.708142",{"slug":480,"name":480,"fn":481,"description":482,"org":483,"tags":484,"stars":61,"repoUrl":60,"updatedAt":493},"infrastructure","ship infrastructure telemetry to Grafana Cloud","Ship Kubernetes, host, container, and cloud-provider telemetry into Grafana Cloud — `k8s-monitoring` Helm chart for K8s clusters (metrics + logs + traces + events + cost), Alloy `prometheus.exporter.unix` for Linux hosts, cAdvisor + Docker discovery for containers, and CloudWatch \u002F Azure Monitor \u002F Google Cloud Monitoring datasource setup. Use when onboarding a new cluster or VM fleet to Grafana Cloud, picking the right Helm values for K8s scraping, wiring kube-state-metrics + node-exporter + cAdvisor, alerting on `PodCrashLooping` \u002F node memory \u002F PVC capacity, or pulling AWS \u002F Azure \u002F GCP cloud metrics — even when the user says \"monitor my cluster\", \"send K8s metrics to Grafana\", \"scrape EC2 metrics\", \"cluster pod logs\", or \"install the monitoring helm chart\" without naming `k8s-monitoring` or Alloy.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[485,486,488,491,492],{"name":6,"slug":5,"type":195},{"name":487,"slug":480,"type":195},"Infrastructure",{"name":489,"slug":490,"type":195},"Kubernetes","kubernetes",{"name":34,"slug":33,"type":195},{"name":31,"slug":30,"type":195},"2026-07-12T07:44:17.145158",{"slug":174,"name":174,"fn":495,"description":496,"org":497,"tags":498,"stars":61,"repoUrl":60,"updatedAt":504},"run k6 performance and load tests","Generate, validate, and review k6 test scripts — load, stress, spike, soak, smoke, breakpoint, functional, and protocol. Covers HTTP, WebSocket, gRPC, browser, all executors, thresholds, checks, custom metrics, the k6-testing library, k6 Cloud execution, and the xk6 extension ecosystem; uses the xk6-docs CLI (with grafana.com web fallback) for docs lookup and validates every script by running it. Use when writing, generating, validating, or debugging any k6 or load-test script (including plain-language asks like \"load test this API\" or \"stress test my service\"), choosing executors\u002Fscenarios, or setting thresholds. For end-to-end website performance suites use k6-perf-test-website; for documenting k6 itself use k6-docs.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[499,500,501,502,503],{"name":6,"slug":5,"type":195},{"name":334,"slug":335,"type":195},{"name":37,"slug":36,"type":195},{"name":43,"slug":42,"type":195},{"name":339,"slug":340,"type":195},"2026-07-25T05:30:51.304968",{"slug":506,"name":506,"fn":507,"description":508,"org":509,"tags":510,"stars":61,"repoUrl":60,"updatedAt":515},"k6-cloud-investigate-test","investigate Grafana Cloud k6 test runs","Investigate a Grafana Cloud k6 test — describe the script, list run history, identify pass\u002Ffail status, pull raw metric time-series and log lines for one or more runs, and (if asked) safely edit the test script. Use when the user asks about a specific k6 cloud test or run, gives a `\u002Fa\u002Fk6-app\u002Ftests\u002F\u003Cid>` or `\u002Fa\u002Fk6-app\u002Fruns\u002F\u003Cid>` URL, asks \"is this test passing\", \"why are my k6 tests failing\", \"show me metrics for run X\", \"show me logs for run X\", or wants to add thresholds \u002F fix a failing test. Trigger this skill even when the user doesn't explicitly say \"investigate\" — pasted `\u002Fa\u002Fk6-app\u002F...` URLs, \"why did run X fail\", \"what happened with my test\", \"is my test healthy\", \"the latest run looks weird\", \"checks are failing but the run says passed\", or any request to diagnose a Grafana Cloud k6 run all qualify.",{"slug":5,"name":6,"logoUrl":7,"githubOrg":5},[511,512,513,514],{"name":40,"slug":39,"type":195},{"name":6,"slug":5,"type":195},{"name":31,"slug":30,"type":195},{"name":43,"slug":42,"type":195},"2026-07-18T05:47:59.937973"]