Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Social Ops
v0.0.13Role-based social media operations skill. Use this skill when executing structured social campaigns — scouting opportunities, crafting content, posting, resp...
⭐ 1· 747·12 current·12 all-time
byDoug Smith@dougbtv
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The SKILL.md and role docs require a SOCIAL_OPS_DATA_DIR and rely on the openclaw CLI and Moltbook interactions, but the registry metadata lists no required env vars or binaries. The included installer script (install-cron-jobs.sh) calls 'openclaw' and python3. These platform/CLI dependencies are coherent with a cron-based social automation tool, but the skill's declared requirements are incomplete/mismatched.
Instruction Scope
Runtime instructions and role docs instruct agents to read and write many local files under $SOCIAL_OPS_DATA_DIR, to read optional local-file references (which can point to arbitrary local files), and to write state at {baseDir}/../state/comment-state.json. The cron-job prompts also instruct the agent to 'use credentials file auth and complete verification challenge if pending' (credentials handling is referenced but not declared). Reading arbitrary local files plus using platform credentials is beyond a narrow 'posting helper' and could expose sensitive local data if misconfigured.
Install Mechanism
There is no external binary download; the skill is instruction-first with one included installer script. The script upserts cron jobs via the openclaw CLI and uses an embedded multi-line prompt as cron job messages. No network downloads or obscure URLs are used, so install risk is moderate; however the script will modify OpenClaw cron jobs (scheduler) which is a privileged action and should be audited before running.
Credentials
SKILL.md requires SOCIAL_OPS_DATA_DIR (required) but the registry metadata lists no required env vars — an inconsistency. The skill expects credentials/verification for Moltbook operations (mentions 'credentials file auth' and API calls in docs) but does not declare any credential env vars or primary credential. That gap means the skill will rely on implicit platform credentials (not surfaced to the operator) or undocumented files.
Persistence & Privilege
always:false (good). The included script will create/modify cron jobs via openclaw cron add/edit, enabling automated task scheduling for the skill — a normal capability for an automation skill but a meaningful privilege. It does not request forced permanent inclusion, but installing the cron jobs gives it repeated autonomous runs; inspect scheduled messages and sessions before enabling.
What to consider before installing
This skill appears to implement a plausible role-based social automation system, but several mismatches and missing declarations mean you should be cautious before installing:
- Inconsistency checks: SKILL.md requires SOCIAL_OPS_DATA_DIR and the scripts call 'openclaw' and python3, but the package metadata lists no required env vars or binaries. Confirm those requirements with the author or set them deliberately.
- Cron installer: The included script will upsert OpenClaw cron jobs (create or edit scheduled runs). Run it with --dry-run first to see proposed commands, and review any cron-job messages and schedules before enabling. Only run the script if you trust the repository and understand the jobs it will create.
- Local file access: The skill is designed to read/write many files under $SOCIAL_OPS_DATA_DIR and may optionally read arbitrary local files listed in Local-File-References.md. Ensure your SOCIAL_OPS_DATA_DIR does not contain secrets, credentials, or sensitive data. Restrict Local-File-References to safe files only.
- Credentials & Moltbook access: The role docs and cron prompts reference Moltbook API usage and 'credentials file auth' but no credential env vars are declared. Clarify how Moltbook credentials are provided and stored. Prefer storing credentials in the platform's secret store rather than in repository files.
- Test in a safe environment: Before enabling in production, create a dedicated data directory containing only non-sensitive test content, run the installer with --dry-run, and inspect the cron commands. Monitor the first runs to confirm behavior.
- If you cannot confirm the missing declarations (required binaries, env vars, credential handling) or do not trust the unknown source/owner, avoid installing the cron jobs and audit all role files for any paths that reference secrets or non-repo directories.Like a lobster shell, security has layers — review code before you run it.
latestvk97a919q836vzde5vsanf0abw982aew8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.