Conference Intern
v2.1.4Discover, curate, and register for crypto conference side events via Luma and Google Sheets
⭐ 0· 166·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Luma + Google Sheets discovery, LLM curation, browser RSVP automation) match the files and scripts. Required binaries (jq, python3, curl, sha256sum) are appropriate for JSON handling, CSV parsing, URL checks and ID generation. The scripts call the OpenClaw browser/agent CLI (expected for browser automation). No unrelated cloud credentials, extraneous binaries, or surprising install steps are requested.
Instruction Scope
SKILL.md and templates instruct the agent to run the provided bash scripts and to use the browser capability to extract pages and fill forms; that is consistent with the purpose. Two notes: (1) the runtime flow asks the agent to run batches repeatedly (register.sh is expected to be re-run until 'done'); this grants the skill automated multi-step behavior — intentional but worth knowing. (2) The agent is asked to read and write specific workspace files (e.g., config.json, registration-status.json, custom-answers.json, luma-session.json) — these are necessary for state tracking but mean personal info (name/email/custom answers) and session cookies are persisted locally.
Install Mechanism
No install spec (instruction-only + bundled scripts) — lowest risk. Nothing is downloaded from remote URLs or extracted. Scripts run locally and rely on existing CLI tools and the OpenClaw agent/browser.
Credentials
The skill reads ~/.openclaw/openclaw.json to detect the workspace and writes workspace files (config, events, curated.md, custom answers, session cookies). This is proportionate to its stated need to persist state and optional Luma session cookies, but means it will store personal registration answers and optionally Luma auth cookies locally. There are no required external API keys or unrelated credentials in the manifest.
Persistence & Privilege
always:false and the skill does not request system-wide config changes. It persists only its own workspace files and session cookies under the OpenClaw workspace. The scripts expect to re-run batches and to call the agent repeatedly, which is normal for this automation; that behavior is not flagged as a platform-level 'always' privilege.
Assessment
This skill appears to do what it claims, but before installing consider the following: (1) it will store per‑conference data in your OpenClaw workspace (~/.openclaw/workspace/conferences/<id>/), including optional Luma session cookies and any answers you provide to custom RSVP fields — delete those files if you don’t want persistence. (2) The skill invokes your configured LLM/agent for curation and for reading Google Sheets; any event data sent to the model provider goes through whatever model service you have configured (OpenAI or other). (3) The registration flow is batched and the scripts expect the agent to run successive batches until completion — if you want to approve each batch manually, run the scripts yourself rather than relying on full automation. (4) Review the registration helper (cli_register_event) and any code that interacts with web pages to confirm it only performs expected clicks/field fills and does not call external endpoints you don’t recognize. (5) If you prefer not to persist login state, avoid logging into Luma in the agent/browser so luma-session.json is not created. If you want extra assurance, run the scripts on a test conference and inspect created files before using real personal data.Like a lobster shell, security has layers — review code before you run it.
latestvk97fzbaj42sxzm9s04wea484k183qy2b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎪 Clawdis
Binsjq, python3, curl, sha256sum