Test Minecraft Exporter
dirien/minecraft-prometheus-exporter
End-to-end docker-compose test harness for the minecraft-prometheus-exporter.
Review and tune Prometheus configuration and performance. An agent skill from prometheus/prometheus-mcp.
Install Tune Prometheus Config
$ npx skills add prometheus/prometheus-mcp --skill tune-prometheus-config -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install prometheus/prometheus-mcp tune-prometheus-config --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/prometheus/prometheus-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pkg/mcp/assets/skills/tune-prometheus-config .claude/skills/tune-prometheus-config && 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 "tune-prometheus-config" agent skill from https://github.com/prometheus/prometheus-mcp/tree/main/pkg/mcp/assets/skills/tune-prometheus-config into .claude/skills/tune-prometheus-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tune-prometheus-config", 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/prometheus/prometheus-mcp/tree/main/pkg/mcp/assets/skills/tune-prometheus-configType 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 prometheus/prometheus-mcp --skill tune-prometheus-config -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install prometheus/prometheus-mcp tune-prometheus-config --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/prometheus/prometheus-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/pkg/mcp/assets/skills/tune-prometheus-config .agents/skills/tune-prometheus-config && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tune-prometheus-config" agent skill from https://github.com/prometheus/prometheus-mcp/tree/main/pkg/mcp/assets/skills/tune-prometheus-config into .agents/skills/tune-prometheus-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tune-prometheus-config", 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 prometheus/prometheus-mcp --skill tune-prometheus-config -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install prometheus/prometheus-mcp tune-prometheus-config --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/prometheus/prometheus-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/pkg/mcp/assets/skills/tune-prometheus-config .cursor/skills/tune-prometheus-config && 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 "tune-prometheus-config" agent skill from https://github.com/prometheus/prometheus-mcp/tree/main/pkg/mcp/assets/skills/tune-prometheus-config into .cursor/skills/tune-prometheus-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tune-prometheus-config", 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/prometheus/prometheus-mcp.git --path pkg/mcp/assets/skills/tune-prometheus-config--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 prometheus/prometheus-mcp --skill tune-prometheus-config -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install prometheus/prometheus-mcp tune-prometheus-config --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/prometheus/prometheus-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/pkg/mcp/assets/skills/tune-prometheus-config .gemini/skills/tune-prometheus-config && 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 "tune-prometheus-config" agent skill from https://github.com/prometheus/prometheus-mcp/tree/main/pkg/mcp/assets/skills/tune-prometheus-config into .gemini/skills/tune-prometheus-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tune-prometheus-config", 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 prometheus/prometheus-mcp tune-prometheus-configInstalls 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 prometheus/prometheus-mcp --skill tune-prometheus-config -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/prometheus/prometheus-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/pkg/mcp/assets/skills/tune-prometheus-config .github/skills/tune-prometheus-config && 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 "tune-prometheus-config" agent skill from https://github.com/prometheus/prometheus-mcp/tree/main/pkg/mcp/assets/skills/tune-prometheus-config into .github/skills/tune-prometheus-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tune-prometheus-config", 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 prometheus/prometheus-mcp --skill tune-prometheus-config -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install prometheus/prometheus-mcp tune-prometheus-config --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/prometheus/prometheus-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/pkg/mcp/assets/skills/tune-prometheus-config .opencode/skills/tune-prometheus-config && 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 "tune-prometheus-config" agent skill from https://github.com/prometheus/prometheus-mcp/tree/main/pkg/mcp/assets/skills/tune-prometheus-config into .opencode/skills/tune-prometheus-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tune-prometheus-config", 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
tune-prometheus-config- GitHub stars
- 118
- Token cost
- ~724 tokens
- SKILL.md length
- 301 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Review and tune Prometheus configuration and performance. An agent skill from prometheus/prometheus-mcp.
- Scrape interval
- SKILL.md covers Getting oriented, Topics worth exploring and Suggesting changes
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Capacity questions
What it does
Tune Prometheus Config is an agent skill from prometheus/prometheus-mcp. Review and tune Prometheus configuration and performance. Use for scrape interval, retention, storage, relabeling, flag, and capacity questions, or when Prometheus itself is slow or resource-hungry; recommends concrete config changes.
Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires the tools of a connected Prometheus MCP server
It sits in DevOps & Cloud, covering Monitoring and alerting and Web scraping. It works with Prometheus. The repository describes itself as: MCP server for LLMs to interact with Prometheus. The licence is Apache-2.0.
When your agent uses it
- Scrape interval
- Capacity questions
- Prometheus itself is slow
- Resource-hungry
Example prompts
- “/tune-prometheus-config”
Requirements
- Compatibility (from SKILL.md): Requires the tools of a connected Prometheus MCP server
What it can do on your machine
Read from SKILL.md and the folder at commit 856fb45. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 the tools of a connected Prometheus MCP server
From compatibility in the SKILL.md frontmatter.
Context cost
Tune Prometheus Config loads about 724 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 301 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 prometheus/prometheus-mcp at commit 856fb45, republished under its Apache-2.0 licence (© prometheus). 301 words, ~724 tokens.
Download SKILL.mdSave it as
.claude/skills/tune-prometheus-config/SKILL.md (or your agent's skills folder).- name
- tune-prometheus-config
- description
- Review and tune Prometheus configuration and performance. Use for scrape interval, retention, storage, relabeling, flag, and capacity questions, or when Prometheus itself is slow or resource-hungry; recommends concrete config changes.
- compatibility
- Requires the tools of a connected Prometheus MCP server
- license
- Apache-2.0
Optimizing Prometheus Configuration and Performance
Assess whether Prometheus is configured sensibly for its actual load: scrape configuration, storage and retention, query behavior, and resource headroom. The goal is a small set of concrete, justified configuration changes -- not a tour of every setting.
Getting oriented
- config returns the full scrape and evaluation configuration; flags the complete command line; runtime_info retention and Go runtime settings; build_info the version.
- tsdb_stats quantifies the load: series counts, cardinality, and which metrics and labels dominate memory.
- query and range_query against Prometheus's own metrics (prometheus_*, process_*, go_*) show how it is coping with that load.
- Prometheus's storage metrics show how the TSDB is keeping up: prometheus_tsdb_compaction_duration_seconds and prometheus_tsdb_wal_fsync_duration_seconds reflect disk pressure, and nonzero prometheus_tsdb_compactions_failed_total or prometheus_tsdb_wal_corruptions_total need attention before any tuning.
Topics worth exploring
Treat these as starting points and dig where the numbers look off:
- Ingestion pressure: samples/sec and live series, e.g. with query: rate(prometheus_tsdb_head_samples_appended_total[5m]) and prometheus_tsdb_head_series Combined with retention, these drive disk and memory needs.
- Scrape economics: jobs scraped more often than their data is useful, targets with very large sample counts, and relabeling opportunities to cut cardinality at ingest (the optimize-high-cardinality runbook digs deeper).
- Rule evaluation: prometheus_rule_group_last_duration_seconds approaching the group's interval means rule groups are running out of budget.
- Query behavior: --query.timeout, --query.max-samples, and --query.max-concurrency vs observed load; the query log (if enabled in config) identifies slow queries, and repeated expensive expressions are recording rule candidates (see review-prometheus-rules).
- Runtime tuning: GOGC and GOMAXPROCS vs allocated resources, and whether --auto-gomaxprocs / --auto-gomemlimit are available but unused.
- Retention: --storage.tsdb.retention.time/.size vs actual disk usage and how far back queries actually reach.
Suggesting changes
Provide specific prometheus.yml snippets or flag changes with the reasoning and expected impact. Recommend validating with promtool check config, applying via reload where available, and rolling out incrementally while watching Prometheus's own metrics for the effect.
© prometheus, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in pkg/mcp/assets/skills/tune-prometheus-config of prometheus/prometheus-mcp.
Open the folder on GitHubat commit 856fb45
Compare with similar skills
Tune Prometheus Config 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 |
|---|---|---|---|---|---|---|
| Tune Prometheus Config this skillprometheus/prometheus-mcp | 118 | — | ~724 | Automated safety check: Pass | Apache-2.0 | |
| Test Minecraft Exporterdirien/minecraft-prometheus-exporter | 142 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Prometheus Configurationdavila7/claude-code-templates | 32k | 12 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Qdrant Monitoring Setupqdrant/skills | 253 | 2 repos | ~874 | Automated safety check: Pass | Apache-2.0 | |
| Alloygrafana/skills | 279 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Telemetrymagnus919/agent-skills | 113 | — | ~3.9k | Automated safety check: Pass | MIT |
Similar skills
Prometheus Configuration
davila7/claude-code-templates
Complete guide to Prometheus setup, metric collection, scrape configuration, and recording rules.
- Official
Qdrant Monitoring Setup
qdrant/skills
Guides Qdrant monitoring setup including Prometheus scraping, health probes, Hybrid Cloud metrics, alerting, and log centralization.
- Official
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 /…
Telemetry
magnus919/agent-skills
Operate the observability stack that deploys as one unit: Prometheus scrape configuration, recording and alerting rules, relabeling, retention, and high availability; OpenTelemetry Collector…
KubeEye Cluster Inspection
kubesphere/kubesphere
Deploys KubeEye on KubeSphere and writes InspectRule and InspectPlan resources to inspect cluster health, then retrieves the inspection reports.
More from prometheus/prometheus-mcp
Prometheus System Health Check
prometheus/prometheus-mcp
Builds a picture of whether Prometheus itself is healthy and successfully monitoring its targets, covering readiness, firing alerts, target health and TSDB load.
Prometheus Top Resource Consumers
prometheus/prometheus-mcp
Find the top CPU, memory, or disk consumers. Use for capacity reviews, noisy-neighbor hunts, and top-N questions about which jobs, pods, or instances use the…
Prometheus Error Rate Investigator
prometheus/prometheus-mcp
Quantifies elevated error rates with PromQL, compares them to a baseline, and isolates which jobs or instances an error spike is concentrated in.
Prometheus Cardinality Optimizer
prometheus/prometheus-mcp
Finds the metrics and labels behind a Prometheus series explosion using a connected Prometheus MCP server, then proposes relabeling, dropping or recording-rule fixes with measured impact.
Prometheus Rules Review
prometheus/prometheus-mcp
Audits Prometheus recording and alerting rules through a connected Prometheus MCP server, finds gaps and noisy alerts, and drafts improved rule-group YAML.
Prometheus Missing Data Troubleshooting
prometheus/prometheus-mcp
Finds where a Prometheus metric stops existing, whether at the target, the scrape, relabeling or the query, using the tools of a connected Prometheus MCP server.
Related
Works with
Categories
Questions about Tune Prometheus Config
What does Tune Prometheus Config do?
Review and tune Prometheus configuration and performance. An agent skill from prometheus/prometheus-mcp. Tune Prometheus Config is an agent skill from prometheus/prometheus-mcp. Review and tune Prometheus configuration and performance.
When should I use Tune Prometheus Config?
Tune Prometheus Config fits situations like: scrape interval; capacity questions; prometheus itself is slow; resource-hungry.
How do I install Tune Prometheus Config in Claude Code?
Run `npx skills add prometheus/prometheus-mcp --skill tune-prometheus-config -a claude-code`. Or copy the skill folder (pkg/mcp/assets/skills/tune-prometheus-config in prometheus/prometheus-mcp) into .claude/skills/tune-prometheus-config in your project. Claude Code loads it when a task matches its description.
How do I install Tune Prometheus Config in Codex?
Run `npx skills add prometheus/prometheus-mcp --skill tune-prometheus-config -a codex`. Or copy the skill folder (pkg/mcp/assets/skills/tune-prometheus-config in prometheus/prometheus-mcp) into .agents/skills/tune-prometheus-config in your project. Codex loads it when a task matches its description.
Can I use Tune Prometheus Config 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 prometheus/prometheus-mcp --skill tune-prometheus-config -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tune-prometheus-config, .gemini/skills/tune-prometheus-config, .github/skills/tune-prometheus-config and .opencode/skills/tune-prometheus-config in your project.
What does Tune Prometheus Config need to run?
SKILL.md names no scripts, command-line tools or credentials: Tune Prometheus Config is instructions for the agent only. Compatibility (from SKILL.md): Requires the tools of a connected Prometheus MCP server.
Does Tune Prometheus Config access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Tune Prometheus Config 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 Tune Prometheus Config use?
Tune Prometheus Config is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Tune Prometheus Config use?
About 724 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Tune Prometheus Config?
Skills that share tags, products or a category with Tune Prometheus Config: Test Minecraft Exporter (dirien/minecraft-prometheus-exporter, 142 stars), Prometheus Configuration (davila7/claude-code-templates, 32k stars), Qdrant Monitoring Setup (qdrant/skills, 253 stars) and Alloy (grafana/skills, 279 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tune Prometheus Config?
prometheus (a GitHub organization) maintains it in prometheus/prometheus-mcp, which has 118 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 4, 2026.
Source: prometheus/prometheus-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.