seatengine-audit

Query the SeatEngine API to categorize scraped clubs as Healthy, Empty, Dead, or Errors.

Updated May 25, 2024
One-click install
npx skills add https://github.com/gioe/laughtrack --skill seatengine-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seatengine-audit
Source: https://github.com/gioe/laughtrack/tree/main/.agents/skills/seatengine-audit
Command: npx skills add https://github.com/gioe/laughtrack --skill seatengine-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bulk health audit of all visible SeatEngine-scraped clubs. Checks every club with scraper='seatengine' against the SeatEngine API and categorizes them as healthy, empty, or dead.

Core Features & Use Cases

  • Bulk health checks across all venues surfaced by the seatengine scraper
  • Categorizes venues into Healthy, Empty, Dead, and Errors with recommended remediation steps
  • Produces a consolidated report suitable for ops and product stakeholders

Quick Start

Run an audit against all visible SeatEngine-scraped clubs to generate a health report.

Frequently Asked Questions about seatengine-audit

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

FAQPage Schema
How do I run a bulk health audit for SeatEngine-scraped clubs?

To run a bulk health audit, execute the Skill from your scraper project directory to query the SeatEngine API for all clubs with scraper='seatengine'. It categorizes each club's health status and generates a consolidated report.

What is a SeatEngine API health check and how does it classify clubs?

A SeatEngine API health check queries all visible scraped clubs and categorizes their status into Healthy, Empty, Dead, or Errors. This triage process identifies data quality issues and provides a structured remediation guide for ops teams.

How do I handle API errors and missing IDs during a SeatEngine club audit?

The SeatEngine club audit gracefully handles API errors, missing IDs, and network issues during execution. It catches these exceptions and categorizes the affected clubs appropriately within the Errors section of the final health report.

Can I use this audit tool to check clubs scraped by other platforms?

No, this audit specifically targets clubs where the scraper attribute is set to 'seatengine'. It filters exclusively for SeatEngine-scraped venues to validate their API health status and does not process clubs from other scraper sources.

Do I need a specific directory setup to execute the SeatEngine health check?

Yes, you must execute the audit from the scraper project directory, specifically the apps/scraper path. Running the Skill from this location ensures the SeatEngine API queries and subsequent health report compilation function correctly.

Why does my SeatEngine scraper data show empty or dead clubs?

Empty or dead clubs are identified when the SeatEngine API returns no data or fails to respond during the bulk health audit. The Skill categorizes these venues accordingly and supplies a structured remediation guide to address the underlying data quality issues.