Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Techla FB Repost

v1.0.0

Skill để lấy nội dung từ link bài viết Facebook, viết lại bài theo phong cách phù hợp, tạo ảnh minh họa bằng Gemini, rồi đăng lên Facebook Page qua Graph API...

0· 327·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
high confidence
Purpose & Capability
The skill's actions (Apify scraping, Gemini image generation, Facebook Graph posting) are coherent with the description. However registry metadata declares no required credentials or dependencies while SKILL.md and the scripts clearly require APIFY_TOKEN, GEMINI_API_KEY, FB_PAGE_ID and FB_PAGE_ACCESS_TOKEN and expect Python. That mismatch between declared metadata and actual runtime requirements is an inconsistency you should be aware of.
Instruction Scope
The SKILL.md clearly limits actions to: call Apify to scrape, call a model (agent) to rewrite, call Gemini for images, and call Facebook Graph API to upload and post. It also includes a checklist requiring user confirmation before posting. No hidden external endpoints appear in the scripts. One scope concern: SKILL.md instructs the agent to 'activate whenever user provides a FB link + asks to repost' — if the agent is permitted to autonomously pick skills, this could cause the skill to be selected often. Also the instructions and scripts take secrets as command-line arguments (exposing them to process listings) instead of using env vars, which is a privacy/security concern.
Install Mechanism
There is no install spec (instruction-only + shipped scripts), which reduces install-surface risk. But the package includes Python scripts that import the third-party 'requests' library; the skill metadata did not declare a dependency or required binary (python3) or a way to install requests. That omission can cause runtime errors or lead users to manually install packages without guidance.
!
Credentials
The credentials requested in SKILL.md (APIFY_TOKEN, GEMINI_API_KEY, FB_PAGE_ID, FB_PAGE_ACCESS_TOKEN) are appropriate for the stated functionality. However the registry metadata lists no required env vars/primary credential — a clear mismatch. Additional concern: scripts accept credentials as CLI arguments which can be exposed via system process listings (ps). The skill also suggests storing secrets in OpenClaw secrets/env vars but does not enforce or demonstrate that; verify how you will supply tokens securely.
Persistence & Privilege
The skill does not request permanent 'always' inclusion and does not modify other skills or system-wide settings. Autonomous invocation is allowed by default on the platform, which is normal; this skill does not add unusual persistence privileges.
What to consider before installing
This skill appears to do what it says, but take these precautions before using it: - Metadata mismatch: the registry lists no required env vars or dependencies but SKILL.md and the scripts clearly need APIFY_TOKEN, GEMINI_API_KEY, FB_PAGE_ID and FB_PAGE_ACCESS_TOKEN and a Python runtime with the 'requests' package. Expect to provide those secrets and to have python3 + requests available. - Secret handling: the scripts accept API keys and tokens as command-line arguments. On multi-user systems, command-line arguments can be visible to other users (via ps). Prefer providing tokens via a secure secrets store or environment variables and avoid pasting long-lived page tokens into ephemeral chat entries. - Confirm-before-post: SKILL.md includes a checklist that requires explicit user confirmation before posting. Before enabling the skill for autonomous use, verify the agent actually shows the preview and waits for your confirmation as promised. Don't enable full autonomy unless you trust the skill and have tested it. - Token scope & rotation: Facebook Page tokens can be powerful. Use the minimum-scoped token, test on a throwaway page first, and be prepared to revoke/rotate tokens if you suspect misuse. - Dependency & runtime: ensure python3 and the 'requests' package are installed in the environment the agent will run in. Consider reviewing the code yourself or running it locally to confirm behavior before granting secrets. If you need higher assurance, request the publisher to: (1) update registry metadata to list required env vars and runtime dependencies, (2) switch to reading secrets from environment variables or a secure file rather than CLI args, and (3) provide a provenance/homepage or contact so you can validate the source. If you cannot verify the source or cannot secure the tokens, do not install or run this skill with your production Page token.

Like a lobster shell, security has layers — review code before you run it.

latestvk975peyzynaeetdxvw7se3jr4h824d15

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments