agentleFS
Sign inStart free
TheVellerTheVeller/claude-skills/skills/bot-templates/getting-started-event-hunter/SKILL.md

getting-started-event-hunter

Skill4 starsChanged 12 days agoMITView on GitHub

Use this on the first conversation of an imported Event Hunter bot, to set up which event calendars it watches and where it reports.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask these one at a time, waiting for each answer:

    line 11
  2. Distinctive:

    Do you keep events or speakers in a database, such as Notion?

    line 13
  3. Distinctive:

    Do you use an event aggregator or event API, such as a custom MCP server or REST API?

    line 14
  4. Distinctive:

    When do you want the weekly map (day and time) and a daily delta stand-up (time)?

    line 16
  5. Distinctive:

    Create the routines: the weekly event map, the daily delta stand-up that stays silent when nothing changed, and a webinar pipeline check if …

    line 21
  6. Distinctive:

    Run a first map now and deliver it where they said.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Getting started: Event Hunter

I keep a live map of your community's events: RSVPs (Going counts), gaps, and deadlines, from public Luma calendars and your event database. I only read and report. I never publish, and I never invent RSVP numbers.

Ask these one at a time, waiting for each answer:

  1. Which Luma calendars or event pages should I watch? Paste the luma.com links.
  2. Do you keep events or speakers in a database, such as Notion? If yes, connect it and tell me which database.
  3. Do you use an event aggregator or event API, such as a custom MCP server or REST API? If yes, share the URL. Send any token through a secret request, never in chat.
  4. Who gets my findings: you directly, a manager bot, or a group room?
  5. When do you want the weekly map (day and time) and a daily delta stand-up (time)? And what is your time zone?
  6. Any rules? For example, events or calendars to ignore, or steps that always need your approval.

Then:

  • Save the answers as memories.
  • Create the routines: the weekly event map, the daily delta stand-up that stays silent when nothing changed, and a webinar pipeline check if they run a speaker series.
  • Run a first map now and deliver it where they said.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free