Back to skill
Skillv1.0.0
ClawScan security
Facebook Management Skills by MCBAI · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
SuspiciousApr 7, 2026, 5:42 AM
- Verdict
- suspicious
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill's code and docs match the stated Facebook Page management purpose, but the package metadata omits the environment variables/credential usage the script relies on (FB_ACCESS_TOKEN / FB_PAGE_ID), which is an important inconsistency you should understand before installing.
- Guidance
- The code appears to do exactly what the description promises and only contacts Facebook's Graph API. However: (1) The package metadata does not declare the environment variables the script can read (FB_ACCESS_TOKEN, FB_PAGE_ID) — treat this as a packaging oversight and assume the skill needs a Page Access Token. (2) Page tokens with the listed scopes can post, delete, and moderate; if leaked they allow full control of the Page. Do not store a long-lived Page token on shared machines or in repositories; follow the README advice to add fb_config.json to .gitignore, and prefer using a secure secret store or environment variables with limited exposure. (3) Review the token scopes you grant (only the permissions needed) and consider creating a dedicated Facebook App and Page token for automated use, revoking it after testing. (4) If you need stronger assurance, ask the publisher to update the registry metadata to list FB_ACCESS_TOKEN and FB_PAGE_ID as required env vars (or clearly state the config file usage) and to provide a trusted homepage or source repo. If you proceed, run the script in an isolated environment and be ready to revoke the token quickly if anything unexpected occurs.
Review Dimensions
- Purpose & Capability
- okName, description, README, references, SKILL.md and the Python script all consistently implement Facebook Page management via the Graph API (posts, photos, carousel, video/Reels, story, scheduling, comments). The network endpoints are only graph.facebook.com and align with the stated functionality.
- Instruction Scope
- concernSKILL.md instructs creating a local config file (scripts/fb_config.json) containing the Page access token and page_id and also documents using Graph API Explorer to obtain tokens. The runtime script additionally falls back to environment variables FB_ACCESS_TOKEN and FB_PAGE_ID when the config file is absent — but the skill metadata declared no required env vars. The code only accesses local media files for uploads and the Facebook Graph API, which is expected, but the un-declared env usage is a scope/metadata mismatch.
- Install Mechanism
- okThis is an instruction-only skill with a bundled Python script. There is no install spec that downloads code from third-party URLs. Dependencies are minimal (requests via pip). No risky external installers or archive extraction are present.
- Credentials
- concernThe skill metadata reports no required credentials, but the script requires a Page Access Token and Page ID (via scripts/fb_config.json or the environment variables FB_ACCESS_TOKEN and FB_PAGE_ID). Those credentials are powerful (posting/moderation access to a Page); the omission in metadata is a mismatch and should be corrected. The skill's guidance discusses token scopes and warns to .gitignore the config file, which is appropriate, but the inherent risk of long-lived Page tokens (they may be 'never expires') means leaking the token would allow full page posting/managing.
- Persistence & Privilege
- okalways is false and the skill does not request permanent platform-level privileges. The skill stores/reads its own local config file (fb_config.json) and/or environment variables; it does not modify other skills or system-wide settings.