grafana

@grafana source repo

169 skills
0 followers
5 hours ago last updated

▌
Gitnexus Debugging · grafana
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"

0
installs
▌
Gitnexus Exploring · grafana
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

0
installs
▌
Gitnexus Refactoring · grafana
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"

0
installs
▌
Gitnexus Impact Analysis · grafana
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"

0
installs
▌
Faro Setup Web · grafana bundle
Instruments a web app with Grafana Faro Web SDK for frontend observability. Use when setting up error tracking, Web Vitals, session monitoring, or distributed tracing in a browser app.

0
installs
▌
Go · grafana
Best practices for working with Go codebases. Use when writing, debugging, or exploring Go code, including reading dependency sources and documentation.

0
installs
▌
Draft Release · grafana
Draft a new release. Bumps version, generates CHANGELOG.md from git history, and creates a PR.

0
installs
▌
Querying Yesoreyeram Infinity Datasource · grafana
Build queries with the Infinity data source — the query types (JSON, CSV, TSV, XML, GraphQL, HTML, UQL, GROQ, Google Sheets, Series, Transformations), the parsers (Frontend/simple, Backend JSONata, JQ, UQL, GROQ) and which support alerting, the sources (URL, Inline, Reference, Azure Blob, Random walk), output formats (table, timeseries, logs, trace, node graph, dataframe), root selector and columns, computed columns/filters/summarize, pagination, and template variables. Use when a user asks how to query Infinity; how to fetch JSON/CSV/XML/GraphQL/HTML from a URL or inline; how to select rows and columns; how to transform data with UQL/GROQ/JSONata/JQ; how to make a query work with alerting; how to paginate; or how to use variables in a query.

0
installs
▌
Configuring Yesoreyeram Infinity Datasource · grafana
Configure the Infinity data source — base URL and allowed hosts, the authentication methods (basic, bearer token, API key, digest, OAuth passthrough, OAuth 2.0 client credentials/JWT, Azure, Azure Blob, AWS), TLS, custom HTTP headers, network and security settings, the custom health check, and provisioning with a config file. Use when a user asks how to set up, configure, or change settings for the Infinity data source; how to authenticate to an API; how to allow hosts; how to provision it as YAML; or how to troubleshoot connection, authentication, or health-check issues.

0
installs
▌
Xk6 Docs · grafana bundle
Look up official k6 documentation with `<binary> x docs` when writing, debugging, or configuring a k6 test, or reaching for any k6 API, option, executor, or CLI flag. k6 syntax changes between versions, so consult it instead of recalling k6 from memory or searching the web.

0
installs
▌
K6 Docs Release · grafana
Release a new version of xk6-docs. Use when the user says "release", "tag", "new version", "publish", "cut a release" in the xk6-docs repo. Covers the full flow — push, tag, GitHub release, extension registry PR, and Slack announcement.

0
installs
▌
Grafana MCP Tools · grafana
Install, configure, and use the Grafana MCP server effectively. Covers setup via Docker or binary, environment variables, tool categories, RBAC, and best practices for context window management. Use when the user wants to set up mcp-grafana, configure Grafana MCP tools, or needs guidance on which MCP tool to use.

0
installs
▌
Grafana Assistant CLI · grafana
Use the grafana-assistant CLI to interact with Grafana Assistant via A2A API. Covers installation, configuration, prompting, keeping conversation context, and practical patterns for ops investigations. Use when the user mentions grafana-assistant, Grafana Assistant CLI, assistant tunnel, or wants to query a Grafana instance via the assistant.

0
installs
▌
Grafana Cloud MCP Tools · grafana
Connect to and use the Grafana Cloud MCP server effectively, including natural-language Grafana Assistant questions and observability investigations. Covers setup, OAuth authorization, tool categories, read/write access scopes, and best practices for context window management. Use when the user wants to set up Grafana Cloud MCP, ask Grafana Assistant a question, investigate metrics, logs, traces, profiles, dashboards, alerts, or incidents, needs guidance on which tool to use, or wants to understand access scopes.

