openclaw 网盘下载
OpenClaw

技能详情(站内镜像,无评论)

首页 > 技能库 > fb_page_manager

Publish posts to a Facebook Page via the Meta Graph API. Use when the user says "post to Facebook", "FB post", "粉專發文", "社群貼文", "幫我發文", "schedule post", "排程發文...

媒体与内容

许可证:MIT-0

MIT-0 ·免费使用、修改和重新分发。无需归因。

版本:v2.0.0

统计:⭐ 1 · 189 · 0 current installs · 0 all-time installs

1

安装量(当前) 0

🛡 VirusTotal :良性 · OpenClaw :良性

Package:aaazzzr/fb-page-manager

安全扫描(ClawHub)

  • VirusTotal :良性
  • OpenClaw :良性

OpenClaw 评估

The skill's code, required environment variables, and runtime instructions are coherent with a Facebook Page posting tool; nothing in the package attempts to contact unexpected endpoints or request unrelated secrets.

目的

Name/description, required binaries (node), required env vars (page token, page id, app secret), and the included script all align with the stated purpose of publishing to the Meta Graph API.

说明范围

SKILL.md properly limits actions to drafting, previewing, and calling the provided script. It instructs the agent to always preview and obtain user confirmation before publishing, but the provided CLI script itself does not enforce interactive confirmation — the safety depends on the agent following the SKILL.md workflow.

安装机制

No install spec is provided (instruction-only install) and the code files are included in the skill bundle. The only runtime requirement is Node; no external downloads, unusual installers, or third-party package pulls are present.

证书

Requested environment variables (LONG_META_page_TOKEN, META_PAGE_ID, META_APP_SECRET) are exactly those needed to post and compute appsecret_proof. Caveat: the token setup guide suggests storing the long-lived Page token in shell profile or in ~/.openclaw/openclaw.json — storing long-lived tokens in a shared skill/agent config increases exposure to other skills and processes, so users should consider storage and rotation policies.

持久

Skill does not request always:true or other elevated platform privileges. It does not modify other skills or system-wide settings. Autonomous invocation is enabled by default (normal) but should be combined with the confirmation step described in SKILL.md.

综合结论

This skill appears to do exactly what it says: post to a Facebook Page using the Graph API. Before installing, ensure you: (1) limit the token’s scopes to only what’s required (pages_manage_posts, pages_read_engagement), (2) avoid putting long-lived page tokens in shared or world-readable config files if you care about limiting exposure — prefer ephemeral tokens or secure credential storage and rotate tokens regularly, (3) confirm your agent w…

安装(复制给龙虾 AI)

将下方整段复制到龙虾中文库对话中,由龙虾按 SKILL.md 完成安装。

请把本段交给龙虾中文库(龙虾 AI)执行:为本机安装 OpenClaw 技能「fb_page_manager」。简介:Publish posts to a Facebook Page via the Meta Graph API. Use when the user says…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装:https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/aaazzzr/fb-page-manager/SKILL.md
(来源:yingzhi8.cn 技能库)

SKILL.md

打开原始 SKILL.md(GitHub raw)

---
name: fb-page-poster
description: Publish posts to a Facebook Page via the Meta Graph API. Use when the user says "post to Facebook", "FB post", "粉專發文", "社群貼文", "幫我發文", "schedule post", "排程發文", or provides content and says "post this" or "publish this". Supports text-only, image, link-in-comment, scheduled posts, and multilingual translation (ZH↔EN) with a review step before publishing.
version: 1.0.0
metadata: {"openclaw": {"emoji": "📘", "requires": {"env": ["LONG_META_page_TOKEN", "META_PAGE_ID", "META_APP_SECRET"], "bins": ["node"]}, "primaryEnv": "LONG_META_page_TOKEN"}}
---

# Facebook Page Poster

Publish content to a Facebook Page through the Meta Graph API.

## Environment Variables

| Variable | Purpose |
|---|---|
| `LONG_META_page_TOKEN` | Long-lived Page Access Token with `pages_manage_posts` and `pages_read_engagement` permissions |
| `META_PAGE_ID` | Numeric Page ID |
| `META_APP_SECRET` | Meta App Secret for appsecret_proof |

If any are missing, walk the user through `{baseDir}/references/token-setup-guide.md`.

## Workflow

### 1. Parse the request

Extract from the user message:
- **Content**: the text to post
- **Language direction**: ZH→EN, EN→ZH, ZH→ZH, or EN→EN
- **Post type**: text | image | link-in-comment | scheduled (combinable)
- **Tone**: infer automatically — marketing/social (upbeat, CTA) for promotions and events; formal/professional for announcements and corporate. Ask if ambiguous.
- **Image**: local file path or URL (if applicable)
- **Schedule**: ISO 8601 timestamp (if applicable)
- **Link**: URL for the first comment (if applicable)

### 2. Draft and translate — always preview first

**Never publish without user confirmation.**

If source language differs from target, translate with these rules:
- Preserve meaning, intent, hashtags
- Adapt idioms naturally, do not translate literally
- Keep brand names and proper nouns in original form
- Maintain emoji usage unless unnatural in target language

Present preview:

```
📋 Post Preview
─────────────────
[Post text here]

🔗 First comment: [URL or N/A]
🖼️ Image: [filename/URL or N/A]
⏰ Schedule: [time or "Publish immediately"]
─────────────────
Confirm? (yes / edit / cancel)
```

### 3. Publish

Run the script at `{baseDir}/scripts/fb-post.js`:

```bash
# Text-only
node {baseDir}/scripts/fb-post.js --type text --message "content"

# Image (file)
node {baseDir}/scripts/fb-post.js --type image --message "content" --image-file /path/to/img.jpg

# Image (URL)
node {baseDir}/scripts/fb-post.js --type image --message "content" --image-url "https://..."

# Link in first comment
node {baseDir}/scripts/fb-post.js --type text --message "content" --comment-link "https://..."

# Scheduled (append to any above)
node {baseDir}/scripts/fb-post.js --type text --message "content" --schedule "2025-12-25T10:00:00+0800"
```

Flags are combinable. Example — image + comment link + scheduled:

```bash
node {baseDir}/scripts/fb-post.js --type image --message "content" --image-url "https://..." --comment-link "https://..." --schedule "2025-12-25T10:00:00+0800"
```

### 4. Report result

- Show the post ID
- Confirm comment was posted (if link-in-comment)
- Confirm scheduled time (if scheduled)
- On error, show the message and suggest a fix

## Error reference

| Error | Likely cause | Fix |
|---|---|---|
| OAuthException / Invalid token | Token expired | Refresh via `{baseDir}/references/token-setup-guide.md` |
| Permission denied | Missing `pages_manage_posts` | Re-authorize token with correct scopes |
| Scheduled time in past | Must be ≥10 min in the future | Adjust the timestamp |
| Image too large | >10 MB | Compress or resize |
| Rate limit | Too many requests | Wait a few minutes, retry |