Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →product-on-purpose/measure-instrumentation-spec
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.
Passed 17 of 21 test cases with the skill, and 17 of 21 without it.
and 2 more in the full report
3 fixed15 passed either way1 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are adding an AI support assistant to our web dashboard that answers subscriber questions using retrieved knowledge articles. Write a complete instrumentation specification for this feature. Include the tracked event dictionary, triggers, event properties, user traits, trace capture rules for LLM prompts/responses/context, sensitive data and privacy precautions, and QA test steps.
| Checked | Without skill | With skill |
|---|---|---|
| Specifies egress minimization requirements before trace transmission | Missed | Passed |
| Specifies trace access permissions with explicit read logging | Missed | Passed |
| Specifies oversampling of flagged trace interactions rather than uniform sampling | Missed | Passed |
The instructions your model reads when the skill loads.
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.
measure-dashboard-requirementsmeasure-experiment-designdeliver-prd firstmeasure-experiment-results or measure-survey-analysisWhen asked to create an instrumentation spec, follow these steps:
Define Analytics Goals Start with the questions you need to answer. What will you measure? What decisions will this data inform? This prevents over-instrumentation while ensuring nothing important is missed.
Identify Events to Track
List each user action or system event that should be tracked. Follow consistent naming conventions (typically noun_verb or verb_noun in snake_case). Each event should represent a distinct, meaningful action.
Specify Event Triggers For each event, describe exactly when it fires. Be precise: "When user clicks Submit button" vs. "When form is submitted successfully." These are different events with different meanings.
Define Event Properties List the properties (attributes) attached to each event. Include property name, data type, description, and example values. Properties provide context that makes events useful.
Document User Properties Identify persistent user-level attributes that should be associated with all events (e.g., subscription tier, account creation date). These enable segmentation in analysis.
Address PII and Privacy
test cases passed, vs 17 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.