Daily Hacker News digest in Slack

Build an agent workflow that posts a daily Hacker News digest to Slack every weekday morning, filtered to a topic list I control.

Trigger: cron, every weekday (Monday through Friday) at 8:00am in my local timezone.

Inputs the agent should accept and let me edit later:

- topics: a list of plain-English topics I care about (default to: AI, infrastructure, devtools, founders).

- slack_channel: the Slack channel (or channel id) to post the digest in.

- story_pool_size: how many top stories to consider per run (default 30, allow up to 100).

- min_score and min_comments: optional thresholds, default 0.

What the agent should do on each run:

1. Call the hacker-news Get Top Stories operation to fetch the current top story ids in front-page ranking order. Take the first story_pool_size ids.

2. Hydrate each id by calling the hacker-news Get Item operation in parallel. Skip any item where deleted=true or dead=true. Keep only items where type is 'story' or 'job'.

3. Filter the hydrated stories down to ones that match the user's topics. Match on title and the url/domain; treat topics generously (for example 'AI' should match LLMs, agents, models). Drop stories that don't clearly relate to any topic. Also drop stories below min_score or min_comments if set.

4. Deduplicate against the previous run. Persist the set of story ids included in the last digest (in workflow memory / state) and skip any id that appeared yesterday. After posting, overwrite that set with today's ids.

5. For each surviving story, write a 2 to 3 bullet summary covering what the story is about and why it matters. Use the HN discussion context (the linked url and, when useful, the top one or two comments fetched via Get Item on the kids array) so the summary reflects what people are actually arguing about, not just the headline. Prioritize stories with high comment activity when ranking within a topic.

6. Group the digest by topic. Within each topic, sort by comment count descending, then score descending. For each story include: the title (linked to the article url, or to the HN discussion if there is no external url), the score, the comment count, and a direct link to the HN discussion (https://news.ycombinator.com/item?id=<id>), followed by the bullet summary.

7. Post the digest as a single message to slack_channel using the slackbot Send a Message operation. Format it with Slack markdown: a short header line with today's date and the topic list, then one section per topic with a bold topic name and the ranked story entries underneath. Keep the whole thing skimmable in under a minute. If nothing matches the topics, post a one-line 'No matching stories today' note instead so I know the run succeeded.

Use the slackbot integration (not the user-token slack integration) so the digest is attributed to a shared bot rather than a person. Hacker News needs no authentication.