nodnarbnitramnodnarbnitram/claude-code-extensions/.claude/skills/grafana-billing/SKILL.md

grafana-billing

Skill16 starsChanged 7 months agoMITView on GitHub

Query Prometheus and Loki billing metrics from Grafana. Use when discussing observability costs, active series, ingestion rates, storage usage, or cardinality analysis.

Reads credentials

In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- cloudflare-vpc-servicesSkill
- code-reviewerSkill
- commit-helperSkill
- esphome-box3-builderSkill
- esphome-config-helperSkill
- frigate-configuratorSkill
- grafana-plugin-scaffoldingSkill
- ha-addonSkill
- ha-apiSkill
- ha-automationSkill
- ha-dashboardSkill
- ha-energySkill
- ha-integrationSkill
- ha-voiceSkill
- kubernetes-healthSkill
- kubernetes-operationsSkill
- linearSkill
- tauri-v2Skill
- typescript-v6Skill
- vitest-v4Skill
- vite-v8Skill

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Use this skill when the user asks about:
line 53
Distinctive:
Run the billing metrics script to gather current data
line 63
Distinctive:
Always check that API keys are set before running
line 71
Very specific:
Use --json flag when you need to process the output programmatically
line 72
Distinctive:
Default to querying both environments for comparison
line 73

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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

SKILL.md

Grafana Billing Metrics Skill

Query key billing metrics from Prometheus and Loki through Grafana's data source proxy API.

Quick Start

# Query both staging and prod (default)
uv run .claude/skills/grafana-billing/scripts/billing_metrics.py

# Query specific environment
uv run .claude/skills/grafana-billing/scripts/billing_metrics.py --env staging
uv run .claude/skills/grafana-billing/scripts/billing_metrics.py --env prod

# JSON output for automation
uv run .claude/skills/grafana-billing/scripts/billing_metrics.py --json

# Filter to specific service
uv run .claude/skills/grafana-billing/scripts/billing_metrics.py --service prometheus
uv run .claude/skills/grafana-billing/scripts/billing_metrics.py --service loki

Environment Variables Required

GRAFANA_STAGING_API_KEY - API key for staging Grafana workspace
GRAFANA_PROD_API_KEY - API key for prod Grafana workspace

Key Metrics Captured

Prometheus

Metric	Description
Active Time Series	Current count of active series (billing dimension)
Samples/sec	Ingestion rate (DPM = samples/sec * 60)
TSDB Storage	On-disk storage bytes
Top Cardinality	Top 10 metrics by series count

Loki

Metric	Description
Ingestion Rate	GB/day being ingested
Total Bytes	Cumulative bytes received
Active Streams	Number of active log streams
Memory Chunks	Chunks held in memory

When to Use

Use this skill when the user asks about:

Observability billing or costs
Active time series counts
Prometheus cardinality analysis
Loki ingestion rates
Storage usage for metrics or logs
Comparing staging vs production usage

Instructions for Claude

Run the billing metrics script to gather current data
Present the results in a clear, formatted way
Highlight any concerning metrics (high cardinality, rapid growth)
Compare staging vs prod if both are queried
Suggest cost optimization if metrics are unusually high

Critical Rules

Always check that API keys are set before running
Use --json flag when you need to process the output programmatically
Default to querying both environments for comparison
Handle errors gracefully - missing data sources should not crash the script

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.

Check your setup, free