critic-instrumentation

Verify contract behaviors have corresponding analytics events and mapped success metrics.

3|Updated May 20, 2026
One-click install
npx skills add https://github.com/iampawan/Manifest --skill critic-instrumentation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: critic-instrumentation
Source: https://github.com/iampawan/Manifest/tree/main/skills/critic-instrumentation
Command: npx skills add https://github.com/iampawan/Manifest --skill critic-instrumentation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill verifies that every behavior in a contract has an associated analytics event and that success metrics are mapped correctly, ensuring reliable post-launch verification.

Core Features & Use Cases

  • Behavior Analytics: Checks if each behavior in a contract has an analytics event.
  • Event Mapping: Ensures success metrics map to existing events.
  • Verification: A crucial component for post-launch feature verification.
  • Use Case: When developing a new feature, this Skill helps ensure that all necessary data for post-launch analysis is in place.

Quick Start

Verify the instrumentation of the feature in the contract by running 'contract-verify'.

Frequently Asked Questions about critic-instrumentation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify behavior analytics and event mapping for post-launch feature analysis?

Verifying behavior analytics requires checking that every behavior in a contract has a corresponding analytics event and that success metrics are properly mapped to ensure data integrity for post-launch verification.

What is contract analysis for event mapping in post-launch verification?

Contract analysis for event mapping is the process of validating that feature behaviors defined in contracts have matching analytics events, ensuring reliable data collection for post-launch success metric evaluation.

How do I check if success metrics map to existing analytics events?

Checking if success metrics map to existing events involves analyzing contract definitions to verify that each defined behavior has an associated analytics event for accurate post-launch feature verification.

Can I use contract verification to ensure data integrity for feature analysis?

Yes, contract verification ensures data integrity for feature analysis by confirming that all necessary analytics events and success metrics are properly mapped before post-launch verification begins.

When do I need to run analytics event verification for contract behaviors?

You need to run analytics event verification when developing a new feature, ensuring all necessary data for post-launch analysis is in place and that contract behaviors have corresponding events mapped.

What are the limitations of manual event mapping verification for post-launch features?

Manual event mapping verification lacks the automated analysis of contract definitions needed to comprehensively verify behavior analytics, risking missing data integrity issues during post-launch feature verification.