0
installs
▌
Agento11y Eval Starter · grafana
Agent Observability eval starter

0
installs
▌
Agento11y Experiments · grafana
Run any Python LLM agent as an Agent Observability experiment using the public agento11y.experiments package: define a test suite, run an existing agent through typed trials, bind or record generation I/O, grade outputs, and publish scores, including from stored Grafana test suites.

0
installs
▌
Setup Coding Agent · grafana
Set up Grafana Agent observability for a coding agent (Claude Code, Codex, Copilot CLI, Cursor, OpenCode, pi, or Vibe) with the agento11y binary: install it, save credentials, wire the agent, verify a session reaches Grafana Cloud, and diagnose a broken pipeline. Use when the user says "set up agento11y", "monitor my coding agent", "agento11y doctor says something is wrong", "my sessions do not show up in Grafana", or asks why conversations arrive but analytics stay empty.

0
installs
▌
Commit Message · grafana
Draft a commit message when the user describes a code change and asks for a commit message. Not for general questions or explanations.

0
installs
▌
K6 Load Test · grafana
Use this skill when the user says "write a k6 script", "generate a k6 load test", or "create performance tests with k6." Handles load, performance, stress, soak, and spike tests for APIs, services, and applications, leveraging k6 MCP tools for script validation and documentation lookup.

0
installs
▌
K6 Smoke Test · grafana
Use this skill when the user wants a quick k6 smoke test to verify basic functionality under minimal load. Smoke tests run 1–5 VUs for a short duration and assert that endpoints respond correctly. Trigger on "smoke test", "sanity check", or "quick health check with k6".

0
installs
▌
K6 Browser Test · grafana
Use this skill when the user wants to write a k6 browser test that interacts with a web page using a real browser (Chromium). Covers navigation, clicks, form fills, assertions, and web-vitals thresholds via the k6/browser module. Trigger on "browser test", "UI test with k6", or "test the frontend with k6".

0
installs
▌
K6 Test Planner · grafana bundle
Use this skill to plan k6 test suites from natural-language requirements. It analyses the system under test, identifies the right test types (load, stress, soak, spike, smoke, browser), and produces a structured test plan that other k6 skills can execute. Trigger when the user asks to "plan tests", "design a test strategy", or "what k6 tests should I write".

0
installs
▌
K6 Playwright Converter · grafana
Use this skill when a user provides a Playwright script and needs a faithful conversion into a production-ready k6/browser test while following Grafana's migration guidance and MCP workflows.

0
installs
▌
Openspec Explore · grafana
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

0
installs
▌
Openspec Propose · grafana
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

0
installs
▌
AI Sdk Parity Review · grafana bundle
Review any requested ai-sdk scope against the registered upstream Vercel AI SDK parity baseline. Use for PRs, the current git diff, a branch range, a package or directory such as providers/anthropic, a reported bug, a new feature, stream chunks, SSE framing, provider messages, provider request conversion, orchestration, tools, output, provider options, frontend interop, or conformance fixture changes.

