Token导航 LogoToken导航TokenDH.com
开发敏感数据clawhub未标认证来源可访问clear审计提醒

facebook-page脸书页面

Agent Skill

facebook-page 用于辅助前端页面、组件、样式和交互逻辑开发,适合在 OpenClaw 中需要维护前端项目、生成组件或检查界面实现时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

21,638

周安装

920

GitHub Stars

2

下载量

7,581
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:facebook-page(脸书页面)
来源仓库:https://github.com/seph1709/facebook-page
安装命令:
openclaw skills install facebook-page
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install facebook-page

简介

用于辅助前端页面和组件开发。facebook-page 属于开发类 Skill,可作为该场景下的辅助能力补充。

  • 适合维护 Facebook 页面交互逻辑。
  • 使用时需配置 PowerShell 环境和凭证文件。
  • 涉及敏感操作时应确认最小权限原则。适用宿主包括 OpenClaw,接入前应确认版本、权限和运行环境要求。
  • 安装前建议检查维护状态和是否会触发本地命令执行。

SKILL.md

name
facebook-page
description
Facebook Page manager: post, schedule, reply, get insights & more. Requires: powershell/pwsh. Reads ~/.config/fb-page/credentials.json (FB_PAGE_TOKEN, FB_PAGE_ID). FB_APP_SECRET for one-time setup only — delete afterward. Long-lived token; rotate periodically and immediately if host is compromised. Grant minimal permissions only. No data forwarded to third parties; all calls go to graph.facebook.com only.
metadata
{"openclaw":{"emoji":"[fb]","requires":{"anyBins":["powershell","pwsh"]}}}

facebook-page — Universal Meta Graph API Skill

Constructs and executes Meta Graph API calls inline based on what the user wants. No scripts needed.

API version: v25.0 Base URL: https://graph.facebook.com/v25.0


STEP 1 — Load Credentials

Credentials are stored in ~/.config/fb-page/credentials.json.

$cfg    = Get-Content "$HOME/.config/fb-page/credentials.json" -Raw | ConvertFrom-Json
$token  = $cfg.FB_PAGE_TOKEN
$pageId = $cfg.FB_PAGE_ID

If the file doesn't exist, guide setup. Required fields:

FieldPurpose
FB_PAGE_TOKENNever-expiring Page access token — used for all API calls
FB_PAGE_IDNumeric Facebook Page ID
FB_APP_IDMeta App ID — only needed during token exchange
FB_APP_SECRETMeta App Secret — only needed during token exchange

One-time token exchange setup:

# Provide: $appId, $appSecret, $shortToken (from Graph API Explorer), $pageId
# 1. Exchange for long-lived user token
$r1 = Invoke-RestMethod "https://graph.facebook.com/oauth/access_token?grant_type=fb_exchange_token&client_id=$appId&client_secret=$appSecret&fb_exchange_token=$shortToken"
# 2. Get never-expiring Page token
$r2 = Invoke-RestMethod "https://graph.facebook.com/v25.0/$pageId?fields=access_token&access_token=$($r1.access_token)"
$pageToken = $r2.access_token
# 3. Save — only these four fields, nothing else
@{
    FB_PAGE_ID    = $pageId
    FB_PAGE_TOKEN = $pageToken
    FB_APP_ID     = $appId
    FB_APP_SECRET = $appSecret
} | ConvertTo-Json | Set-Content "$HOME/.config/fb-page/credentials.json" -Encoding UTF8

Restrict file permissions immediately after saving:

# Windows
icacls "$HOME/.config/fb-page/credentials.json" /inheritance:r /grant:r "$($env:USERNAME):(R,W)"
# macOS / Linux
# chmod 600 ~/.config/fb-page/credentials.json
⚠️ Never commit this file to version control. It contains long-lived secrets. This skill makes no external calls other than to graph.facebook.com. No data is forwarded to third parties.

STEP 2 — Figure Out the API Call

Common Endpoints

What user wantsMethodEndpoint
Post textPOST/$pageId/feed — body: message
Post with imagePOST/$pageId/photos — multipart: source + message
Post with videoPOST/$pageId/videos — multipart: source + description
Post with linkPOST/$pageId/feed — body: message + link
Delete a postDELETE/{post-id}
Schedule a postPOST/$pageId/feed — body: message + published=false + scheduled_publish_time (unix timestamp)
Get recent postsGET/$pageId/published_posts?fields=id,message,created_time&limit=10
Get page infoGET/$pageId?fields=name,fan_count,followers_count,about
Like a postPOST/{post-id}/likes
Get commentsGET/{post-id}/comments?fields=message,from,created_time
Reply to commentPOST/{comment-id}/comments — body: message
Hide commentPOST/{comment-id} — body: is_hidden=true
Delete commentDELETE/{comment-id}
Get page insightsGET/$pageId/insights?metric=page_fans,page_impressions&period=day
Get post insightsGET/{post-id}/insights?metric=post_impressions,post_reactions_by_type_total
List eventsGET/$pageId/events?fields=name,start_time,description
Create eventPOST/$pageId/events — body: name, start_time, description
List albumsGET/$pageId/albums?fields=name,count
Get page rolesGET/$pageId/roles
Publish draft postPOST/{post-id} — body: is_published=true

