Social Media Scheduler
v1.1.0Schedule and post text, images, videos, and threads across Discord, Reddit, Twitter/X, Mastodon, Bluesky, Moltbook, LinkedIn, and Telegram via OAuth or API k...
⭐ 1· 1.7k·2 current·3 all-time
byShilatdoesai@mrshorrid
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name and code (multiple platform adapters, scheduling, media uploads) match the stated purpose of a social-media scheduler. However the registry metadata claims no required binaries, env vars, or config paths, while README/SKILL.md/CHANGELOG state Node.js 18+ is required and the scripts require platform credentials (Twitter, Reddit, Mastodon, Bluesky, Moltbook, LinkedIn, Telegram, Discord webhooks). The declared requirements in the registry are therefore inconsistent with what the skill actually needs.
Instruction Scope
SKILL.md instructs the agent/user to run npm install and to run node scripts (post.js, schedule.js, daemon, dashboard), to create config JSONs and .env files with API keys, and to use local credential files (examples reference .credentials/moltbook.json and storage/queue.json). Those runtime instructions will cause network calls to many external APIs and will read/write local workspace files. The instructions do not attempt to read unrelated system secrets, but they do instruct creation/usage of credential files and starting a persistent daemon that will post on accounts — this allows automated posting if credentials are supplied and therefore requires user caution. Additionally, some internal docs claim working credentials are saved in `.credentials/moltbook.json`, which contradicts the stated guidance that credentials should not be committed.
Install Mechanism
There is no formal install spec in registry metadata, but SKILL.md instructs running `npm install` and the code includes package.json/package-lock.json. npm install will fetch third-party packages from registries (moderate risk). No downloaded archives from unknown URLs are present in the provided metadata. You should inspect package.json and package-lock.json to see which dependencies will be installed.
Credentials
The registry says 'Required env vars: none' and 'Required config paths: none', but SKILL.md and various scripts require many credentials (OAuth keys, access tokens, API keys, Discord webhook URLs, etc.). That mismatch is a red flag: the skill will need sensitive secrets to operate but does not declare them in metadata. Also multiple references in docs to existing credential files (e.g., `.credentials/moltbook.json`) are suspicious and should be validated to ensure no secrets are baked into the codebase.
Persistence & Privilege
always:false (normal). The skill runs a scheduler daemon and a web dashboard (http://localhost:3737) when invoked — that gives it persistent network activity while running but it does not request forced always-on inclusion. Autonomous agent invocation is allowed by default; combined with platform credentials this means the skill could post automatically if the agent invokes it — users should ensure credentials and invocation policies are set deliberately.
What to consider before installing
Do not install or run this skill until you perform a few checks:
1) Inspect package.json and package-lock.json to see what npm packages will be installed (and run `npm audit`).
2) Search the repository for any committed secrets or files like `.credentials/*`, `.env`, or actual API tokens. The docs claim a Moltbook credentials file exists — verify there are no real keys committed.
3) Confirm you have Node.js 18+ locally (SKILL.md/CHANGELOG claim this), because the registry metadata incorrectly stated 'no required binaries'.
4) Understand that to post you must supply OAuth/API credentials; do not paste those into repository files. Keep them in a local .env or credential store and avoid committing them.
5) Review scripts (especially scripts/schedule.js, scripts/post.js, and platform adapters) for unexpected behavior (file reads outside the skill folder, remote URLs, or calls that upload data to endpoints you don't expect).
6) If you plan to let an agent call this skill autonomously, limit its permissions and consider disabling autonomous invocation of this skill or running it in an isolated environment to prevent unintended posting or credential exposure.
If you want, provide package.json and the contents of any `.credentials`/`.env.example` files and I can highlight exact places to review or lines that look like secrets or dangerous behavior.Like a lobster shell, security has layers — review code before you run it.
latestvk972nr6rreewn8r81pgghrg70d80k6k0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.