state-data-onboarding

Automate onboarding, normalization, and validation of state crash data into the CrashLens pipeline.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ecomhub200/Douglas_County_2 --skill state-data-onboarding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: state-data-onboarding
Source: https://github.com/ecomhub200/Douglas_County_2/tree/main/.claude/skills/state-data-onboarding
Command: npx skills add https://github.com/ecomhub200/Douglas_County_2 --skill state-data-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboarding new state crash data into CrashLens requires aligning schemas, building normalizers, downloading data, and configuring registries. This skill provides a repeatable, end-to-end workflow to streamline these tasks and reduce manual integration effort.

Core Features & Use Cases

  • Onboard new state crash data into the CrashLens pipeline with consistent normalization to a Virginia-standard schema.
  • Develop and register normalizers, update value mappings, and keep the pipeline aligned with evolving data sources such as ArcGIS, Socrata, or direct downloads.
  • Create and manage download scripts and the data registry to enable automated, repeatable ingestion across jurisdictions.
  • Provide comprehensive onboarding documentation and validation steps to ensure frontend filters and reports behave as expected.
  • Use Case: adding a new state or handling a schema change when a state updates its crash data format.

Quick Start

Run the onboarding workflow to integrate a new state's crash data using the Virginia-standard normalization pipeline.

Frequently Asked Questions about state-data-onboarding

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

FAQPage Schema
How do I onboard new state crash data into a normalized pipeline?

Onboarding new state crash data requires aligning schemas, building normalizers, and configuring registries. This skill provides a repeatable workflow to automate these tasks and reduce manual integration effort.

What is the best way to normalize crash data from different states to a standard schema?

Normalizing crash data to a standard schema involves developing and registering normalizer classes that map values to a baseline. This skill uses a Virginia-standard normalization pipeline to ensure consistent data alignment across jurisdictions.

How do I handle a schema change when a state updates its crash data format?

Handling a crash data schema change requires updating value mappings and normalizer logic to match the new format. This skill supports evolving data sources by allowing you to modify normalizers and maintain pipeline alignment.

Can I automate crash data downloads from ArcGIS or Socrata sources?

Automating crash data downloads from ArcGIS or Socrata requires creating and managing download scripts. This skill enables automated, repeatable ingestion across jurisdictions by configuring these scripts within the data registry.

Does the crash data onboarding workflow support validation for frontend filters?

Validating crash data onboarding ensures frontend filters and reports behave as expected. This skill provides comprehensive onboarding documentation and validation steps to verify that the normalized data supports accurate reporting.

Why do I need a data registry for ingesting multi-jurisdiction crash data?

A data registry is needed to enable automated, repeatable ingestion across multiple jurisdictions. This skill configures the registry alongside download workflows to manage diverse state data sources systematically.