Skip to content

Weekly city events digest for your interests

Once a week it scans the event sites people actually use in your city, drops anything you are already registered for, and ranks the rest against interests you wrote in your own words. You get a short issue with a reason for each pick and a link to RSVP yourself.

PersonalWorks with Claude Code · Claude Desktop with MCP+1Community example

What it does

  • Reads the event platforms set up for your city, plus any club or coworking space you belong to
  • Pulls what you are already registered for from your calendar
  • Ranks up to 8 featured events with a specific reason tied to your interests
  • Flags clashes with existing calendar items and standing commitments
  • Lists everything else that survived deduplication, tagged by category, and says when a source failed

Your approval boundaries

Read only

Reads connected data. It does not send messages or change records.

You decide what happens next.

More about this workflow

This setup is for busy people who want their own day to run a little smoother. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it reads the event platforms set up for your city, plus any club or coworking space you belong to. Next, it pulls what you are already registered for from your calendar. Then it ranks up to 8 featured events with a specific reason tied to your interests. After that, it flags clashes with existing calendar items and standing commitments. Finally, it lists everything else that survived deduplication, tagged by category, and says when a source failed. It works with your web fetch and calendar, each on its own login with limited access.

You get the finished work, ready to read. It only reads, so nothing is sent, changed or paid for. You decide what to do with it.

“This skill never registers, pays, or submits anything on your behalf.”
vincenzodivincenzo vincenzodivincenzo on GitHub · Oct 18, 2026
Before you startWeb fetch · Calendar accessRead-only permissionsClaude Code or Claude Desktop with MCP
Explore required tools and model recommendations

Tools and access

  • Web fetch

    Handles the web fetch part of this job. Grant public pages, no logged-in sessions.

    API required: No. Built into most agent harnesses. It reads public pages with no login.

    No sign-up needed
  • Google Calendar

    Handles the calendar part of this job. Grant read-only calendar scope.

    API required: Yes. Needs a Google Cloud OAuth app with the Calendar API turned on.

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Sonnet 5.5

Fast and careful with your inbox and calendar.

$2 per million input tokens, $10 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

Claude Haiku 5.5

Cheapest Claude option for daily sorting.

From $0.10 per million input tokens and from $0.50 per million output tokens.

Anthropic docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

in your own words, primary and secondary

things never to suggest

2Your prompt

4 of 4 still empty
Fill these in before you run it: [CITY] [INTERESTS: in your own words, primary and secondary] [STANDING EXCLUSIONS: things never to suggest] [RUN DAY] You are the Weekly city events digest for your interests agent. Once a week it scans the event sites people actually use in your city, drops anything you are already registered for, and ranks the rest against interests you wrote in your own words. You get a short issue with a reason for each pick and a link to RSVP yourself. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Reads the event platforms set up for your city, plus any club or coworking space you belong to - Pulls what you are already registered for from your calendar - Ranks up to 8 featured events with a specific reason tied to your interests - Flags clashes with existing calendar items and standing commitments - Lists everything else that survived deduplication, tagged by category, and says when a source failed What you must never do without a yes from a person: - Anything that writes, sends, or spends. This job only reads. Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Claude Desktop with MCP, ChatGPT agent

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Set up Web fetch. Keep it to public pages, no logged-in sessions.
  2. 2Connect Google Calendar with its own login, not yours. Grant read-only calendar scope.
  3. 3Paste the prompt where your harness takes instructions. See the note under the Copy button.
  4. 4Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  5. 5Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access30 / 30

Read only. It never writes, sends or spends.

Human approval30 / 30

Nothing to approve, it only reads.

Undo and logs20 / 20

No changes to undo. Reads can be logged.

Scope18 / 20

Runs on its own login across 2 tools. Fewer connections means a smaller blast radius.

How to raise it

Nothing major to fix. One polish tip: show a short daily log of what it read, so you can spot it reaching for anything new.

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Weekly city events digest for your interests](https://trustcase.dev/badge/weekly-city-events-digest-for-your-interests.svg)](https://trustcase.dev/use-cases/weekly-city-events-digest-for-your-interests)
HTML
<a href="https://trustcase.dev/use-cases/weekly-city-events-digest-for-your-interests"><img src="https://trustcase.dev/badge/weekly-city-events-digest-for-your-interests.svg" alt="Trustcase trust score for Weekly city events digest for your interests" height="20"></a>

Other workflows that use the same tools