メニュー
Drain the non-fatal duplicateCandidates queue in build-errors.json — confirm or reject MED-confidence cross-source duplicate pairs by writing decisions into event-duplicate-cache.json via a PR.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Daily scan of social and community feeds (r/SeattleEvents, etc.) for new event sources not already covered by 206.events. Fetches RSS feeds, extracts external URLs, deduplicates against existing sources and candidates, and appends new finds to the discovery log and candidate files. Use when triggered by the daily cron or when asked to run social source discovery.
Classify venues and events as outdoor / indoor / covered for 206.events weather badges. Reads the settingGaps work queue from build-errors.json and, in bounded batches, writes venue-level (preferred) or per-event setting resolutions into the event-uncertainty-cache, or marks them unresolvable when the setting is genuinely unknowable.
Backfill missing event and venue photos in 206.events. Reads the photoGaps work queue from build-errors.json and, in bounded batches, fills venue photos via source-YAML PRs and event photos via the event-uncertainty-cache (imageUrl), or marks them unresolvable when no photo exists.
Run the out-of-band 206.events generate job. Pulls latest code, installs deps, runs generate-outofband against the S3 bucket, and posts a summary. Auto-fixes broken rippers by spawning subagents. Use when triggered by the 11 PM UTC daily cron or when asked to run the out-of-band calendar generation.
Backfill missing event costs in 206.events. Reads the costGaps work queue from build-errors.json and, in bounded batches, fills source-wide free venues via YAML `cost:` PRs and per-event prices via the event-uncertainty-cache (--cost-* flags), or marks them unresolvable when pricing is genuinely not published.
For template copies only — discover engine features added to the upstream 206.events repo (prestomation/206events) that this copy doesn't have yet, describe each one to the owner, and stage the ones they choose to merge as per-feature draft PRs. Never run on the reference instance.
| name | duplicate-resolver |
| description | Drain the non-fatal duplicateCandidates queue in build-errors.json — confirm or reject MED-confidence cross-source duplicate pairs by writing decisions into event-duplicate-cache.json via a PR. |
Resolve outstanding cross-source duplicate candidates — pairs of events
that the build-time matcher (lib/cross-source-dedup.ts) thinks might be the
same real-world event but isn't confident enough to merge automatically.
HIGH-confidence matches are merged at build time with no human involvement.
This skill only handles the MED tier (the duplicateCandidates queue):
campus-scale venues, coordless listings, and title variants where a human (or
LLM) judgment call is needed. See docs/cross-source-event-dedup.md.
duplicateStats + duplicateCandidates in
build-errors.json (and every reporting surface).key (the unordered pair of the two events'
icsUrl + summary + date), the two events, and the match scores.event-duplicate-cache.json.confirmed pairs are merged (collapse +
attribute, exactly like a HIGH match); rejected pairs are kept separate and
never re-proposed.This is a non-fatal, self-limiting queue — like the photo/cost resolvers, it drains across builds and does not block CI.
List the queue:
python3 skills/duplicate-resolver/scripts/duplicate-cache.py candidates --limit 30
For each candidate, decide if the two events are the same occurrence.
Use the titles, locations, and urls. Confirm only when you're confident
they're the same real-world event (same festival/show, same day, same
place). When in doubt, reject — a wrong merge hides a real event, which
is worse than a visible duplicate.
Typical patterns:
Write each decision:
python3 skills/duplicate-resolver/scripts/duplicate-cache.py resolve \
--key "<key from the queue>" \
--decision confirmed \
--note "Same Seattle Center festival, two feeds"
Use --decision rejected for non-matches. --force overwrites an existing
decision.
Commit event-duplicate-cache.json and open a PR. CI reads the
committed file directly; once merged, the next build applies the decisions.
Report a summary in your reply:
🔀 Duplicate resolver: C confirmed, R rejected, Q remaining
(event, event) pair and include the date, so a
recurring cross-source duplicate is resolved per occurrence (matching the
cache design of the other resolvers).event-duplicate-cache.json for anything other than these
decisions; the build owns the matching, you own the confirm/reject.