← ClaudeAtlas

event-digestlisted

Use this skill when the user asks about IT/ML meetups and conferences to attend — «какие митапы на неделе», «куда сходить», «добавь канал с мероприятиями», «что я записал на “Иду”», «как прошёл митап», «покажи разборы походов» — or wants the event digest, the «Иду» button, the goal-the-day-before ping or the debrief ping set up, changed or debugged. It pulls Telegram channels and RSS (Habr «Конференции») through the job-digest RSSHub, keeps Moscow offline events, sends each to Telegram with «Иду / Скип», then asks for a one-line micro-goal the evening before and a debrief an hour after the end.
Sapar-hub/sapar-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill Sapar-hub/sapar-skills
# event-digest The point is going, not reading: a digest item ends in «Иду», then two questions in Telegram. Pipeline: `feeds.txt` → RSSHub (shared with job-digest) → `scripts/events.py run` (post-level filter, date parsing, dedup in sqlite) → `tg send` with «Иду / Скип» → `events.py tick` every 5 min: - «Иду» with a parsed day and time → `going`; without a time or a day → the bot asks «Когда?» (two tries). - The day before at 20:00 (or right away if «Иду» is pressed later) → «Микроцель — одна строка». - An hour after the end (start + 3 h when the end is unknown) → `где было хуже всего → тело → слово → что сделал`. - «не иду» / «не был» in any answer → `cancelled`. Silence → the stage is skipped (`no_report` after the event). - One open question at a time: tg-bridge routes a plain (non-reply) text to the only open ask, so a second one waits for the next tick. Files: - code: `scripts/events.py` (imports `../job-digest/scripts/digest.py` for feeds, text and the db) - config: `~/.config/event-digest/feeds.txt` (`<url> [link]`), `keywords.txt` - state: `~/.local/state/event-digest/items.db` — `items` (as in job-digest) + `events` (`id, start, end, start_is_guess, end_is_guess, status, goal, report, asked, ask_pid`) ## Answering ```bash python3 -I scripts/events.py show --days 1 # upcoming events with status (new/going/need_date/…) python3 -I scripts/events.py show --days 7 --all # everything fetched, + passed / - filtered out python3 -I scripts/events.py log