measure-instrumentation-spec SKILL.md skillA
measure-instrumentation-spec from product-on-purpose/pm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add product-on-purpose/pm-skills/measure-instrumentation-spec@v3.0.1Pins v3.0.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- product-on-purpose/pm-skills
- Path
skills/measure-instrumentation-spec/SKILL.md- Versions recorded
- 6
- Latest version
- v3.0.1, committed Oct 30, 2026
- First version recorded
- Jun 10, 2026
- Size
- 6,082 bytes
- Repository stars
- 790
- License
- Apache-2.0
Specifies 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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # Instrumentation Spec An instrumentation spec defines what analytics events to track, when to fire them, and what properties to include. It serves as a contract between product and engineering, ensuring consistent data collection that enables accurate measurement. Good instrumentation specs prevent the "we can't answer that question because we didn't track it" problem. ## When to Use - Before engineering implements a new feature - When defining analytics requirements for experiments - When auditing existing tracking for gaps or inconsistencies - When onboarding a new analytics tool - Before launch to ensure measurement is in place ## When NOT to Use - You are specifying the dashboard built on top of the events -> use `measure-dashboard-requirements` - You need experiment-specific metrics and variants, not product-wide tracking -> use `measure-experiment-design` - The feature itself is not yet specified (no flows to instrument) -> use `deliver-prd` first - You are analyzing data you already collect -> use `measure-experiment-results` or `measure-survey-analysis` ## Instructions …
Read the whole file at its exact version.
How to install
mdr add product-on-purpose/pm-skills/measure-instrumentation-spec@sha256:fe9ca4997138efbaThe line at the top of this page pins the label v3.0.1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ky6fnr75hfakhigc)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jun 10, 2026 and Oct 30, 2026, about one every 28 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v3.0.1 latest | 2026-10-30 | b686487 | 6,082 B | A | view · diff |
| v3.0.0 | 2026-08-21 | 69df49c | 6,082 B | A | view · diff |
| v2.3.0 | 2026-08-17 | b17f554 | 4,918 B | A | view · diff |
| v2.2.0 | 2026-07-05 | 87e423c | 4,024 B | A | view · diff |
| v2.1.0 | 2026-06-11 | 695f126 | 3,897 B | A | view · diff |
| v2.0.0 | 2026-06-10 | b8ccff6 | 3,291 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6082 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
product-on-purpose/pm-skills · 790 stars · license Apache-2.0 · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ky6fnr75hfakhigc GET https://markdownregistry.com/api/v1/resolve?ref=product-on-purpose/pm-skills/measure-instrumentation-spec GET https://markdownregistry.com/api/v1/blob/fe9ca4997138efba812395d5b6d8f6e9b2ca5b3a0140b2a7d7e56053ab14eff7
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.