agentleFS
grafanagrafana/skills/AGENTS.md

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…

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
  1. Very specific:

    When the context matches, the agent loads the full SKILL.md

    line 40
  2. Very specific:

    Create skills/<plugin-name>/<skill-name>/SKILL.md following the template at template/SKILL.md

    line 77
  3. Distinctive:

    Use the spec: name (lowercase, hyphens, max 64 chars), description (max 1024 chars, include "Use when...")

    line 79
  4. Very specific:

    Run ./scripts/lint-skills.sh skills/<plugin-name> to validate

    line 80
  5. Distinctive:

    Update README.md to list the new skill

    line 82
  6. Distinctive:

    Be concise: Only include Grafana-specific knowledge the AI doesn't already have

    line 100
  7. Distinctive:

    Add README.md or other docs inside skill directories

    line 126
  8. Very specific:

    Put "When to Use" sections in the skill body (put in description frontmatter instead)

    line 127
  9. Common:

    Add internal Grafana tooling, credentials, or infrastructure-specific content

    line 128

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

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 files

Key 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.

  1. The agent reads the skill's description frontmatter
  2. When the context matches, the agent loads the full SKILL.md
  3. Supporting files in scripts/ and references/ 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 matches
  • true: 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-invocabledisable-model-invocationUserAgentUse case
true (default)false (default)YesYesMost skills
truetrueYesNoSide-effect operations (/deploy, /send)
falsefalseNoYesBackground 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

  1. Create skills/<plugin-name>/<skill-name>/SKILL.md following the template at template/SKILL.md
    • Plugin groups: grafana-core, grafana-cloud, grafana-plugins
  2. Use the spec: name (lowercase, hyphens, max 64 chars), description (max 1024 chars, include "Use when...")
  3. Run ./scripts/lint-skills.sh skills/<plugin-name> to validate
  4. Register the skill in both marketplace files under the appropriate plugin group
  5. Update README.md to list the new skill

When Adding Supporting Files

Skills can include:

  • scripts/ — executable scripts, referenced from SKILL.md with relative paths
  • references/ — 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: true for 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-skills

Cursor

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 description frontmatter instead)
  • Add internal Grafana tooling, credentials, or infrastructure-specific content
  • Hardcode script paths — use relative paths or ${CLAUDE_PLUGIN_ROOT}
  • Edit .claude-plugin/marketplace.json without making the identical change to .cursor-plugin/marketplace.json and .agents-plugin/marketplace.json

Official Resources

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.