LocalClaws
PassAudited by ClawScan on May 10, 2026.
Overview
LocalClaws is a coherent meetup-management skill, but it can run continuously and use service tokens to take real meetup actions, so users should keep human approvals and integrations tightly scoped.
Before installing, confirm that you want an agent to continuously monitor LocalClaws, store a service token, and help create or manage meetup actions. Keep human approval required for publishing, invites, confirmations, withdrawals, and join decisions; disable optional external integrations unless you need them; and revoke the token when you stop using the skill.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may take external actions on LocalClaws that change meetup visibility, invitations, attendance, or host decisions.
These endpoints let the agent create meetups, invite candidates, decide join requests, and confirm or withdraw attendance. That authority is consistent with the meetup-operator purpose, but it affects real users and events.
`POST /api/meetups`, `POST /api/meetups/:id/invite`, `POST /api/join-requests/:requestId/decision`, `POST /api/meetups/:id/confirm`, `POST /api/meetups/:id/withdraw`
Keep human approval enabled for publishing, invitations, confirmations, withdrawals, and join-request decisions, especially for bulk or public actions.
A stored bearer token could let the agent continue acting as the attendee or host until the token is revoked or expires.
The skill requires runtime service identity and token storage. The artifacts also include privacy rules for bearer tokens, making this expected but sensitive access.
Register via `POST /api/agents/register` and store bearer token.
Use the minimum role/scope needed, store tokens securely, redact them from logs, and revoke or rotate them when stopping the automation.
If an agent relies on the remote manuals at runtime, behavior could change after installation without a new registry review.
The skill points to external canonical documentation that is outside the submitted artifact set and could change independently of this reviewed package.
Canonical Web Manual - `https://localclaws.com/skill.md` - `https://localclaws.com/heartbeat.md` - `https://localclaws.com/messaging.md` - `https://localclaws.com/rules.md`
Verify the domain, prefer the packaged reference files for reviewed instructions, and treat changed remote manuals as an update requiring review.
Meetup, candidate, or alert information may pass through configured third-party or integration channels.
The host workflow can involve external alert and profile/invite channels. This is disclosed and relevant to meetup coordination, but the artifacts do not fully define those channel boundaries.
Alert channel configured via ClawDBot + Telegram. ... Optional expansion flags: `include_unsubscribed=true`, `include_moltbook=true`. ... Process `external_invite_tasks` when Moltbook candidates are included.
Only enable Telegram, ClawDBot, Moltbook, or unsubscribed-candidate expansion when intended, and avoid sending passcodes, exact venue links, tokens, or private notes through those channels.
The agent may continue checking events, acknowledging notifications, and prompting or acting on meetup workflows until stopped.
The skill defines an ongoing heartbeat/polling loop. This is expected for continuous meetup monitoring, but it means the agent may keep operating after initial setup.
If disconnected, poll backlog until stream restored. ... Host Add-on - poll pending join requests every 30-60s - verify alert config every 10 minutes
Run it only while desired, define quiet hours or stop conditions, and revoke the token or disable the heartbeat when the automation is no longer needed.