event-scraper

Detect a site's CMS or API pattern and prioritize API-based data sources before HTML scraping.

7|2|Updated Nov 23, 2025
One-click install
npx skills add https://github.com/MattB543/asheville-event-feed --skill event-scraper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-scraper
Source: https://github.com/MattB543/asheville-event-feed/tree/main/claude/event-scraper
Command: npx skills add https://github.com/MattB543/asheville-event-feed --skill event-scraper

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Asheville Event Feed expansion requires a reliable, API-first approach to adding new event sources, avoiding browser automation and ensuring scalable pipelines across multiple data sources.

## Core Features & Use Cases

  • Provides a repeatable workflow to detect CMS platforms, locate APIs, and implement scrapers for API-based, HTML/JSON-LD, and hybrid data sources.
  • Includes rigorous testing patterns, timezone handling, and production-ready validation to ensure data integrity and reliability.
  • Use Case: Add a new source like a venue's API or a JSON-LD feed and deploy a scraper that ingests events into the AVL Event Feed with correct timezones and deduplication.

### Quick Start Begin by detecting the target CMS and attempting known API endpoints before any scraping, then implement an API-first scraper following the phased workflow.

Frequently Asked Questions about event-scraper

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

FAQPage Schema
What is API-first web scraping and when should I use it over HTML scraping?

API-first web scraping detects a site's CMS or API pattern and prioritizes structured API endpoints for data extraction before attempting HTML parsing. Use this approach to build scalable, reliable event ingestion pipelines that avoid fragile browser automation.

How do I build a web scraper that handles mixed API and JSON-LD data sources?

To build a web scraper for mixed sources, follow a phased workflow that explores API discovery first, then falls back to HTML or JSON-LD extraction. Implement hybrid pattern handling to ingest structured event data from multiple source types reliably.

How do I handle timezones when scraping event data from multiple websites?

Handle timezones in event scraping by applying structured testing workflows that validate timezone conversions during phased development. This ensures production-ready pipelines maintain data integrity and correct event timestamps across diverse data sources.

What's the best way to test web scrapers for production readiness?

The best way to test web scrapers for production readiness is using a strict workflow from exploration to production. This includes phased validation, API discovery testing, and graceful error handling to ensure data integrity and reliability.

Can I use this API-first scraping workflow for event feeds outside of Asheville?

Yes, you can apply this API-first scraping workflow to any event feed expansion. The repeatable workflow detects CMS platforms, locates APIs, and implements scrapers for API-based, HTML/JSON-LD, and hybrid data sources across multiple target sites.

Why does my HTML web scraper break when the target website changes its layout?

HTML web scrapers break on layout changes because they depend on fragile DOM structure. Prioritizing API-based data sources and implementing hybrid patterns with graceful error handling creates resilient pipelines that avoid brittle browser automation.