External Events Manager

Manages the curated external_events collection in PocketBase (PRD §4.1, §5.4) and feeds events as signals. Tier filter: Tier 1/2 for candidate trends, Tier 3 optional. Key-free. Also used to add/update events from the back-office manual entry form.

guillaumemeyer Updated

File contents

External Events Manager

Collection

external_events in PocketBase. Schema (from external-events.json export):

Field Type Meaning
title text Event name
description text Optional blurb
start_date / end_date date Event window
tier select 1 (anchor) / 2 (seasonal) / 3 (filler)
type select holiday, sport, culture, tech, …
tags multi Keywords for clustering

As a signal source

  1. Read all events sorted by start_date.
  2. Keep events with tier ≤ minTier (default 2) and start_date within the horizon (default 60 days).
  3. Emit signals with source: "external_events", source_ref derived from source+title+event id, url = event id.

Management rules

  • Adding an event is idempotent on title+start_date.
  • Tier 3 events exist to fill quiet periods — mark them clearly, never let them dominate the candidate set.

guillaumemeyer/trendy/tree/main/skills/trendy/external-events-manager commit ed4903ef96

Frequently asked questions

npx skillmds@latest add guillaumemeyer/external-events-manager