export-debugger

Diagnose why a specific user was or wasn't exported to an external platform.

4|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/lytics/agent-skills --skill export-debugger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: export-debugger
Source: https://github.com/lytics/agent-skills/tree/main/export-debugger
Command: npx skills add https://github.com/lytics/agent-skills --skill export-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses why a specific user was or wasn't exported to an external platform, enabling rapid root-cause analysis of export failures or omissions.

Core Features & Use Cases

  • Trace a user's export path across the segmentation, job lifecycle, flow progress, and quiet windows to determine where a failure or miss occurred.
  • Retrieve diagnostic signals from export logs and job status to provide actionable next steps for operators or engineers.
  • Use cases include debugging why a profile was not sent to a destination, understanding export latency, and validating export configurations.

Quick Start

Run the export-debugger with a user identity and destination to generate a diagnostic report.

Frequently Asked Questions about export-debugger

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

FAQPage Schema
Why does a user profile fail to export to an external platform?

Export failures occur when segment membership checks fail, job statuses error, flow progress stalls, or quiet windows suppress output. Tracing the export pipeline path identifies the exact failure point and provides structured diagnostic guidance to resolve the omission.

How do I trace a user's export path across a data pipeline?

Trace a user's export path by validating segment membership, checking export job status, monitoring flow progress, and reviewing export logs. Execute an ad-hoc diagnostic query with a user identity and destination to generate a structured root-cause analysis report.

Can I debug export latency using ad-hoc queries?

Yes, ad-hoc queries debug export latency by retrieving diagnostic signals from export logs and job statuses. Supplying a user identity and destination allows the debugger to return actionable next steps for resolving pipeline delays.

Do I need an API token to diagnose export pipeline issues?

Yes, diagnosing export pipeline issues requires an API token and base URL to access the external platform. These credentials enable both ad-hoc queries and flow-based export diagnostics to validate configurations and retrieve logs.

What is a quiet window in an export pipeline?

A quiet window in an export pipeline is a configured period that suppresses user profile outputs to a destination. Checking quiet windows during debugging determines if an export omission is an intentional configuration rather than a pipeline failure.