agentleFS
itentialitential/infra-agent-skills/skills/metric-query/SKILL.md

metric-query

Skill1 starsChanged 32 days agoApache-2.0View on GitHub

Read historical or current metric samples (time series) for a resource from a monitoring platform, for troubleshooting or before/after comparison. Use when you need observed numbers for a known metric over a time window. Covers Prometheus, Zabbix, and Amazon CloudWatch. Read-only. Assumes an authenticated API client for the chosen platform is already available. Not for creating monitors or acknowledging alerts (see alert-monitor-management).

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

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

    Not for creating monitors, thresholds or alert rules, or acknowledging alerts: see alert-monitor-management.

    line 15
  2. Distinctive:

    Read-only: no monitor, alert, retention, or collection changes, and no thresholds or diagnoses are produced.

    line 34
  3. Distinctive:

    No health conclusion is drawn from an empty or failed read.

    line 49

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

Metric Query

Reads time-series samples for a named metric or monitored item over a bounded window from a monitoring platform, and reports them together with the scope and completeness of what came back.

When to use this skill

  • Fetching observed values (utilisation, error counters, latency) for a known metric and interval to support troubleshooting or to compare against an earlier window.
  • Checking whether a platform returned partial, truncated, or empty data for a query before drawing conclusions.
  • Not for creating monitors, thresholds or alert rules, or acknowledging alerts: see alert-monitor-management. Not for dashboards or log searches.

Universal concepts

This capability has no wire-level standard behind it; each platform defines its own query model. Where documented, the following hold on every platform listed:

  • A query names a series (metric or item, plus any label/dimension selection) and a time window.
  • Results carry timestamps and values, or aggregates over a period, and their meaning depends on the platform's own aggregation, resolution, and units.
  • A result can be bounded, paginated, or aggregated by the platform; a bounded or aggregated result is not the full raw record.
  • An empty result or an error does not show that a resource is healthy, idle, or unmonitored.

Procedure

  1. Identify the platform from the request and find it in references/INDEX.md. If it is not listed, stop: this skill does not cover it.
  2. Open that platform's procedure.md and follow it exactly.
  3. Report the outcome using that procedure's own status vocabulary, with the query scope, window, and any warnings or incompleteness.

Known limitations

  • Read-only: no monitor, alert, retention, or collection changes, and no thresholds or diagnoses are produced.
  • The caller supplies the metric identity; discovery is covered only where a platform procedure includes it.

Contributing to this skill

This router changes only to correct shared concepts or to add a pointer to a newly supported platform. Platform detail belongs under references/<platform>/.

Tools

An authenticated API client for the selected platform. Each platform's procedure.md names its operations and endpoints.md binds them.

Verification checklist

  • The platform, metric, and window in the result match the request.
  • Warnings, truncation, pagination state, and platform status values are carried into the report.
  • No health conclusion is drawn from an empty or failed read.

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.