API Call Patterns

GET:

$result = Invoke-RestMethod -Uri "https://graph.facebook.com/v25.0/ENDPOINT?access_token=$token" -ErrorAction Stop

POST (form body):

$result = Invoke-RestMethod -Uri "https://graph.facebook.com/v25.0/ENDPOINT" -Method POST `
    -Body @{ field1="value1"; field2="value2"; access_token=$token } -ErrorAction Stop

DELETE:

$result = Invoke-RestMethod -Uri "https://graph.facebook.com/v25.0/{id}?access_token=$token" -Method DELETE -ErrorAction Stop

Multipart (image/video upload):

$boundary  = [System.Guid]::NewGuid().ToString()
$fileBytes = [System.IO.File]::ReadAllBytes($filePath)
$fileName  = [System.IO.Path]::GetFileName($filePath)
$stream    = New-Object System.IO.MemoryStream
$writer    = New-Object System.IO.StreamWriter($stream)
$writer.Write("--$boundary`r`nContent-Disposition: form-data; name=`"message`"`r`n`r`n$message`r`n")
$writer.Write("--$boundary`r`nContent-Disposition: form-data; name=`"access_token`"`r`n`r`n$token`r`n")
$writer.Write("--$boundary`r`nContent-Disposition: form-data; name=`"source`"; filename=`"$fileName`"`r`nContent-Type: image/jpeg`r`n`r`n")
$writer.Flush(); $stream.Write($fileBytes, 0, $fileBytes.Length)
$writer.Write("`r`n--$boundary--`r`n"); $writer.Flush()
$result = Invoke-RestMethod -Uri "https://graph.facebook.com/v25.0/$pageId/photos" -Method POST `
    -ContentType "multipart/form-data; boundary=$boundary" -Body $stream.ToArray() -ErrorAction Stop

Scheduled post — convert local time to Unix timestamp:

$runAt    = [datetime]"2026-03-15 09:00"
$unixTime = [int][double]::Parse(($runAt.ToUniversalTime() - [datetime]"1970-01-01").TotalSeconds)
$result   = Invoke-RestMethod -Uri "https://graph.facebook.com/v25.0/$pageId/feed" -Method POST `
    -Body @{ message="text"; published="false"; scheduled_publish_time=$unixTime; access_token=$token } -ErrorAction Stop

STEP 3 — Handle Errors

try {
    # ... API call ...
} catch {
    $err     = $_.ErrorDetails.Message | ConvertFrom-Json -ErrorAction SilentlyContinue
    $code    = $err.error.code
    $subcode = $err.error.error_subcode
    $msg     = $err.error.message
}
CodeSubcodeMeaningFix
100—Invalid parameterCheck the parameter values
102—Session expiredRe-run setup to get a new token
190460Token expiredRe-run setup with a new short-lived token
190467Invalid tokenRe-run setup
200—Permission deniedAdd the permission listed in error.message to your app
10—Permission denied (page)Add pages_read_engagement or pages_manage_posts
230—Requires re-authRe-run setup
368—Temporarily blockedWait and retry; page may be rate-limited

Permissions Reference

PermissionRequired for
pages_manage_postsCreate, delete, schedule posts
pages_read_engagementRead posts, likes, comments, insights
pages_show_listList pages you manage
pages_manage_metadataUpdate page settings
pages_manage_engagementModerate comments, reply to reviews
pages_read_user_contentRead visitor posts and comments
pages_manage_adsManage ad campaigns on the page
pages_manage_instant_articlesManage Instant Articles

If a permission is missing:

  1. Go to Meta for Developers
  2. Select your app → Permissions and Features
  3. Add the required permission
  4. Regenerate token via Graph API Explorer
  5. Re-run setup with the new token

AGENT RULES

  • Always load credentials first. If missing or incomplete, guide setup.
  • Only use FB_PAGE_TOKEN and FB_PAGE_ID for API calls. FB_APP_ID and FB_APP_SECRET are for token exchange only.
  • Never write extra fields to the credentials file (no owner IDs, conv IDs, or third-party keys).
  • Remove FB_APP_SECRET from credentials.json after token exchange — it is not needed for API calls.
  • Least-privilege: only request the permissions your use case needs. Do not request pages_manage_ads or pages_manage_instant_articles unless explicitly needed.
  • Rotate FB_PAGE_TOKEN periodically via Graph API Explorer, and immediately if the host is ever compromised.
  • All API calls go to graph.facebook.com only. No external forwarding, no third-party services.
  • Construct API calls inline from user intent — don't look for script files.
  • On any error: parse error.code + error.error_subcode, map to the table above, tell the user exactly what to do.
  • If a permission is missing: name it, link to Meta for Developers, say to re-run setup.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

72.84%
按下载量换算5,522

安全审计

VirusTotal

可疑

ClawScan

通过

Static analysis

未展示

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills