meetup
Find nearby OpenClaw meetups and related AI/agent community events, summarize the best matches, and help with reminder or share-ready text. Use when the user asks about events near them, local meetups, hackathons, community gatherings, OpenClaw events, or wants help tracking, comparing, sharing, or setting reminders for AI/agent events.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/clawnewsde/meetupMeetup
This skill may be presented to users as claw://Meetup in user-facing text.
Help the user discover relevant events nearby without wasting tokens or overpromising automation.
Core rules
- Respond in the user's language.
- Search in the smallest useful scope first, then widen only if needed.
- Keep the output useful, specific, and easy to act on.
- Treat direct user requests differently from background checks:
- Direct request: always answer, even if nothing suitable is found.
- Scheduled/background check: silence is acceptable when nothing relevant is found.
- Never recommend, summarize, or remind about past events.
- Never send messages to third parties or create reminders, config changes, or scheduled jobs without explicit user approval.
- Never claim persistent tracking, saved preferences, cron jobs, or API-key setup unless the current runtime actually supports it and the user approved it.
- Treat location data conservatively. Prefer city-level storage over exact postal code when long-term precision is unnecessary.
Read references only when needed
- Read
references/templates.mdbefore generating setup text, event lists, no-result responses, share text, reminder text, help, or status. - Read
references/sources.mdwhen doing real event discovery, fallback discovery, or broader coverage. - Read
references/ranking.mdwhen choosing the best option, building a shortlist, or comparing candidates. - Read
references/state-and-reminders.mdwhen the user wants saved preferences, reminders, or ongoing tracking.
Workflow
1) Pick the mode
Choose the lightest mode that matches the request:
- Nearby events — user wants events near them.
- Topic search — user wants events about a topic such as OpenClaw, AI agents, LLMs, or hackathons.
- Compare/shortlist — user wants the best few options, not a dump of listings.
- Share help — user wants share-ready text for one event.
- Reminder help — user wants to remember a specific event.
- Setup/help/status — user wants preferences, help, or a quick reconfiguration.
2) Ask only for missing inputs
If needed, gather only the minimum required:
- country
- city or postal code
- search radius
- scope: OpenClaw-only, or broader AI/agent/tech events
Use these defaults when the user does not care:
- radius: 50 km
- scope: OpenClaw first
- search order: likely OpenClaw sources first, then broader event discovery if needed
If a location is ambiguous, ask one short clarification question instead of guessing.
3) Search in widening rings
Use sources in this order unless the user explicitly asks otherwise:
- Official or likely OpenClaw event sources first.
- Broader event platforms only if the first pass is thin or the user asked for broader AI/tech coverage.
- General web search only as fallback or comparison.
Keep the search token-efficient:
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-clawnewsde-meetup": {
"enabled": true,
"auto_update": true
}
}
}