Menu

Individual skill

instrument-metric

0upvotes

Wire up a track() call for a metric's event, placed at the real outcome, and verify it arrives. Doesn't create the metric (create-metric) or choose it (choose-metric). Trigger phrases: instrument this event, add a track call, wire up tracking, verify the event arrives.

skills/fme/instrument-metric/SKILL.md

Read pinned source

Source commit e01dc7275f7e261f390be2fe7be4559feadb74ef

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
134
Repository last updated
Oct 28, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Instrument Metric

Wire up the `track()` call an FME metric needs, then verify the event is actually arriving — don't declare success on code changes alone. Key = the same key `getTreatment` uses (attribution fact); value units must match the metric's `format` (ms vs s, dollars vs cents) — a wrong unit gives silently wrong results. Related: `/create-metric` creates metrics; `/choose-metric` recommends which metrics to use.

## Tools

Works through the Harness MCP server or the Harness CLI; names are from [tool-map.md](../../../references/fme/tool-map.md).

| Operation | MCP | CLI |
|-----------|-----|-----|
| Get metric | `harness_get` · `fme_metric` · `params: { metric_id }` | `harness get metric <id> --json` |
| Get event type | `harness_get` · `fme_event_type` · `params: { event_type_id }` | `harness get event_type <event-name> --json` |

## Instructions
Back to top