Luma Events
v1.0.0Fetch upcoming events from Luma (lu.ma) for any city. Use when the user asks about tech events, startup meetups, networking events, conferences, or things happening in cities like Bangalore, Mumbai, Delhi, San Francisco, New York, etc.
⭐ 1· 1.9k·1 current·1 all-time
byNeil Agarwal@regalstreak
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description (fetch Luma events) align with the included Python script: it fetches lu.ma/<city>, extracts __NEXT_DATA__ JSON, filters and formats events. Declared dependencies (stdlib only) and package.json metadata are consistent with the stated purpose. Note: SKILL.md describes event persistence to a Clawd memory file as a feature, but the provided script does not implement writing or merging to ~/clawd/memory/luma-events.json — an implementation mismatch.
Instruction Scope
SKILL.md explicitly instructs the agent to 'Always save fetched events to ~/clawd/memory/luma-events.json' and to merge/retain 60 days of events. The runtime Python script performs network fetches and prints or emits JSON, but it contains no file-write or merge logic. This creates unclear runtime responsibility (will the agent itself write to disk?) and grants the skill the ability to persist user browsing/activity data if the agent follows SKILL.md. Persisting user activity is privacy-sensitive and should be explicit and consented to.
Install Mechanism
No install spec or downloads — this is instruction + script only and uses Python stdlib. No external packages or remote installers are pulled, which reduces install risk.
Credentials
The skill requests no environment variables or credentials and only contacts the public lu.ma domain, which is proportionate for event scraping. The only unusual permission is implicit filesystem persistence (writing to ~/clawd/memory), which is not declared as an environment/config requirement but is requested in documentation; that should be made explicit to the user.
Persistence & Privilege
The skill does not set always:true and does not request elevated system privileges. However, SKILL.md asks for always-saving fetched events to a user-local memory path, which grants persistent storage of the user's event queries and interests. Because the saved-file behavior is not implemented in the script, it's unclear whether persistence would occur automatically; this ambiguity increases the risk surface (privacy/long-term data retention).
What to consider before installing
The skill appears to do what it advertises (scrapes lu.ma public pages) and uses only Python stdlib, which is reasonable. However: (1) SKILL.md instructs the agent to always save fetched events to ~/clawd/memory/luma-events.json and to merge/retain them for 60 days, but the included script does not write or merge that file — ask the publisher which component (agent vs script) is responsible for persistence before installing. (2) If you allow automatic saving, be aware this will record the cities/events you query (privacy concern). Require explicit consent and review/controls for that memory file. (3) If you prefer, run the script manually in a sandbox first to confirm output, or modify the script to implement safe, explicit persistence (prompt before write, use a configurable path, or disable auto-save). (4) The network access is only to lu.ma; ensure you are comfortable with public web scraping and respect rate limits. If you need the skill to be non-persistent, remove or disable the 'save to ~/clawd/memory' instruction before granting the skill write permission.Like a lobster shell, security has layers — review code before you run it.
latestvk97534b565fzh91qm16jb0jckh804r1g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.