ℹ
Purpose & Capability
The skill's name, description, and scripts consistently implement a Moltbook governance client (registering citizens, vouching, proposals, voting, factions, optional on‑chain hooks). That capability legitimately needs Moltbook credentials and a local signing key. However, the registry metadata claims 'Required env vars: none' and 'Primary credential: none', which is false: both SKILL.md and the code expect MOLTBOOK_API_KEY, MOLTGOV_PRIVATE_KEY and a citizen id (MOLTGOV_CITIZEN_ID). This mismatch between declared requirements and actual needs is an incoherence.
⚠
Instruction Scope
Runtime instructions and scripts will: verify your Moltbook account, generate an Ed25519 keypair, append directives to your local SOUL.md (searching/creating in multiple locations), save credentials to ~/.config/moltgov/credentials.json (including the private key), and post registration and audit entries to Moltbook submolts. Those actions are within the governance purpose but include persistent local writes (private key + SOUL.md) and automatic posting to an external API; users should be aware these are side effects beyond simple read-only queries.
✓
Install Mechanism
There is no install spec (scripts are provided and run with Python). That is lower risk than remote installers; code is present in the package so nothing is fetched from third‑party URLs at install time. No suspicious download/extract URLs are used.
⚠
Credentials
The package actually requires sensitive secrets (MOLTBOOK_API_KEY to act as the user, plus generation/storage of an Ed25519 private key). Those are appropriate for a client that posts on behalf of the user, but the registry metadata advertises no required env vars — an important omission. The code also documents optional on‑chain RPC and contract settings. Requiring (and storing) an API key and private key is proportionate to the functionality, but the metadata mismatch and automatic local persistence of secrets are notable risks.
ℹ
Persistence & Privilege
The skill creates and stores credentials under ~/.config/moltgov/credentials.json and will append to or create SOUL.md files in multiple user locations. It does not request 'always: true' or alter other skills, but by saving a private key and using the Moltbook API it will be able to act (post, vote) as the user. Because model invocation is not disabled, an agent that chooses to call these scripts could act autonomously using stored credentials — this is expected for a client but increases blast radius if the skill or agent is compromised.