KubeEye Cluster Inspection
kubesphere/kubesphere
Deploys KubeEye on KubeSphere and writes InspectRule and InspectPlan resources to inspect cluster health, then retrieves the inspection reports.
A skill your agent uses when changing metric CSV files, exporter-owned counters, Prometheus labels, or metric rendering.
Install Metric Contract Changes
$ npx skills add NVIDIA/dcgm-exporter --skill metric-contract-changes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/dcgm-exporter metric-contract-changes --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/NVIDIA/dcgm-exporter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/metric-contract-changes .claude/skills/metric-contract-changes && 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 "metric-contract-changes" agent skill from https://github.com/NVIDIA/dcgm-exporter/tree/main/.cursor/skills/metric-contract-changes into .claude/skills/metric-contract-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metric-contract-changes", 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/NVIDIA/dcgm-exporter/tree/main/.cursor/skills/metric-contract-changesType 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 NVIDIA/dcgm-exporter --skill metric-contract-changes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/dcgm-exporter metric-contract-changes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/dcgm-exporter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/metric-contract-changes .agents/skills/metric-contract-changes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "metric-contract-changes" agent skill from https://github.com/NVIDIA/dcgm-exporter/tree/main/.cursor/skills/metric-contract-changes into .agents/skills/metric-contract-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metric-contract-changes", 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 NVIDIA/dcgm-exporter --skill metric-contract-changes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/dcgm-exporter metric-contract-changes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/dcgm-exporter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/metric-contract-changes .cursor/skills/metric-contract-changes && 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 "metric-contract-changes" agent skill from https://github.com/NVIDIA/dcgm-exporter/tree/main/.cursor/skills/metric-contract-changes into .cursor/skills/metric-contract-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metric-contract-changes", 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/NVIDIA/dcgm-exporter.git --path .cursor/skills/metric-contract-changes--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 NVIDIA/dcgm-exporter --skill metric-contract-changes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/dcgm-exporter metric-contract-changes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/dcgm-exporter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/metric-contract-changes .gemini/skills/metric-contract-changes && 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 "metric-contract-changes" agent skill from https://github.com/NVIDIA/dcgm-exporter/tree/main/.cursor/skills/metric-contract-changes into .gemini/skills/metric-contract-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metric-contract-changes", 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 NVIDIA/dcgm-exporter metric-contract-changesInstalls 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 NVIDIA/dcgm-exporter --skill metric-contract-changes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA/dcgm-exporter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/metric-contract-changes .github/skills/metric-contract-changes && 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 "metric-contract-changes" agent skill from https://github.com/NVIDIA/dcgm-exporter/tree/main/.cursor/skills/metric-contract-changes into .github/skills/metric-contract-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metric-contract-changes", 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 NVIDIA/dcgm-exporter --skill metric-contract-changes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NVIDIA/dcgm-exporter metric-contract-changes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/dcgm-exporter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/metric-contract-changes .opencode/skills/metric-contract-changes && 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 "metric-contract-changes" agent skill from https://github.com/NVIDIA/dcgm-exporter/tree/main/.cursor/skills/metric-contract-changes into .opencode/skills/metric-contract-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metric-contract-changes", 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
metric-contract-changes- GitHub stars
- 1.9k
- Token cost
- ~149 tokens
- SKILL.md length
- 45 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when changing metric CSV files, exporter-owned counters, Prometheus labels, or metric rendering.
- Works in 5 steps: Read llms.txt, etc/AGENTS.md, and… → Identify the owning code path in… → Update code, CSV, docs, and Helm… → …
- Changing metric CSV files
- Calls go and make
- Exporter-owned counters
What it does
Metric Contract Changes is an agent skill from NVIDIA/dcgm-exporter, published by the product's own GitHub organization. Use when changing metric CSV files, exporter-owned counters, Prometheus labels, or metric rendering.
Its SKILL.md is about 150 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Monitoring and alerting and CSV and tabular files. It works with Prometheus. The repository describes itself as: NVIDIA GPU metrics exporter for Prometheus leveraging DCGM. The licence is Apache-2.0.
When your agent uses it
- Changing metric CSV files
- Exporter-owned counters
- Prometheus labels
- Metric rendering
Example prompts
- “/metric-contract-changes”
Requirements
- Docker
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read llms.txt, etc/AGENTS.md, and internal/pkg/AGENTS.md.
- Identify the owning code path in internal/pkg/counters,
- Update code, CSV, docs, and Helm examples together when behavior changes.
- Run
- Add GPU/Docker/Kubernetes validation only when the change needs that layer.
What it can do on your machine
Read from SKILL.md and the folder at commit fafd151. 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:
gomake
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.
Context cost
Metric Contract Changes loads about 149 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 45 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 NVIDIA/dcgm-exporter at commit fafd151, republished under its Apache-2.0 licence (© NVIDIA). 45 words, ~149 tokens.
Download SKILL.mdSave it as
.claude/skills/metric-contract-changes/SKILL.md (or your agent's skills folder).- name
- metric-contract-changes
- description
- Use when changing metric CSV files, exporter-owned counters, Prometheus labels, or metric rendering.
Metric Contract Changes
- Read
llms.txt,etc/AGENTS.md, andinternal/pkg/AGENTS.md. - Identify the owning code path in
internal/pkg/counters,internal/pkg/collector, orinternal/pkg/rendermetrics. - Update code, CSV, docs, and Helm examples together when behavior changes.
- Run:
go test ./internal/pkg/counters
make test-main- Add GPU/Docker/Kubernetes validation only when the change needs that layer.
© NVIDIA, 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 .cursor/skills/metric-contract-changes of NVIDIA/dcgm-exporter.
Open the folder on GitHubat commit fafd151
Compare with similar skills
Metric Contract Changes 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 |
|---|---|---|---|---|---|---|
| Metric Contract Changes this skillNVIDIA/dcgm-exporter | 1.9k | — | ~149 | Automated safety check: Pass | Apache-2.0 | |
| KubeEye Cluster Inspectionkubesphere/kubesphere | 17k | — | ~3.6k | Automated safety check: Pass | Custom licence | |
| Happy Infra Metrics and Grafanaslopus/happy | 24k | — | ~2k | Automated safety check: Notes | MIT | |
| Syncmetapawurb/hotpath-rs | 1.9k | — | ~1.2k | Automated safety check: Notes | MIT | |
| WizTelemetry Platform Servicekubesphere/kubesphere | 17k | — | ~1.8k | Automated safety check: Pass | Custom licence | |
| Collectors Prometheus Profilesnetdata/netdata | 81k | — | ~4.7k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Happy Infra Metrics and Grafana
slopus/happy
Queries live Prometheus metrics and manages Grafana dashboards as code for Happy's infrastructure, using the grafanactl CLI and the Grafana datasource proxy API.
Syncmeta
pawurb/hotpath-rs
Sync changes from the hotpath, hotpath-macros and hotpath-drain crates to their meta counterparts (hotpath-meta, hotpath-macros-meta and hotpath-drain-meta).
WizTelemetry Platform Service
kubesphere/kubesphere
Installs and configures the WizTelemetry Platform Service extension for KubeSphere, the shared API server behind its observability extensions.
Collectors Prometheus Profiles
netdata/netdata
Create, review or validate Netdata Prometheus chart profiles, exporter dashboard design, collection policy and stock semantic proofs.
Optimize Slurm Topology
NVlabs/alpasim
Optimize AlpaSim Slurm topology throughput using persistent local Prometheus/Grafana telemetry and run artifacts.
More from NVIDIA/dcgm-exporter
- Official
Local GPU Kubernetes Validation
NVIDIA/dcgm-exporter
A skill your agent uses when validating DCGM Exporter in a local GPU-backed k3d/Kubernetes environment.
- Official
Comprehensive Testing
NVIDIA/dcgm-exporter
A skill your agent uses when adding or selecting tests for DCGM Exporter changes.
Related
Works with
Categories
Questions about Metric Contract Changes
What does Metric Contract Changes do?
A skill your agent uses when changing metric CSV files, exporter-owned counters, Prometheus labels, or metric rendering. Metric Contract Changes is an agent skill from NVIDIA/dcgm-exporter, published by the product's own GitHub organization. Use when changing metric CSV files, exporter-owned counters, Prometheus labels, or metric rendering.
When should I use Metric Contract Changes?
Metric Contract Changes fits situations like: changing metric CSV files; exporter-owned counters; prometheus labels; metric rendering.
How do I install Metric Contract Changes in Claude Code?
Run `npx skills add NVIDIA/dcgm-exporter --skill metric-contract-changes -a claude-code`. Or copy the skill folder (.cursor/skills/metric-contract-changes in NVIDIA/dcgm-exporter) into .claude/skills/metric-contract-changes in your project. Claude Code loads it when a task matches its description.
How do I install Metric Contract Changes in Codex?
Run `npx skills add NVIDIA/dcgm-exporter --skill metric-contract-changes -a codex`. Or copy the skill folder (.cursor/skills/metric-contract-changes in NVIDIA/dcgm-exporter) into .agents/skills/metric-contract-changes in your project. Codex loads it when a task matches its description.
Can I use Metric Contract Changes 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 NVIDIA/dcgm-exporter --skill metric-contract-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/metric-contract-changes, .gemini/skills/metric-contract-changes, .github/skills/metric-contract-changes and .opencode/skills/metric-contract-changes in your project.
What does Metric Contract Changes need to run?
Going by SKILL.md and its folder, Metric Contract Changes needs the command-line tools its instructions call (go and make). Our summary lists: Docker.
Does Metric Contract Changes 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 Metric Contract Changes 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 Metric Contract Changes use?
Metric Contract Changes is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Metric Contract Changes use?
About 149 tokens (SKILL.md is roughly 596 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 Metric Contract Changes?
Skills that share tags, products or a category with Metric Contract Changes: KubeEye Cluster Inspection (kubesphere/kubesphere, 17k stars), Happy Infra Metrics and Grafana (slopus/happy, 24k stars), Syncmeta (pawurb/hotpath-rs, 1.9k stars) and WizTelemetry Platform Service (kubesphere/kubesphere, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Metric Contract Changes?
NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/dcgm-exporter, which has 1,891 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 18, 2026.
Source: NVIDIA/dcgm-exporter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.