metrickit

Collect and analyze on-device telemetry from MetricKit for production apps.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/harshav167/build-ios-apps --skill metrickit-harshav167
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metrickit
Source: https://github.com/harshav167/build-ios-apps/tree/main/skills/metrickit
Command: npx skills add https://github.com/harshav167/build-ios-apps --skill metrickit-harshav167

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

MetricKit telemetry can be complex to instrument, collect, and triage; this Skill centralizes on-device performance metrics and crash diagnostics for production apps, enabling proactive optimization and reliability.

Core Features & Use Cases

  • Production telemetry ingestion: manage MXMetricManager subscriptions to collect daily metric payloads and immediate diagnostic payloads.
  • Diagnostics triage and symbolication readiness: access MXCallStackTree for crash/hang analysis and prepare data for downstream symbolication.
  • Custom signposts and extended launch: instrument and review custom signpost metrics and extended launch measurement patterns for deeper performance insights.
  • Export and backend integration: serialize payloads via jsonRepresentation() and route to your analytics backend for dashboards and alerting.

Quick Start

Start a long-lived MXMetricManager subscriber at app startup and begin handling metric and diagnostic payloads.

Frequently Asked Questions about metrickit

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

FAQPage Schema
How do I collect and handle MetricKit payloads in a production app?

To collect MetricKit payloads, you set up an MXMetricManager subscriber at app startup to receive daily MXMetricPayload and immediate MXDiagnosticPayload data for production telemetry analysis.

What's the best way to prepare MXCallStackTree data for crash symbolication?

Prepare MXCallStackTree data for symbolication by accessing the crash and hang diagnostics within MXDiagnosticPayload, ensuring the raw call stack tree is extracted and ready for downstream backend processing.

How do I export MXMetricPayload data to a custom analytics backend?

Export MXMetricPayload data by serializing the telemetry payloads using the jsonRepresentation() method, then routing the resulting JSON output directly to your analytics backend for dashboarding and alerting.

Can I track custom signposts and extended launch measurements using MXMetricManager?

Yes, MXMetricManager supports tracking custom signpost metrics and extended launch measurement patterns, allowing you to instrument and review deeper performance insights alongside standard telemetry.

Does MetricKit require a long-lived subscriber for handling diagnostic payloads?

Yes, MetricKit requires a long-lived MXMetricManager subscriber started at app startup to ensure immediate diagnostic payloads and daily metric payloads are captured without data loss.

Why should I persist raw MetricKit payloads before processing diagnostics?

Persisting raw MetricKit payloads ensures no telemetry data is lost during transit, maintaining symbolication readiness and allowing reliable offline triage of MXDiagnosticPayload and MXMetricPayload records.