Alloy
grafana/skills
Build a unified telemetry pipeline with Grafana Alloy — one OpenTelemetry-compatible binary that collects metrics, logs, traces, and profiles and ships to Grafana Cloud / Prometheus / Loki / Tempo /…
Operate, configure, provision, secure, and troubleshoot Grafana OSS, Enterprise, and Cloud, including dashboards, folders, data sources, annotations, alert rules, contact points, notification…
Install Grafana
$ npx skills add magnus919/agent-skills --skill grafana -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install magnus919/agent-skills grafana --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/grafana .claude/skills/grafana && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "grafana" agent skill from https://github.com/magnus919/agent-skills/tree/main/grafana into .claude/skills/grafana/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grafana", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/magnus919/agent-skills/tree/main/grafanaType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add magnus919/agent-skills --skill grafana -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install magnus919/agent-skills grafana --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/grafana .agents/skills/grafana && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "grafana" agent skill from https://github.com/magnus919/agent-skills/tree/main/grafana into .agents/skills/grafana/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grafana", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/agent-skills --skill grafana -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install magnus919/agent-skills grafana --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/grafana .cursor/skills/grafana && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "grafana" agent skill from https://github.com/magnus919/agent-skills/tree/main/grafana into .cursor/skills/grafana/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grafana", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/magnus919/agent-skills.git --path grafana--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add magnus919/agent-skills --skill grafana -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install magnus919/agent-skills grafana --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/grafana .gemini/skills/grafana && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "grafana" agent skill from https://github.com/magnus919/agent-skills/tree/main/grafana into .gemini/skills/grafana/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grafana", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install magnus919/agent-skills grafanaInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add magnus919/agent-skills --skill grafana -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/grafana .github/skills/grafana && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "grafana" agent skill from https://github.com/magnus919/agent-skills/tree/main/grafana into .github/skills/grafana/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grafana", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/agent-skills --skill grafana -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install magnus919/agent-skills grafana --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/grafana .opencode/skills/grafana && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "grafana" agent skill from https://github.com/magnus919/agent-skills/tree/main/grafana into .opencode/skills/grafana/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grafana", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
grafana- GitHub stars
- 115
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,038 words
- Files
- 11 (incl. references)
- Skills in repo
- 131
- Repo updated
- First seen
- Licence
- MIT
At a glance
Operate, configure, provision, secure, and troubleshoot Grafana OSS, Enterprise, and Cloud, including dashboards, folders, data sources, annotations, alert rules, contact points, notification…
- Works in 5 steps: Define the operational outcome → Reconcile ownership before content → Validate semantics before presentation → …
- Grafana product work and Grafana-side integrations
- SKILL.md covers Operating contract, When not to use, Read-only discovery and Route the task, plus 3 more sections
- Calls curl
What it does
Grafana is an agent skill from magnus919/agent-skills. Operate, configure, provision, secure, and troubleshoot Grafana OSS, Enterprise, and Cloud, including dashboards, folders, data sources, annotations, alert rules, contact points, notification policies, silences, mute timings, service accounts, RBAC, plugins, APIs, and as-code workflows. Use for Grafana product work and Grafana-side integrations. Do not use for defining SLOs or paging policy, operating Prometheus/Loki/Tempo/InfluxDB backends, generic Docker/Kubernetes/Terraform/reverse-proxy work, plugin…
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `EVIDENCE-LEDGER.md`, `README.md` and `evals/evals.json`). Compatibility notes: Requires current Grafana documentation and authorized access to the target for live operations. API work requires an HTTP client and appropriately scoped…
It sits in DevOps & Cloud, covering Monitoring and alerting. It works with Grafana, Docker, Kubernetes and Prometheus. The repository describes itself as: Curated collection of AI agent skills for Hermes and other agent frameworks. The licence is MIT.
When your agent uses it
- Grafana product work and Grafana-side integrations
- Operating Prometheus/Loki/Tempo/InfluxDB backends
- Generic Docker/Kubernetes/Terraform/reverse-proxy work
- Plugin development
Example prompts
- “/grafana”
Requirements
- Docker
- Compatibility (from SKILL.md): Requires current Grafana documentation and authorized access to the target for live operations. API work requires an HTTP client and appropriately scoped Grafana credentials.
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 22b4723. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires current Grafana documentation and authorized access to the target for live operations. API work requires an HTTP client and appropriately scoped Grafana credentials.
From compatibility in the SKILL.md frontmatter.
Context cost
Grafana loads about 2.4k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 151 tokens; SKILL.md has 1,038 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from magnus919/agent-skills at commit 22b4723, republished under its MIT licence (© magnus919). 1,038 words, ~2,431 tokens.
Download SKILL.mdSave it as
.claude/skills/grafana/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.- name
- grafana
- description
- Operate, configure, provision, secure, and troubleshoot Grafana OSS, Enterprise, and Cloud, including dashboards, folders, data sources, annotations, alert rules, contact points, notification policies, silences, mute timings, service accounts, RBAC, plugins, APIs, and as-code workflows. Use for Grafana product work and Grafana-side integrations. Do not use for defining SLOs or paging policy, operating Prometheus/Loki/Tempo/InfluxDB backends, generic Docker/Kubernetes/Terraform/reverse-proxy work, plugin development, or authorized security assessments; use the corresponding specialist skill.
- compatibility
- Requires current Grafana documentation and authorized access to the target for live operations. API work requires an HTTP client and appropriately scoped Grafana credentials.
- license
- MIT
- metadata.source
- https://grafana.com/docs/grafana/latest/
- metadata.source_index
- references/source-index.md
- metadata.research_checked
- 2026-07-26
Grafana Operations
Treat Grafana as a set of versioned, separately authorized resources with explicit owners. Discover the target, resource provenance, and effective routing before proposing a mutation. A healthy server or attractive dashboard is not proof that provisioning, queries, alert evaluation, or notification delivery works.
Operating contract
- Identify Grafana version, edition, deployment mode, organization, folder or namespace, authentication model, and current permission scope before selecting an API or workflow.
- Inventory existing file provisioning, Terraform/provider state, Git Sync, Grafana Operator resources, and API/UI-managed objects. Assign one authoritative owner per resource UID before changing it.
- Confirm the target, scope, and rollback path before acting. Read-only discovery may proceed without confirmation.
- Treat dashboard, folder, data-source, alerting, user/RBAC, plugin, and server-configuration changes as separate authorization scopes.
- Never print, commit, or preserve secret values from service-account tokens, passwords,
secureJsonData, decrypted receiver settings, OAuth secrets, signing keys, SMTP credentials, or webhooks. Preserve supported secure configuration fields through their authorized secret mechanism and record redacted metadata only. - Validate dashboard and alert queries against the real data source when access exists. Otherwise state the offline limitation and do not claim semantic correctness.
- Verify the requested boundary. Server health does not prove dashboard provisioning; rule firing does not prove routing; notification delivery does not prove resolution behavior.
When not to use
Use site-reliability-engineering to define SLIs, SLOs, error budgets, page-worthiness, severity policy, escalation, and incident practice. Use data-source-specific guidance for PromQL, LogQL, TraceQL, Flux, SQL, storage, and backend operation. Use docker-compose, kubernetes, traefik, or platform-engineering for their infrastructure control planes. Use secure-software-engineering for preventive security design and security-audit-methodology for an authorized assessment. This skill owns Grafana product behavior and Grafana-side integration.
Read-only discovery
Collect only what the current access permits:
grafana server -v
curl --fail --silent --show-error "$GRAFANA_URL/api/health"For containers, packages, Helm, or Cloud, use the owning platform's read-only inventory to establish the image/tag, configuration path, deployment mode, and public boundary. Do not dump process environments or resolved configuration containing secrets. With an authorized service-account token, prefer bounded GET requests for the exact resource class; send the token through a protected environment or credential store, not command history or reports.
Record:
- version and edition: OSS, Enterprise, or Cloud;
- deployment owner and persistence: package, container, Compose, Kubernetes, Helm, Operator, or managed stack;
- organization, folder, namespace, and target environment;
- authentication method and effective permissions;
- data-source UIDs and types without secure fields;
- dashboard/folder UIDs, alerting resources, and their provenance;
- provisioning providers, watched paths, polling interval, deletion/edit settings, and duplicate ownership;
- rollback source and the boundary that can be tested safely.
Read API and version discovery before choosing endpoints. Grafana 12 introduced the new /apis model, while legacy /api routes begin deprecation in Grafana 13 and do not yet have complete one-to-one replacements.
Route the task
| Need | Read first |
|---|---|
| Discover version, edition, auth, organization, resource APIs, and permission scope | API and version discovery |
| Design or review dashboards, panels, variables, units, transformations, links, annotations, library panels, JSON, or accessibility | Dashboard engineering |
| Build or diagnose rule evaluation, labels, contact points, policies, grouping, silences, mute timings, templates, and delivery | Alerting and routing |
| Choose or reconcile file provisioning, Terraform, Git Sync, API, Foundation SDK, or Operator ownership | Provisioning and GitOps |
| Diagnose blank panels, query/auth failures, provisioning drift, failed evaluations, missing notifications, or proxy/auth problems | Troubleshooting |
| Handle credentials, users, service accounts, RBAC, plugins, deletion, sharing, or production-impacting change | Security and change control |
| Check evidence, version currency, live findings, or refresh rules | Source index |
Safe workflow
1. Define the operational outcome
Name the audience, decision, resource UIDs, authoritative owner, target environment, expected interruption, verification method, and rollback. For dashboards, declare the observability method or question. For alerts, declare owner, severity rationale, runbook/dashboard link, expected route, and noise risk.
Show full SKILL.md (430 more words)Show less
2. Reconcile ownership before content
Compare the running object with every potential writer. Do not edit a provisioned resource through another surface merely because that surface permits it. Detect overlapping provider paths, duplicate UIDs or titles, Terraform/API drift, UI edits that will be overwritten, and deletion or pruning behavior before changing files or objects.
3. Validate semantics before presentation
Run representative queries over a known time range. Confirm metric/log/trace type, units, labels, aggregation, cardinality, null/no-data behavior, time zone, refresh interval, and query cost. Derive defaults, thresholds, refresh cadence, top-N limits, and minimum-traffic cutoffs from target evidence, approved policy, or an explicit measurement objective; otherwise leave them open rather than choosing plausible values. For repeated panels or multi-dimensional alerts, bound the dimension set and prove it remains actionable.
4. Preview and apply through the owner
Use the authoritative source and the narrowest supported operation. Review diffs and exported backups with secrets redacted. A policy-tree replacement, prune, provider-source removal, UID reuse, RBAC change, plugin install, or data-source/dashboard deletion requires explicit confirmation immediately before mutation.
5. Verify each affected plane
| Plane | Minimum evidence |
|---|---|
| Server | Versioned process responds and database health is reported; bounded logs show no new failure loop |
| Provisioning | One owner per UID/path; reconciliation completes; no duplicate/drift warnings across more than one scan |
| Data source | Authorized health/query test succeeds with expected time range and representative data |
| Dashboard | Queries are semantically valid; units/labels/empty states render correctly; links and variables preserve context |
| Alert evaluation | Expected normal, pending, firing, no-data/error, and recovery behavior is observed or explicitly untested |
| Notification routing | Actual labels select the intended policy/contact point; grouping and mute behavior are checked |
| Delivery | A controlled test reaches the intended receiver and a resolved notification is observed when permitted |
| Access | Intended role can act; a lower-privilege role cannot; secrets remain redacted |
Approval boundaries
Explicit approval is required before password resets; user, organization, team, service-account, or RBAC changes; plugin installation or removal; data-source, dashboard, folder, alert-rule, contact-point, or policy deletion; notification-policy replacement; live notification tests; provisioning reloads or service restarts; secret rotation; anonymous/public sharing changes; or direct database recovery. Never edit Grafana's database directly unless the user explicitly authorizes a documented recovery procedure after backup and supportable alternatives are exhausted.
Exit criteria
The task is complete when the requested resource or diagnosis is tied to a known Grafana version and owner, relevant queries or routes are validated at the strongest authorized boundary, no secret was exposed, and rollback remains available. List every stronger boundary not exercised, including authenticated API inventory, live data-source queries, alert firing, receiver delivery, resolved notifications, accessibility testing, reload/restart persistence, or production behavior.
© magnus919, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 10 other files (references) in grafana of magnus919/agent-skills.
- SKILL.md
- EVIDENCE-LEDGER.md
- README.md
- evals/evals.json
- references/alerting-and-routing.md
- references/api-and-version-discovery.md
- references/dashboard-engineering.md
- references/provisioning-and-gitops.md
- references/security-and-change-control.md
- references/source-index.md
- references/troubleshooting.md
Open the folder on GitHubat commit 22b4723
Compare with similar skills
Grafana next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Grafana this skillmagnus919/agent-skills | 115 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Alloygrafana/skills | 282 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Beylagrafana/skills | 282 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Dashboard Previewm4r1k/Eneru | 149 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Graftm4r1k/Eneru | 149 | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Release Reviewm4r1k/Eneru | 149 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Beyla
grafana/skills
Auto-instrument an application's HTTP / gRPC / DB traffic with Grafana Beyla eBPF — no code changes, no SDK, no restart.
Dashboard Preview
m4r1k/Eneru
Visually verify Eneru browser-dashboard changes against a live daemon or audit an exact deployment.
Graft
m4r1k/Eneru
This repo is indexed by graft/. An agent skill from m4r1k/Eneru.
Release Review
m4r1k/Eneru
Mandatory pre-release deep review for minor/major releases (X.Y.0 / X.0.0).
Proto Backend Module
aide-family/moon
Implements backend modules from proto definitions for goddess, marksman, and rabbit apps.
More from magnus919/agent-skills
All 131 skills in this repoArtifact Pyramids
magnus919/agent-skills
Organize durable agent research outputs as summaries, analysis, and evidence dossiers.
Ascii City Engine
magnus919/agent-skills
Build portable, first-person colored ASCII city engines and small GIS-derived city packs.
Color Management
magnus919/agent-skills
Manage color workflows with ICC profiles, working spaces, gamut mapping, and color science.
Data Scientist
magnus919/agent-skills
A skill your agent uses for PhD-level expertise in data science, statistics, and machine learning: rigorous statistical analysis, experimental design, causal inference, advanced modeling, research…
Docker Compose
magnus919/agent-skills
Use Docker Compose to define, run, debug, and harden multi-container applications.
Fpga Development
magnus919/agent-skills
Design, review, simulate, and verify FPGA logic using explicit RTL contracts, clock and reset models, CDC analysis, timing constraints, and reproducible implementation evidence.
Related
Categories
Questions about Grafana
What does Grafana do?
Operate, configure, provision, secure, and troubleshoot Grafana OSS, Enterprise, and Cloud, including dashboards, folders, data sources, annotations, alert rules, contact points, notification…. Grafana is an agent skill from magnus919/agent-skills. Operate, configure, provision, secure, and troubleshoot Grafana OSS, Enterprise, and Cloud, including dashboards, folders, data sources, annotations, alert rules, contact points, notification policies, silences, mute timings, service accounts, RBAC, plugins, APIs, and as-code workflows.
When should I use Grafana?
Grafana fits situations like: grafana product work and Grafana-side integrations; operating Prometheus/Loki/Tempo/InfluxDB backends; generic Docker/Kubernetes/Terraform/reverse-proxy work; plugin development.
How do I install Grafana in Claude Code?
Run `npx skills add magnus919/agent-skills --skill grafana -a claude-code`. Or copy the skill folder (grafana in magnus919/agent-skills) into .claude/skills/grafana in your project. Claude Code loads it when a task matches its description.
How do I install Grafana in Codex?
Run `npx skills add magnus919/agent-skills --skill grafana -a codex`. Or copy the skill folder (grafana in magnus919/agent-skills) into .agents/skills/grafana in your project. Codex loads it when a task matches its description.
Can I use Grafana in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add magnus919/agent-skills --skill grafana -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/grafana, .gemini/skills/grafana, .github/skills/grafana and .opencode/skills/grafana in your project.
What does Grafana need to run?
Going by SKILL.md and its folder, Grafana needs the command-line tools its instructions call (curl). Our summary lists: Docker. Compatibility (from SKILL.md): Requires current Grafana documentation and authorized access to the target for live operations. API work requires an HTTP client and appropriately scoped Grafana credentials..
Does Grafana access the network?
SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Grafana safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Grafana use?
Grafana is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Grafana use?
About 2.4k tokens (SKILL.md is roughly 9.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.
What are the alternatives to Grafana?
Skills that share tags, products or a category with Grafana: Alloy (grafana/skills, 282 stars), Beyla (grafana/skills, 282 stars), Dashboard Preview (m4r1k/Eneru, 149 stars) and Graft (m4r1k/Eneru, 149 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Grafana?
magnus919 (a GitHub user) maintains it in magnus919/agent-skills, which has 115 GitHub stars. The repository holds 131 skills in this directory. The repository was last updated on October 10, 2026.
Source: magnus919/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.