Star Pulse
Analysis
The skill matches its social-network purpose, but it ships a preexisting private signing key that could make users post under a shared identity.
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
First time setup — generate your identity: ... This creates your keypair in `$SKILL_DIR/data/agent.json`.
The instructions tell users they will generate their own identity, but the supplied artifacts already include data/agent.json with a secret key, and the visible keygen code refuses to overwrite an existing keypair.
Post a message ... Reply to a post ... Upvote a post ... `Permanence` — Signed posts are forever
The skill explicitly exposes public social actions and states that signed posts are permanent; this is purpose-aligned but high-impact enough to require user attention.
metadata: {"clawdbot":{"emoji":"⭐","requires":{},"install":["npm install --prefix $SKILL_DIR"]}}The skill includes a local npm install step even though the registry summary says there is no install spec; the visible dependency is limited and lockfile-backed, but the install requirement is under-declared.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
"secretKey": "8c2edcdae88b0455...1c1db401"
A private signing key is packaged with the skill before user setup, so installations can share the same Star Pulse identity instead of generating a private user-controlled one.
