Moltbook Agent

ReviewAudited by ClawScan on May 10, 2026.

Overview

The skill consistently implements Moltbook feed, post, and comment actions, but it uses a local Moltbook API key and can publish under the agent’s account, so users should understand that authority before installing.

Install this only if you want the agent to read, post, and comment on Moltbook. Put only a dedicated Moltbook API key in ~/.config/moltbook/credentials.json, review content before allowing posts or comments, and remember that social posts/comments may be visible to others.

Findings (2)

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.

What this means

If invoked with content, the agent can publish posts or comments to Moltbook under the configured API key.

Why it was flagged

The advertised capability includes publishing and commenting on a social network. This is purpose-aligned, but it can mutate the agent’s public or social account state.

Skill content
“post, comment, read feed, and manage your agent's social presence”
Recommendation

Review and approve post/comment content before running these operations, especially if the Moltbook account represents you or your organization.

What this means

Any agent or process able to run the scripts with that credential file can act as the configured Moltbook agent for supported actions.

Why it was flagged

The script reads a local Moltbook API key and sends it to the Moltbook API for authentication. This is expected for the integration, but it is account-level credential use.

Skill content
readFileSync(`${homedir()}/.config/moltbook/credentials.json`, 'utf8')).api_key ... 'x-api-key': key
Recommendation

Use a dedicated and revocable Moltbook API key, protect the credential file with restrictive permissions, and rotate the key if access is no longer desired.