Moltbook Fanboy

The SKILL.md claims the skill will 'automatically ... generate comments and likes' on Moltbook and 'send directly to Telegram' and sync bidirectionally via GitHub. The code, however, only fetches posts (public API) and locally records simulated like/comment actions in data/actions.json and writes reports to an Obsidian path. There are no POST calls to Moltbook to actually perform likes/comments, and there is no Telegram integration implemented. Also the skill performs a git push to /root/clawd/obsidian-vault without declaring any GitHub credentials — these capabilities/requirements are inconsistent with the stated "no configuration needed" claim.

SKILL.md instructs the agent to run scripts that will fetch posts, generate interactions, save reports, push to GitHub, and send reports to Telegram. The actual scripts fetch public data and generate local actions and reports, then unconditionally attempt to git add/commit/push from /root/clawd/obsidian-vault. The SKILL.md also instructs to "send directly to Telegram" but no code or declared env var supports that. The skill also writes outside its own directory (into /root/clawd/obsidian-vault) and will attempt network pushes — instructions therefore reference external endpoints and filesystem locations that are not declared or authorized in metadata.

There is no install spec (low install risk). However the Python scripts use third-party modules (requests) and rely on system git being configured; these dependencies are not declared in the registry metadata. No remote download URLs or extract steps are used, which is good, but missing dependency declarations mean the runtime environment assumptions are not explicit.

The registry declares no required environment variables or credentials, yet the scripts attempt to push to GitHub (via git) and write into /root/clawd/obsidian-vault. Successful push depends on existing git credentials (SSH key or stored credentials) which are effectively used, despite not being declared. The skill also assumes access to a specific Obsidian vault path which could contain private files. This is disproportionate to a 'read public Moltbook and summarize' description and risks exposing local/remote content via git pushes.

The skill does not set always:true, but it writes files outside its own directory (obsidian-vault reports) and attempts to commit and push changes to a remote repository. That means it will alter user data and attempt remote writes without explicit configuration fields or prompts. While not requesting elevated platform privileges, this behavior is significant because it may cause automatic commits/pushes of generated content or unintentionally included files (potential secrets) to a remote GitHub repo.