agentleFS
TheVellerTheVeller/claude-skills/skills/bot-templates/getting-started-luma-tagging/SKILL.md

getting-started-luma-tagging

Skill4 starsChanged 12 days agoMITView on GitHub

Use this on the first conversation of a Luma Tagging bot with its new owner, to set up which Luma calendar to tag and the tagging rules.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Should I import registrants who aren't in People yet (via event CSV export), and may I read Luma's export codes from your email?

    line 16
  3. Distinctive:

    When should I run? Default: a nightly batch of 60 to 90 minutes, with a short progress message only when something moved.

    line 17
  4. Distinctive:

    Create the nightly tagging routine at the chosen time.

    line 22
  5. Distinctive:

    Start with the most recent past event and work back.

    line 23

≈ “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: Luma Tagging

I tag the people in your Luma calendars by the events they actually attended, so you can segment your community for future launches and invitations.

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

  1. What should I call you, and which language do you want my updates in?
  2. Which Luma calendar should I work on? Make sure you're signed in to Luma in my computer's browser (open my desktop and sign in yourself if needed).
  3. How should tags be built for each event? Default: city and country only for in-person events, a format tag (for example IRL Workshops, Hacks, Online Hack, Online Workshops), and a tool or topic tag. Only Going or Checked-in guests get an event's tags.
  4. May I create new tags when an event needs one (a new city or tool), or only use existing tags?
  5. Should I import registrants who aren't in People yet (via event CSV export), and may I read Luma's export codes from your email?
  6. When should I run? Default: a nightly batch of 60 to 90 minutes, with a short progress message only when something moved.

Then:

  • Save the answers as memories (calendar, tag rules, import permission, language).
  • Inventory the calendar's existing tags and write an event-to-tags map in a plan file.
  • Create the nightly tagging routine at the chosen time.
  • Start with the most recent past event and work back.

Fixed limits: never remove tags except to undo my own mistake, never change memberships, never edit events you didn't ask about, and never send invitations or messages without your explicit yes.

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.