Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Automated Content Machine
v1.0.0自動化內容創作引擎 - 每日自動生成並發布內容：(1)Twitter/Threads threads (2)Blog posts (3)YouTube script (4)Newsletter (5)自動發布到多平台。支持AI生成+人類審核
⭐ 0· 1k·4 current·4 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill claims to auto-generate and auto-publish content to services (Twitter/Threads, WordPress/Ghost, Buffer/Hypefury, Substack/Ghost, Gumroad, etc.). However, the metadata declares no required environment variables, no config paths, and no install steps. For a skill that posts to external platforms you would normally expect declared API keys, OAuth tokens, or at least instructions on how credentials are provided. The absence of any declared credential requirements is inconsistent with the stated purpose.
Instruction Scope
SKILL.md is high-level and open-ended: it lists content types, target platforms, monetization, and third-party tools but provides no concrete runtime steps, API endpoints, or safeguards. The instructions could implicitly authorize an agent to attempt automated posting if credentials are available, and they are vague enough to grant broad discretion to the agent (e.g., what to post, when, and which account to use). That lack of specificity is a risk because it leaves handling of secrets, account selection, and publishing policies undefined.
Install Mechanism
There is no install spec and no code files — this is an instruction-only skill. That reduces the immediate risk of arbitrary code being installed on disk.
Credentials
The skill references many third-party services that normally require credentials (Twitter/Threads, WordPress, Ghost, Buffer/Hypefury, Substack, Gumroad), but requires.env and primary credential are both empty. Either the skill expects the agent or user to provide credentials at runtime without declaration, or it cannot actually perform auto-publishing. This mismatch is disproportionate and unexplained. Also there is no guidance about scopes/least-privilege for any tokens.
Persistence & Privilege
Flags show the skill is not force-installed (always=false) and allows user invocation/autonomous invocation (platform defaults). There is no indication the skill modifies other skills or system-wide settings. No persistence or elevated privileges are requested in the manifest.
What to consider before installing
This skill is a high-level plan for an automated multi-platform publishing system but lacks crucial implementation details. Before installing or enabling it: 1) Ask the author how publishing is performed — which APIs/endpoints, and where/how credentials are provided and stored. 2) Never provide full account passwords; prefer per-service API tokens with minimal write scopes and test tokens on sandbox accounts. 3) Request documentation on what the agent will post automatically and any moderation/human-review checkpoints. 4) If you plan to use it, start by granting access to a test account only, and audit published content. 5) Because the skill is instruction-only (no code), it cannot itself write files, but its vagueness could let an autonomous agent attempt to use any credentials available in the environment — ensure no sensitive tokens are present in your runtime environment. If you need stronger assurance, ask for a version that declares required env vars, details credential handling, and provides explicit publish/confirmation steps.Like a lobster shell, security has layers — review code before you run it.
latestvk978hyqr7hnjgjqf6fk46s29qx81f6ab
License
MIT-0
Free to use, modify, and redistribute. No attribution required.