skills.rest
gamedevpl
gamedevplOFFICIAL
Explore all skills by this author →
WebsiteGitHub

product-instrumentation

Coordinate telemetry contracts for privacy-safe product measurement across game platform features.

7|23|Updated Aug 9, 2015
Search Tags:#observability#event tracking#telemetry#privacy#game analytics#funnel analytics#product instrumentation
One-click install
npx skills add https://github.com/gamedevpl/www.gamedev.pl --skill product-instrumentation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-instrumentation
Source: https://github.com/gamedevpl/www.gamedev.pl/tree/main/.claude/skills/product-instrumentation
Command: npx skills add https://github.com/gamedevpl/www.gamedev.pl --skill product-instrumentation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents user-facing features from shipping without reliable, privacy-preserving measurement, ensuring product health, creator conversion, game engagement, acquisition, retention, and build economics remain answerable from telemetry.

Core Features & Use Cases

  • Telemetry Architecture: Coordinate browser, API, storage, iframe, visit, and creator telemetry changes across their required contracts.
  • Privacy and Safety Invariants: Preserve anonymous play and visit streams, ephemeral correlation, coarse acquisition data, hostile-input validation, rate limits, caps, and aggregate-only reporting.
  • Event Vocabulary and Metrics: Extend stable event names, funnel stages, game health signals, shared-zone outcomes, scorecards, and creator metrics without breaking existing analyses.
  • Use Case: Use this Skill when adding or changing play, creation, sign-in, sharing, party mode, dashboards, or any metric so the implementation includes the required events, validation, aggregation, retention updates, and tests.

Quick Start

Use the product-instrumentation skill to review this feature change, identify the affected measurement questions, update every required telemetry contract, and list the tests and aggregates needed before release.

Frequently Asked Questions about product-instrumentation

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

FAQPage Schema
How do I add event tracking to new game features without breaking existing telemetry?▼

To add event tracking safely, synchronize browser and API schemas, validate hostile inputs, and extend stable event vocabularies and funnel stages without breaking existing analyses. Update required telemetry contracts, aggregates, and retention policies before release.

What is product instrumentation for game analytics?▼

Product instrumentation for game analytics preserves reliable, privacy-safe measurement across user-facing features. It coordinates telemetry architecture, event vocabularies, and dashboards so product health, engagement, and retention remain answerable from collected data.

How do I maintain privacy invariants when implementing telemetry code?▼

Maintain telemetry privacy by separating anonymous play and visit streams, enforcing ephemeral correlation, applying rate limits and caps, and restricting outputs to aggregate-only reporting. Validate hostile inputs and bound collection to preserve user anonymity.

Does my event tracking need synchronized browser and API schemas for party mode?▼

Yes, party mode event tracking requires synchronized browser and API schemas to coordinate telemetry contracts. You must update required events, aggregates, and retention changes across both layers to ensure reliable measurement.

What's the best way to validate funnel analytics implementation before shipping?▼

Validate funnel analytics by identifying affected measurement questions, updating every required telemetry contract, and listing focused tests and aggregates needed before release. Ensure hostile-input validation and bounded collection are implemented.

Why does my game telemetry require anonymous stream separation?▼

Game telemetry requires anonymous stream separation to preserve privacy invariants during play and visit tracking. Separating streams, enforcing ephemeral correlation, and limiting collection to aggregate-only reporting prevents exposing identifiable user data.

Related Skills

Explore More Software Engineering Skills→
clarinovistclarinovist

analytics-tracking

Define GA4 and GTM tracking plans with event catalogs and validation checklists.

Community
Advanced
TheCraigHewittTheCraigHewitt
7.3k

email-sequence

Generate email sequences for onboarding, nurture, and re-engagement campaigns.

Community
Intermediate
GoldenZeroGoldenZero
1

health-equity-monitoring

Monitor health disparities across demographic, socioeconomic, and geographic dimensions using standardized equity indices.

Community
Advanced
lciaccilciacci

posthog-analytics

Instrument PostHog event tracking, feature flags, and dashboards across web and backend apps.

Community
Advanced