Data Flow Tracker Skill

Trace data flow across RAW, DERIVED, PACKAGES, and DATABASE stages.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fstr21/sportsbot --skill data-flow-tracker-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Data Flow Tracker Skill
Source: https://github.com/fstr21/sportsbot/tree/main/.claude/skills/data-flow-tracker
Command: npx skills add https://github.com/fstr21/sportsbot --skill data-flow-tracker-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rich, and includes scripts (resource) components.

What problem does it solves? When data is missing in the final database, it's difficult and time-consuming to pinpoint exactly where it got lost in a multi-stage pipeline. This Skill provides a clear, step-by-step trace, helping you quickly diagnose and resolve data flow issues.

Core Features & Use Cases

  • Multi-Stage Trace: Traces a specific game or date through all pipeline stages: raw capture, derived data, packaged artifacts, and database ingestion.
  • Loss Point Identification: Clearly identifies at which stage data was lost or failed to progress (e.g., found in raw but not derived).
  • Actionable Diagnosis: Provides plain English explanations and recommendations for resolving data flow issues, guiding you to the next steps.
  • Use Case: If a user reports "game X is not in the database," use this Skill to trace game X and determine if it was captured, derived, packaged, or if ingestion failed.

Quick Start

Trace a specific NFL game through the pipeline

python .claude/skills/data-flow-tracker/scripts/trace_data.py --sport nfl --date 2025-10-23 --game-id 12345

Frequently Asked Questions about Data Flow Tracker Skill

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

FAQPage Schema
How do I trace where data gets lost in my pipeline?

Data flow tracing identifies the exact stage where data disappears between capture and database. This Skill traces a specific game or date through raw, derived, packaged, and database stages, pinpointing loss points and providing plain-English diagnostics to resolve missing data issues.

Can I track a specific game through multiple pipeline stages?

Yes. This Skill traces a single game across raw capture, derived data, packaged artifacts, and database ingestion, showing timestamps and status at each stage so you can see where it stalled or failed to progress.

What should I do when data exists in raw artifacts but not in the database?

Use data flow tracing to isolate the failure point—whether it stopped during derivation, packaging, or ingestion. The Skill delivers stage-by-stage timestamps and actionable recommendations to guide your next debugging step.

Does this work with sports data pipelines?

Yes. The Skill is designed for sports data contexts, supporting tracing across game capture, transformation, packaging, and database stages with read-only safety and graceful handling of missing records.

How do I get started tracing a data flow issue?

Provide the sport, date, and game ID to the trace script. It returns a step-by-step breakdown showing where your data exists and where it stops, eliminating manual log hunting across pipeline stages.

What are the limitations of this tracing approach?

The Skill operates read-only and works within existing pipeline stages. It excels at loss-point identification but does not modify or repair data; use findings to guide upstream corrections.