beautysale-crawl-ingest-debugger

Trace crawl ingestion failures from API input to persistence in the BeautySale repository.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/spandios/vibe-utils --skill beautysale-crawl-ingest-debugger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beautysale-crawl-ingest-debugger
Source: https://github.com/spandios/vibe-utils/tree/main/skills/beautysale-crawl-ingest-debugger
Command: npx skills add https://github.com/spandios/vibe-utils --skill beautysale-crawl-ingest-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps debug issues within the BeautySale repository related to crawl ingestion, processing, and data accuracy, ensuring that data is correctly captured and reflected.

Core Features & Use Cases

  • End-to-End Tracing: Follows the data flow from API input through persistence and downstream effects.
  • Root Cause Analysis: Identifies the earliest broken stage in the crawl ingestion pipeline.
  • Use Case: When users report missing products or incorrect pricing on the BeautySale platform, this skill helps pinpoint whether the issue lies in the initial crawl, data normalization, price change detection, or notification system.

Quick Start

Use the beautysale-crawl-ingest-debugger skill to trace a crawl ingestion issue in the BeautySale repository.

Frequently Asked Questions about beautysale-crawl-ingest-debugger

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

FAQPage Schema
How do I debug crawl ingestion failures when crawled data is missing or duplicated?

Debug crawl ingestion failures by tracing data flow from API input through persistence to downstream effects. Identify the earliest broken stage in the pipeline, whether in crawl processing, data normalization, or price snapshot creation, to ensure fixes target the correct component.

Why does price change detection show incorrect pricing after a crawl ingestion run?

Incorrect pricing during price change detection often stems from stale or incorrect data in the crawl ingestion pipeline. Trace the issue end-to-end from API input to persistence to pinpoint whether the root cause lies in initial crawl processing or downstream notification side effects.

What is the best way to trace missing products in a crawl data pipeline?

Trace missing products in a crawl data pipeline by performing root cause analysis across the ingestion workflow. Identify the earliest broken stage between API input, data normalization, and persistence to ensure the fix lands on the correct component.

How do I identify which component is causing crawl ingestion side effects?

Identify the component causing crawl ingestion side effects by tracing the data flow from API input to downstream notifications. Pinpoint the earliest broken stage in the processing logic to ensure fixes are applied to the correct pipeline component.

Can I use this debugger for crawl result processing and price snapshot creation issues?

Yes, this debugger applies to crawl result processing and price snapshot creation issues. It traces data flow from API input through persistence to identify whether the issue lies in initial crawl ingestion, data normalization, or price change detection.

What are the limitations of debugging crawl ingestion without a structured workflow?

Without a structured workflow, debugging crawl ingestion risks applying fixes to the wrong component. Identifying the earliest broken stage in the data pipeline is required to correctly address issues in crawl processing, price snapshot creation, or notification side effects.