skills
AGENTS.md302 starsChanged 15 days agoApache-2.0View on GitHub
Instructions for AI agents working with this repository. This is the Grafana public skills repository — a plugin marketplace providing AI-assisted development skills for Claude Code, Cursor, and other tools supporting the Agent Skills standard. Skills cover Grafana, Prometheus, Loki, Tempo, Pyroscope, k6, and the broader LGTM observability stack. Key architecture: Skills are folders of instructions, scripts, and resources that agents load dynamically when relevant. Two frontmatter fields control who can invoke a skill: disable-model-invocation (default: false): - false: Agent…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository54 other files it gives its agents.
- admission-controlSkill
- app-sdk-conceptsSkill
- cue-kind-definitionSkill
- reconciler-logicSkill
- adaptive-metricsSkill
- adminSkill
- app-observabilitySkill
- assistant-mcpSkill
- cloud-integrationsSkill
- cost-managementSkill
- database-observabilitySkill
- dpm-finderSkill
- fleet-managementSkill
- frontend-session-rcaSkill
- infrastructureSkill
- loki-label-analyzerSkill
- ml-aiSkill
- oncall-irmSkill
- private-connectivitySkill
- prometheus-cardinality-troubleshooterSkill
- prometheus-label-strategySkill
- send-dataSkill
- synthetic-monitoring-checksSkill
- testingSkill
- alerting-irmSkill
- alloySkill
- beylaSkill
- dashboardingSkill
- grafana-ossSkill
- opentelemetrySkill
- promqlSkill
- skill-authoringSkill
- datasources-provisioningSkill
- k6-browser-testSkill
- k6-cloud-investigate-testSkill
- k6-docsSkill
- k6-manageSkill
- k6-perf-test-websiteSkill
- k6Skill
- k6-test-maintenanceSkill
- k6-trend-analysisSkill
- lokiSkill
- mimirSkill
- performance-rcaSkill
- profilecli-insightsSkill
- prometheusSkill
- pyroscopeSkill
- tempoSkill
- audit-and-reduce-dependenciesSkill
- check-npmSkill
- grafana-scenesSkill
- plugin-bundle-sizeSkill
- react-19-plugin-migrationSkill
- your-skill-nameSkill
The file
We split this AGENTS.md into the rules it gives an agent
9 rules. About 1 is common, 4 are distinctive, and 4 are very specific to this project.
≈1
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 40
When the context matches, the agent loads the full SKILL.md
- Very specific: line 77
Create skills/<plugin-name>/<skill-name>/SKILL.md following the template at template/SKILL.md
- Distinctive: line 79
Use the spec: name (lowercase, hyphens, max 64 chars), description (max 1024 chars, include "Use when...")
- Very specific: line 80
Run ./scripts/lint-skills.sh skills/<plugin-name> to validate
- Distinctive: line 82
Update README.md to list the new skill
- Distinctive: line 100
Be concise: Only include Grafana-specific knowledge the AI doesn't already have
- Distinctive: line 126
Add README.md or other docs inside skill directories
- Very specific: line 127
Put "When to Use" sections in the skill body (put in description frontmatter instead)
- Common: line 128
Add internal Grafana tooling, credentials, or infrastructure-specific content
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AGENTS.md
Instructions for AI agents working with this repository.
Repository Purpose
This is the Grafana public skills repository — a plugin marketplace providing AI-assisted development skills for Claude Code, Cursor, and other tools supporting the Agent Skills standard.
Skills cover Grafana, Prometheus, Loki, Tempo, Pyroscope, k6, and the broader LGTM observability stack.
Structure Overview
.claude-plugin/marketplace.json # Claude Code marketplace manifest
.cursor-plugin/marketplace.json # Cursor marketplace manifest (identical content)
.agents-plugin/marketplace.json # Codex marketplace manifest (identical content)
skills/ # All skills, grouped by plugin
<plugin-name>/
<skill-name>/
SKILL.md # Required: skill definition
scripts/ # Optional: executable helper scripts
references/ # Optional: reference docs loaded on demand
assets/ # Optional: templates, schemas, data files
template/SKILL.md # Starter template for contributors
scripts/lint-skills.sh # Validates SKILL.md filesKey architecture:
- Single source of truth in
skills/— Claude Code, Cursor, and Codex all reference the same content - Three marketplace manifests (
.claude-plugin/,.cursor-plugin/,.agents-plugin/) with identical content skills/is the conventional directory used by all major agent tools
How Skills Work
Skills are folders of instructions, scripts, and resources that agents load dynamically when relevant.
- The agent reads the skill's
descriptionfrontmatter - When the context matches, the agent loads the full
SKILL.md - Supporting files in
scripts/andreferences/are loaded on demand
Invocation Modes
Two frontmatter fields control who can invoke a skill:
disable-model-invocation (default: false):
false: Agent may auto-load when context matchestrue: Agent will never auto-load; only runs when user types/skill-name
user-invocable (default: true):
true: Appears in the/menu, user can call with/skill-name [arguments]false: Hidden from menu; only the agent can load it (background knowledge)
user-invocable | disable-model-invocation | User | Agent | Use case |
true (default) | false (default) | Yes | Yes | Most skills |
true | true | Yes | No | Side-effect operations (/deploy, /send) |
false | false | No | Yes | Background knowledge (conventions, guidelines) |
Dynamic Arguments
Skills can accept user input via $ARGUMENTS:
---
name: greet
description: Greet a user by name. Use when /greet is invoked.
---
Hello, $ARGUMENTS!Usage: /greet Alice → "Hello, Alice!"
When Adding New Skills
- Create
skills/<plugin-name>/<skill-name>/SKILL.mdfollowing the template attemplate/SKILL.md- Plugin groups:
grafana-core,grafana-cloud,grafana-plugins
- Plugin groups:
- Use the spec: name (lowercase, hyphens, max 64 chars), description (max 1024 chars, include "Use when...")
- Run
./scripts/lint-skills.sh skills/<plugin-name>to validate - Register the skill in both marketplace files under the appropriate plugin group
- Update
README.mdto list the new skill
When Adding Supporting Files
Skills can include:
scripts/— executable scripts, referenced from SKILL.md with relative pathsreferences/— detailed docs split out for progressive disclosure (keeps SKILL.md under 500 lines)assets/— templates, JSON schemas, data files
Reference scripts using relative paths from the skill directory, or use ${CLAUDE_PLUGIN_ROOT} for
plugin-root-relative paths when installed via Claude Code:
"${CLAUDE_PLUGIN_ROOT}/skills/grafana-core/your-skill/scripts/your-script"Skill Writing Guidelines
- Be concise: Only include Grafana-specific knowledge the AI doesn't already have
- Use examples: Code examples are more effective than explanations
- Include triggers in description: The description determines when the skill auto-activates
- Keep under 500 lines: Split large topics into multiple focused skills
- Use
disable-model-invocation: truefor command-style skills that should only run when explicitly invoked
Distribution
Claude Code
claude plugin marketplace add grafana/skills
claude plugin install grafana-core@grafana-skillsCursor
Settings - Rules, Skills, Subagents - Add from GitHub - https://github.com/grafana/skills
Other tools
Any tool supporting the Agent Skills standard or the skills/ convention
(including vercel-labs/skills CLI) can consume skills directly.
Do Not
- Add README.md or other docs inside skill directories
- Put "When to Use" sections in the skill body (put in
descriptionfrontmatter instead) - Add internal Grafana tooling, credentials, or infrastructure-specific content
- Hardcode script paths — use relative paths or
${CLAUDE_PLUGIN_ROOT} - Edit
.claude-plugin/marketplace.jsonwithout making the identical change to.cursor-plugin/marketplace.jsonand.agents-plugin/marketplace.json
Official Resources
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