0
installs
▌
AI Sdk Parity Upgrade · grafana bundle
Upgrade the registered upstream Vercel AI SDK parity baseline for the Go ai-sdk repo. Use when bumping upstream ai or @ai-sdk/* package versions, regenerating conformance expectations, reconciling upstream behavior changes, or moving test/conformance/upstream.yaml forward.

0
installs
▌
Openspec Apply Change · grafana
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

0
installs
▌
Pr Description Writer · grafana bundle
Write or rewrite pull request descriptions from a branch diff, commit range, existing PR, issue, upstream reference, specification, bug report, or review context. Use when an agent needs to create, update, or improve a PR body so it explains concrete code and behavior changes, why they were made, validation performed, and remaining risk.

0
installs
▌
Audit Guide · grafana bundle
Comprehensive read-only audit of an existing Pathfinder guide. Combines structural (lint), semantic (check + best-practices decision trees + the 21 critical rules), and adversarial (attack) analysis into one phased workflow that produces a single prioritised report. Use when the user asks to audit, review, lint+check, or check the quality of an existing guide directory.

0
installs
▌
Update Guide · grafana bundle
Modify an existing Pathfinder guide based on a change request. Plans the edit, applies it surgically, runs a review pass against critical rules, and validates with the Pathfinder CLI. Preserves all blocks outside the planned change. Use when the user wants to add, edit, or remove blocks in an existing guide, swap a data source, retrofit lazyRender, or otherwise modify a guide's content.json without rewriting it from scratch.

0
installs
▌
Autogen Guide · grafana bundle
Generate interactive guide content.json files from source code. Analyzes React/TypeScript UI components to extract structure, selectors, field metadata, and conditional logic, then produces a Pathfinder guide JSON. Use when the user provides GitHub links to source code and wants to create a guide from it, or asks to auto-generate a guide from code.

0
installs
▌
Migrate Guide · grafana
Migrate a standalone guide or learning path to the Pathfinder package format by generating manifest.json (and path-level content.json for LJs). Reads content.json, index.json, recommender rules, and optionally website markdown to derive all manifest fields. Use when the user wants to migrate a guide directory to the package format, or asks to create a manifest.json for a guide.

0
installs
▌
Review Learning Path · grafana bundle
Guide a human reviewer through a learning path PR in interactive-tutorials — five phases from checkout through Block Editor smoke testing and GitHub submit. AI assists; the reviewer tests and approves comments. Use when the user runs /review-learning-path-pr.

0
installs
▌
Autogen Guide Dashboard · grafana bundle
Generate interactive guide content.json files from Grafana dashboard JSON. Analyzes dashboard panels, variables, rows, and data sources to produce a Pathfinder guide that tours or explains a dashboard. Use when the user provides dashboard JSON (file, pasted, or Grafana API URL) and wants to create a guide from it.

0
installs
▌
Preflight Learning Path · grafana bundle
Guide a learning path author through pre-PR self-review in interactive-tutorials. Mirrors /review-learning-path-pr (shared static checklists, shared claim-check, Playwright DOM, readiness) from the author side, then optional package fixes and optional frontend data-testid PR. Use when the user runs /preflight-learning-path.

0
installs
▌
Write Codemod · grafana bundle
Write Codemod

0
installs
▌
Bump Plugin E2e · grafana
Use when bumping the @grafana/plugin-e2e version in the create-plugin template. Fetches the latest npm version, updates _package.json, commits, and opens a draft PR.

0
installs
▌
Diagnose Plugin E2e Incompatibility · grafana
Diagnose a failing nightly E2E run by identifying which grafana/grafana commit likely introduced an incompatibility with @grafana/plugin-e2e. Use whenever the user wants to triage a playwright-nightly failure, asks "what broke the nightly", "which grafana commit broke plugin-e2e", "diagnose plugin-e2e incompatibility", "find the bad commit", "triage the nightly failure", or pastes a failing run URL from the playwright-nightly workflow.

0
installs
▌
App · grafana
Skill for the App area of metrics-drilldown. 24 symbols across 16 files.

0
installs
▌
Stat · grafana
Skill for the Stat area of metrics-drilldown. 12 symbols across 8 files.

0
installs
▌
Labels · grafana
Skill for the Labels area of metrics-drilldown. 12 symbols across 4 files.

0
installs
▌
Fetchers · grafana
Skill for the Fetchers area of metrics-drilldown. 11 symbols across 3 files.

0
installs
▌
Bookmarks · grafana
Skill for the Bookmarks area of metrics-drilldown. 14 symbols across 11 files.

0
installs
▌
Breakdown · grafana
Skill for the Breakdown area of metrics-drilldown. 15 symbols across 9 files.

0
installs
▌
Components · grafana
Skill for the Components area of metrics-drilldown. 25 symbols across 15 files.

0
installs
▌
Extensions · grafana
Skill for the Extensions area of metrics-drilldown. 17 symbols across 8 files.

0
installs
▌
Timeseries · grafana
Skill for the Timeseries area of metrics-drilldown. 13 symbols across 8 files.

0
installs
▌
Metricscene · grafana
Skill for the MetricScene area of metrics-drilldown. 15 symbols across 9 files.

0
installs
▌
Quicksearch · grafana
Skill for the QuickSearch area of metrics-drilldown. 25 symbols across 17 files.

0
installs
▌
Relatedlogs · grafana
Skill for the RelatedLogs area of metrics-drilldown. 12 symbols across 2 files.

0
installs
▌
Gitnexus CLI · grafana
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"

0
installs
▌
Appdatatrail · grafana
Skill for the AppDataTrail area of metrics-drilldown. 28 symbols across 17 files.

0
installs
▌
Savedqueries · grafana
Skill for the SavedQueries area of metrics-drilldown. 12 symbols across 3 files.

0
installs
▌
Gitnexus Guide · grafana
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"

0
installs
▌
Relatedmetrics · grafana
Skill for the RelatedMetrics area of metrics-drilldown. 13 symbols across 11 files.

0
installs
▌
Metrics Variables · grafana
Skill for the Metrics-variables area of metrics-drilldown. 35 symbols across 15 files.

0
installs
▌
Metricsgroupbylist · grafana
Skill for the MetricsGroupByList area of metrics-drilldown. 16 symbols across 9 files.

0
installs
▌
Metricsfiltersection · grafana
Skill for the MetricsFilterSection area of metrics-drilldown. 14 symbols across 4 files.

0
installs
▌
Metriclabelvalueslist · grafana
Skill for the MetricLabelValuesList area of metrics-drilldown. 28 symbols across 12 files.

0
installs
▌
Metricdatasourcehelper · grafana
Skill for the MetricDatasourceHelper area of metrics-drilldown. 22 symbols across 7 files.

0
installs
▌
Release · grafana
Tag and release a new gcx version. Use when the user wants to cut a release, tag a version, run the release process, or says "release patch/minor/major".

0
installs
▌
Review Pr · grafana
Review someone else's gcx pull request, produce a ranked report with a verdict, and optionally post it to GitHub as line-anchored inline comments. Covers what to report, in what order, when to stop, how to rank over-engineering findings, how to judge whether a large diff is justified, and how to turn the report into review comments with an APPROVE/COMMENT/REQUEST_CHANGES recommendation. Trigger on "review this PR", "review

0
installs
▌
Gcx · grafana
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.

0
installs
▌
Add Provider · grafana bundle
Use for the implementation workflow once a capability is already classified as a Grafana Cloud product provider (SLO, OnCall, Synthetic Monitoring, k6, ML, etc.) — provider package, commands, config keys, optional resource adapters. Trigger on "add provider", "new provider", "build the [product] provider". NOT for deciding whether something should be a provider at all, for integration contracts, or for pre-review self-checks — use the repo-local integrate-with-gcx contributor skill for those.

0
installs
▌
Add Datasource · grafana bundle
Use for the implementation workflow that adds gcx CLI support for a datasource type not registered in internal/datasources/providers — query client, command constructors, DatasourceProvider registration. Trigger on "add support for an unsupported datasource type" or "new datasource type". NOT for creating or configuring a datasource instance in a Grafana stack (that is the shipped `gcx datasources create`), NOT for extending an already-registered kind, and NOT for deciding the integration tier or contract or running pre-review self-checks — use the existing kind's implementation or the repo-local integrate-with-gcx contributor skill instead.

0
installs
▌
Generate Slide · grafana
Regenerate the gcx marketing bento-box slide (slide.html) with verified commands from the current codebase. Builds a fresh binary and reflects against the actual command tree. Use when the user says "regenerate slide", "update slide", "generate slide", or "/generate-slide".

0
installs
▌
Gcx Demo · grafana
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 "/gcx-demo".

0
installs
▌
Agento11y · grafana bundle
Inspects and manages Grafana Agent Observability resources via gcx: conversations, generations, experiments, evaluators, rules, scores, and templates. Use when the user wants to list or search conversations, export experiment conversations, inspect generations, manage evaluators (upsert, test, delete), set up evaluation rules, check scores, or browse evaluator templates. Trigger on phrases like "list conversations", "export experiment conversations", "build a fine-tuning dataset", "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".

0
installs
▌
Setup Gcx · grafana bundle
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/CD, 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).

0
installs
▌
Migrate Provider · grafana bundle
Reference for porting a Grafana Cloud product from the legacy grafana-cloud-cli into a gcx provider — adapter, schema/example registration, CRUD redirect commands. HUMAN-DRIVEN — this skill is outside the integrate-with-gcx v1 autonomous workflow and must not be run end to end unattended because its non-registration steps have not been fully audited. Use when a human is deliberately driving a port and says "migrate provider", "port from gcx", "port oncall", "port k6". Not for building providers from scratch — use /add-provider. Recheck present-day placement before porting.

0
installs
▌
Slo Manage · grafana bundle
Creates, updates, syncs, and deletes Grafana SLO definitions via gcx with dry-run validation and GitOps pull/push 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.

0
installs
▌
Integrate With Gcx · grafana bundle
Guides a contributor and their coding agent through adding or extending a capability in the grafana/gcx codebase: deciding whether a new command is needed and where it belongs (provider, datasource kind, resource adapter, cloud command, or bundled skill), designing the command's agent-facing contract (naming, typed inputs, output protocol class, completeness, errors, token cost), implementing with shared-infrastructure reuse, and catching the defect classes that recur in gcx review before a human looks. Use when working inside a grafana/gcx checkout to add, extend, or review a gcx capability. Trigger on phrases like "integrate with gcx", "add my product to gcx", "new gcx command", "expose this API through gcx", or "get my gcx PR ready for review". NOT for operating a Grafana instance with gcx — use the gcx skill or a product skill (slo-manage, synth-manage-checks, create-dashboard). NOT for installing or configuring gcx — use setup-gcx.

0
installs
▌
Slo Optimize · grafana
Analyzes Grafana SLO timeline trends via gcx and produces data-backed advisory recommendations: objective tuning, alerting sensitivity review, label visibility, or window adjustments. Use when the user wants to analyze SLO performance trends and receive improvement suggestions. Trigger on phrases like "optimize my SLO", "SLO improvement suggestions", "tune my SLO", "SLO performance analysis", or "should I change my SLO objective". For SLO status overview use slo-check-status. For investigating breaching SLOs use slo-investigate. For creating or modifying SLO definitions use slo-manage.

0
installs
▌
Oncall Triage · grafana
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.

0
installs
▌
Slo Investigate · grafana bundle
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.

0
installs
▌
Create Dashboard · grafana
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 <service>", "add panels", "add variable", "add annotation", "improve this dashboard", or "iterate on a dashboard".

0
installs
▌
Scaffold Project · grafana
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".

0
installs
▌
Slo Check Status · grafana
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.

0
installs
▌
Gcx Observability · grafana bundle
(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".

0
installs
▌
Import Dashboards · grafana
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/JSON resource files rather than Go code, use manage-dashboards instead.

0
installs
▌
Investigate Alert · grafana bundle
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/silence/resolve) use oncall-triage instead.

0
installs
▌
Manage Dashboards · grafana bundle
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/push/validate/promote 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/dashboard UX changes, also use create-dashboard.

0
installs
▌
Debug With Grafana · grafana bundle
Investigates application problems and incidents using Grafana metrics, logs, and traces via gcx. Use for alerts, errors, latency, regressions, blast radius, or trace comparison. Uses qualified baselines and trace diff to investigate execution changes. Accepts alert payloads, dashboard links, and trace IDs; does not require IRM or all three signals. For alert-rule semantics use investigate-alert; dashboard authoring uses create-dashboard and inventory uses manage-dashboards.

0
installs
▌
Synth Check Status · grafana
Shows Synthetic Monitoring check health - check inventory, per-check pass/fail 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.

0
installs
▌
Synth Manage Checks · grafana bundle
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/hostname/domain for monitoring. For check status overview use synth-check-status. For investigating failing checks use synth-investigate-check.

0
installs
▌
Agento11y Instrument · grafana bundle
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` / `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/framework, classifies instrumentation state (none / partial / broken), then runs a fixed gap checklist whose #1 item is the silent failure no other prompt catches: the SDK emits OTel spans/metrics but never creates a TracerProvider/MeterProvider, 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

0
installs
▌
Agento11y Prod Setup · grafana
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/rules/guards 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 / 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

0
installs
▌
Diagnose Entity Graph · grafana
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".

0
installs
▌
Agento11y Test Starter · grafana
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/edge/adversarial) grounded in real lines, and recommends how to score each case (the evaluators/judges 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

0
installs
▌
Generate Resource Stubs · grafana bundle
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".

0
installs
▌
Synth Investigate Check · grafana bundle
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.

0
installs
▌
Bugfix · grafana bundle
Fix a robustness bug from GitHub issues using worktrees, test-first development, and subagents.

0
installs
▌
Review · grafana bundle
Routed PR review orchestrator. Load for `/review` command or any PR review task.

0
installs
▌
Secure · grafana
Security audit — frontend (F1-F6 rules from `.cursor/rules/frontend-security.mdc`), Go backend (URL allowlists, token handling, hardcoded secrets, unbounded reads), MCP HTTP transport (size / wallclock / concurrency caps, Zod-validated tool inputs), and dependency audit (`npm audit` high+critical, Go module advisories). Reports findings with concrete remediation per rule. Never edits source — the user applies fixes.

0
installs
▌
Refactor · grafana bundle
Execute high-risk refactors of large or intertwined components per the High-Risk Refactor Guidelines wiki — investigation, phased planning, and atomic-commit execution with subagent fan-out and worktree isolation. Use when the user invokes /refactor-investigate, /refactor-plan, or /refactor-execute, or asks to refactor a large component, split a complex hook, decompose a singleton, extract from a monolith, or otherwise restructure intertwined code.

0
installs
▌
Techdebt · grafana bundle
Locate technical debt in a subsystem or architectural component of a codebase. Use when the user runs `/techdebt <subsystem>` or asks to audit a module for smells, duplication, prop drilling, dead code, or other debt patterns. Examples: "/techdebt src/auth", "find tech debt in components/docs-panel", "audit the interactive-engine for smells".

0
installs
▌
Changelog · grafana
Draft a CHANGELOG.md entry from merged PRs since the last release tag. Categorizes by conventional-commit prefix (Added / Fixed / Chore / Security / Changed / Removed), rewrites PR titles into sentence-case narrative bullets with PR refs, and commits to the current branch without pushing. Use when preparing a release, or call this skill from `/release-prep`.

0
installs
▌
I18N Sync · grafana
Detect translation gaps across the 21 locales under `src/locales/`. For keys present in `en-US` but missing from another locale, add the key with an empty string value (matching the runtime fallback to the en-US default). Emit a gap report (filled / empty / stale counts per locale + the list of newly stubbed keys). Never invents translations; translators fill the empty stubs later.

0
installs
▌
Pr Summary · grafana
Generate a structured PR description from the current diff using `docs/design/CONCERNS.md` routing. Interviews the author for motivation before drafting. Produces canonical sections (Summary, What to look at, Why, How to verify, Breaking changes, Reversibility) tailored to change type. Outputs the draft for human review; can apply via `gh pr edit` after explicit confirmation. Pair with `/review` — this skill drafts, `/review` reviews.

0
installs

169 published skills · page 1 of 2