fboc
WarnAudited by ClawScan on May 10, 2026.
Overview
This appears to be a Facebook Page management tool, but it has risky install-time PowerShell execution and can post, hide, or delete Page content using your token.
Review the package before installing, especially the npm postinstall PowerShell behavior and missing helper files. If you proceed, use a dedicated least-privilege Facebook Page token, avoid granting broad Page access, require manual approval for posting/deleting actions, and monitor any cron or scheduled jobs.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Installing the package could attempt to execute setup code on the user's machine before they explicitly run a Facebook command.
The npm package attempts to run a PowerShell script automatically during install on Windows, using ExecutionPolicy Bypass. That install-time execution is not clearly disclosed in the install spec.
"postinstall": "if (process.platform === 'win32') { powershell.exe -ExecutionPolicy Bypass -File ./bin/setup.ps1 }"Do not install until the postinstall behavior is removed or replaced with a clearly documented, user-run setup step using reviewed files.
The reviewed artifacts do not fully account for the code that would actually run, making provenance and behavior hard to verify.
The runtime maps commands to PowerShell .ps1 helpers, but those .ps1 files are not present in the provided file manifest. The package also references bin/facebook-advanced, which is not shown in the manifest.
'fb-post-list': 'fb-post-list.ps1', ... const ps = spawn(pwsh, ['-ExecutionPolicy', 'Bypass', '-File', scriptPath, ...commandArgs]
Require a complete package manifest with all referenced bin and PowerShell files included and reviewed before trusting the skill.
A mistaken or autonomous invocation could remove or hide public Facebook Page content.
This included command attempts to delete a Facebook post and then hide it as fallback, with no mandatory confirmation prompt in that implementation.
makeHttpsRequest('DELETE', `/${postId}`, null, pageAccessToken) ... makeHttpsRequest('POST', `/${postId}`, { is_published: false }, pageAccessToken)Require explicit user confirmation for delete, hide, schedule-delete, and public-post actions, and avoid allowlisting destructive commands without review.
Anyone or any agent with this token could act on the connected Facebook Page within the token's permissions.
The skill requires a privileged Facebook Page token that can manage Page content. This is purpose-aligned but sensitive.
`FB_PAGE_ACCESS_TOKEN`: Required... `pages_manage_posts`: Create, edit, hide, delete posts
Use a dedicated least-privilege Page token, store it securely, rotate it if exposed, and do not grant access to Pages you do not want the agent to manage.
Scheduled jobs may continue running and using the Facebook token until removed.
The documentation shows how to create persistent OpenClaw cron jobs. This is disclosed, but it means the skill can keep operating on a schedule after setup.
openclaw cron add --name "Morning Briefing" --cron "0 9 * * *" ... --message "facebook-advanced fb-post-list 123456789 --limit 10"
Create cron jobs only for tasks you truly want repeated, prefer isolated sessions, and periodically review or delete scheduled jobs.