instrument-metric
From the author
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.
Install
npx skills add harness/harness-skills --skill instrument-metric -a claude-code
Installs to .claude/skills/instrument-metric/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- choose-metricharness/harness-skillsRecommend primary/guardrail metrics for an experiment or rollout, judged against a good-metric checklist. Checks existing metrics and event health, surfaces auto-created guardrails. Doesn't create or attach metrics — see create-metric / instrument-metric / manage-experiments. Trigger phrases: choose/pick a metric, primary metric, guardrail metric, what to monitor.Other★ 125
- create-metricharness/harness-skillsCreate a Harness FME metric: helps decide what to measure, suggests candidate metrics from application code, resolves traffic type and event type IDs, drafts the payload, then creates. Use when asked to create or define a new metric, decide what to measure, or get metric suggestions from application code. Doesn't attach metrics to experiments (manage-experiments) or add the tracking call (instrument-metric). Trigger phrases: create/define a metric, new metric, what metrics should we create, suggest metrics.Engineering★ 125
- observability-instrumentationBlackBeltTechnology/pi-agent-dashboardMake runtime behavior visible and diagnosable. Use on triggers like "add logging/metrics/tracing", "instrument this", "add alerting", "we can't tell what happened in prod", or when a feature needs evidence it works at runtime. Fills an instrumentation gap not covered by the project's existing skills. Not a ship or release workflow.DevOps★ 331
- manage-experimentsharness/harness-skillsCreate, update (metrics, dates, description, hypothesis, baseline/comparison treatments, status), or delete Harness FME feature-flag experiments. Delegates metric selection to choose-metric, metric creation to create-metric, event wiring to instrument-metric, results to review-experiment-results, flag/definition prep to create-feature-flag and update-flag-targeting. Use when asked to create, modify, pause, resume, complete, or delete an experiment. Do not use for explaining results (review-experiment-results). Trigger phrases: create experiment, set up A/B test, design experiment, launch test, update experiment, pause/resume/complete experiment, delete experiment.Testing★ 125
- monitor-experimentwanshuiyin/Auto-claude-code-research-in-sleepMonitor running experiments, check progress, collect results. Use when user says "check results", "is it done", "monitor", or wants experiment output.Other★ 18K
- measure-instrumentation-specproduct-on-purpose/pm-skillsSpecifies what analytics events to track, when they fire, and what properties to include, as a contract between product and engineering that prevents undertracked features. Use before engineering builds a feature or when auditing existing tracking for gaps. For the dashboard built on top of these events, use measure-dashboard-requirements instead.Planning★ 757
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in