document-curator-incident

Supply one or more post links and the Skill reads each source, verifies the curator and affected vaults, then writes or merges an incident record in the curator's YAML file under eth_defi/data/feeds/curators. Every claim is attributed with inline source links.

It reads the curator's existing incidents list and merges when a record describes the same underlying event, even if titles, dates, or URLs differ. An overlapping link is treated as definitive evidence the record already exists; separate events get separate records.

The Skill uses indexed search results or another public copy of the same post as evidence. An inaccessible page alone is never treated as evidence, and unverified allegations are attributed as third-party claims rather than stated as fact.

Incidents are classified as collapse, significant_loss, minor_loss, misleading, or questionable_behaviour. Severity is set to collapse, significant_loss, minor_loss, or other based on demonstrated impact, with misleading and questionable_behaviour normally mapping to other.

The Skill stops and directs you to use the add-curator skill first. It never creates an incomplete curator record as part of the incident documentation workflow.

The Skill runs the repository's load_feeder_metadata schema loader against the edited file to confirm the incidents parse correctly, then runs git diff --check. It reports the curator, add-or-merge outcome, date, classification, and evidence counts.