菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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.
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.
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.
基于 SOC 职业分类
| name | photo-resolver |
| description | 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. |
Backfill photos for events and venues that don't have one. The data model
stores image URLs only (never image bytes), in the imageUrl field.
There are two kinds of gap, fixed two different ways:
| Gap | Where it lives | How to fix |
|---|---|---|
| Venue photo | imageUrl: in the source YAML (ripper / external / recurring) | Open a PR adding imageUrl: (like geo-resolver edits venue coords) |
| Event photo | event-uncertainty-cache.json keyed source:eventId | Write an imageUrl resolution via uncertainty-cache.py resolve --image-url (committed file) |
Both are non-fatal todo queues, like geo and event-uncertainty. The queue
self-limits over time: once a photo is found (or confirmed unavailable and
marked unresolvable), the item drops off.
python3 skills/photo-resolver/scripts/photo-gaps.py stats
Note the coverage % — this is your baseline to beat. Then list the gaps:
python3 skills/photo-resolver/scripts/photo-gaps.py venues --limit 25
python3 skills/photo-resolver/scripts/photo-gaps.py events --limit 25
(Pass --url output/build-errors.json to inspect a local build, or
--url https://206.events/preview/<PR>/build-errors.json for a PR preview.)
Do not try to drain the whole queue in one run. Pick a batch — e.g. the first 25 items — and resolve those. The queue is drained across many runs, exactly like the geo and uncertainty backlogs. Prefer venues first (one PR covers many future events at that venue) and high-traffic sources.
https://…/image.jpg URL. Link only — never download bytes.imageUrl: "<url>" to the source's YAML next to its geo: block:
sources/<name>/ripper.yaml (ripper-level, or per-calendar for a
multi-branch source)sources/external/<name>.yamlsources/recurring/<name>.yamlFor each event gap, fetch the source page (url from the queue), find a
representative image link, and write it into the cache:
python3 skills/event-uncertainty-resolver/scripts/uncertainty-cache.py resolve \
--key "<source>:<eventId>" --image-url "https://example.com/event.jpg" \
--evidence "<source page url>"
If the source genuinely has no image, mark it unresolvable so it drops off the queue and isn't re-investigated:
python3 skills/event-uncertainty-resolver/scripts/uncertainty-cache.py resolve \
--key "<source>:<eventId>" --unresolvable --reason "no image on source page"
The build's applyImageBackfill pass applies these imageUrl resolutions on
the next build (see docs/event-uncertainty.md and docs/photos.md).
skipEventPhotos → PR)When a source has a venue imageUrl but its event pages carry no
harvestable per-event image (only a generic site/category logo, e.g.
sources/seattle_makers), don't mark its events unresolvable one at a time —
every new event the venue publishes would re-enter the queue. Instead retire the
whole source's event-photo backfill in one PR:
skipEventPhotos: true at the ripper level of sources/<name>/ripper.yaml
(alongside the venue imageUrl:), with a one-line comment noting what you
verified.The events keep displaying the venue photo; they just stop appearing in
eventGaps. Only use this when per-event photos genuinely don't exist — if the
ripper could be enhanced to extract a real per-event image, prefer that.
See the skipEventPhotos section in docs/photos.md.
After venue PRs merge / event resolutions are written, re-trigger the build so the changes take effect, then re-check coverage:
python3 skills/photo-resolver/scripts/photo-gaps.py stats
Summarize:
event-uncertainty-cache.json;
commit them in the same PR (CI reads the committed file — no S3). See
docs/github-native-caches.md.source-from-event (poster images).