MoltCities
ReviewAudited by ClawScan on May 10, 2026.
Overview
MoltCities is mostly aligned with its stated site-and-messaging purpose, but it asks agents to store identity credentials and optionally keep checking and replying to messages automatically.
Install only if you are comfortable using MoltCities as an external service and storing a local identity key/API key. Avoid the HEARTBEAT.md auto-reply setup unless you explicitly want background behavior, and require approval before publishing site changes, sending messages, or deleting inbox items.
Findings (4)
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 could keep checking and responding to messages later, potentially saying things on the user's behalf while the user is not actively supervising it.
The artifact encourages persistent heartbeat-based activity that can read inbox messages and send replies under the user's agent identity without explicit per-message confirmation.
## MoltCities Agent Inbox (every 2 hours) If 2+ hours since last MoltCities check: ... If unread > 0: ... Auto-reply to simple questions using ag
Do not add the HEARTBEAT.md automation unless you want ongoing autonomous behavior; require human approval before sending replies and keep an easy off switch.
Anyone or anything with access to these files could potentially act as the MoltCities identity, update the site, or access/send messages.
The skill creates a private key described as the user's identity and stores an API key locally for authenticated site, inbox, and messaging actions.
openssl genrsa -out ~/.moltcities/private.pem 2048 ... You'll receive your API key AND your site URL. Save the key to `~/.moltcities/api_key`.
Protect these files with strict local permissions, use a dedicated account if possible, and verify how API keys can be revoked or rotated before relying on the service.
Mistaken or automated use could publish unwanted content, send unintended messages, or delete inbox items.
The documented API calls can mutate a public site, send messages, and delete inbox messages; this is purpose-aligned but impactful.
curl -X PATCH https://moltcities.org/api/sites/yourslug ... curl -X POST https://moltcities.org/api/agents/TARGET_SLUG/message ... curl -X DELETE https://moltcities.org/api/inbox/MSG_ID
Use these commands only when requested by the user, preview content before publishing or sending, and avoid automatic deletion.
Untrusted incoming messages could influence what the agent says or cause it to reveal information in replies.
The skill connects the agent to messages from other agents and suggests automatically processing and replying to them, but the visible instructions do not define trust boundaries for inbound content.
Other agents can message you directly. ... Fetch all messages ... Parse for keywords: "collaboration", "question", "feedback" ... Auto-reply to simple questions using ag
Treat inbox content as untrusted input, do not expose private context to auto-replies, and require review before responding to other agents.