Skip to main content
skill CX Codex

facebook-page-posts — Claude Code skill: what it does, how to install

facebook-page-posts extracts posts from public Facebook pages with engagement counts, external links, and reactions using an active browser session.

MIT 1 installs ★ 6,409 updated 2026-08-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add browser-act/skills --skill facebook-page-posts -a claude-code
Open on GitHub

What facebook-page-posts does

This skill gathers timeline posts from public Facebook pages. It first calls scripts/get-page-id.py to turn the target page URL into a numeric identifier. Next, scripts/get-page-posts.py pulls post batches containing full text, hashtags, clean outgoing links without redirects, and media types. It supports cursor pagination alongside --after-time and --before-time timestamp filters.

Results include comment counts, share counts, and individual reaction tallies for Like, Love, Care, Wow, Haha, Sad, and Angry. Without an open Facebook tab and an active user login in the browser, the scripts cannot read session cookies and will fail.

Execution stays strictly within what a logged-in user can see in the browser interface. Direct image URLs are not returned in the payload, which provides only media IDs and asset types.

What it helps with

  • scrape posts from a public Facebook page with engagement counts
  • filter timeline posts by specific date ranges using timestamps
  • extract clean external links and hashtags without redirect wrappers
  • break down post reactions into like, love, care, and other types

Example prompts for the agent

  • Scrape the latest 5 posts from https://www.facebook.com/cern with their reaction breakdown
  • Fetch posts from the CERN Facebook page published after timestamp 1779460000

How to install facebook-page-posts

1Skills CLI (Vercel)

npx skills add browser-act/skills --skill facebook-page-posts -a claude-code

2Manually: put the files in place

~/.claude/skills/facebook-page-posts/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/facebook-page-posts/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about facebook-page-posts

How to install facebook-page-posts in Claude Code?

Run npx skills add browser-act/skills --skill facebook-page-posts -a claude-code. The file will be placed into ~/.claude/skills/facebook-page-posts/SKILL.md.

What does facebook-page-posts do?

It reads an open public Facebook page timeline through the user browser session to export structured post data, engagement numbers, and detailed reaction counts.

Can it extract posts without a logged-in Facebook account?

No, it requires an open browser tab with an active Facebook login session because the underlying scripts rely on existing browser cookies.

Source text

SKILL.md · MIT
---
name: facebook-page-posts
description: "Scrapes posts from any public Facebook Page timeline, returning structured data including post text, author info, engagement metrics (likes/comments/shares), reaction breakdowns (like/love/haha/wow/sad/angry/care), hashtags and external links, and media type. Use when user wants to scrape Facebook posts, extract Facebook page content, get Facebook post data, collect Facebook engagement stats, download Facebook posts, monitor a Facebook page, crawl Facebook timeline, get Facebook reactions, get like count/comment count/share count from Facebook, Facebook post bulk export, Facebook social media analytics. Supports date range filtering (afterTime/beforeTime) and cursor-based pagination for bulk collection."
---

# Facebook — Page Posts Scraper

> Facebook page URL → list of posts with full engagement metrics and text references

## Language

All process output to user (progress updates, process notifications) must be in English.

## Objective

Extract posts from a public Facebook Page timeline, including post content, engagement counts, reaction breakdowns, and text references (hashtags/links).

## Prerequisites

- The target Facebook page is open in the browser (e.g., `https://www.facebook.com/cern`)
- User is logged into Facebook (user avatar visible in the top right)

## Pre-execution Checks

### 1. Tool Readiness

If browser-act has been confirmed available in the current session → skip this step.

Invoke `browser-act` via Skill tool to load usage. If installation or configuration issues arise, follow its guidance to resolve then retry.

### 2. Login Verification

If login status for Facebook has been confirmed in the current session → skip this step.

Otherwise: navigate to `https://www.facebook.com` and check:
- User avatar or name visible in top right → logged in, continue
- Login button visible → not logged in, inform the user and assist with login

User refuses or cannot log in → terminate execution.

## Capability Components

> This Skill's operational boundary = what the user can manually do in their browser. It only reads data already displayed to the user on the page, never bypassing authentication or access controls. JS code is encapsulated in Python files under the `scripts/` directory, invoked via `eval "$(python scripts/xxx.py {params})"`. `$(...)` is bash syntax; it is recommended to use the bash tool for execution.

### API: Resolve Facebook page URL to numeric page ID

`eval "$(python scripts/get-page-id.py '{page_url}')"`

Parameters:
- `page_url`: Full Facebook page URL, e.g. `https://www.facebook.com/cern`

**Must run while the target page is open** (or any Facebook page is open) so the browser has Facebook cookies.

Output example:
```json
{
  "pageId": "100064792144187",   // Numeric page ID used in all subsequent API calls
  "pageUrl": "https://www.facebook.com/cern"
}
```

### API: Fetch posts from page timeline

`eval "$(python scripts/get-page-posts.py '{page_id}' --cursor '{cursor}' --after-time {after_time} --before-time {before_time} --count {count})"`

Parameters:
- `page_id`: Numeric Facebook page ID (from get-page-id above)
- `--cursor`: Pagination cursor string from previous response `pagination.endCursor`; omit or pass `null` for first page
- `--after-time`: Unix timestamp (seconds); only return posts after this time; omit or pass `null` for no filter
- `--before-time`: Unix timestamp (seconds); only return posts before this time; omit or pass `null` for no filter
- `--count`: Number of posts per batch, default `5`, max recommended `10`

Output example:
```json
{
  "posts": [
    {
      "postId": "1417704873732571",                        // Numeric post ID
      "url": "https://www.facebook.com/cern/posts/pfbid…", // Post permalink
      "text": "CERN Council updates European Strategy…",   // Full post text
      "textReferences": [
        {
          "type": "ExternalUrl",                           // "ExternalUrl" or "Hashtag"
          "url": "https://home.cern/...",                  // Clean URL (not l.facebook.com redirect)
          "offset": 731,                                   // Position in text
          "length": 96
        },
        {
          "type": "Hashtag",
          "url": "https://www.facebook.com/hashtag/espp",
          "offset": 296,
          "length": 5
        }
      ],
      "creationTime": 1779460218,                          // Unix timestamp (seconds)
      "user": {
        "id": "100064792144187",                           // Page numeric ID
        "name": "CERN",                                    // Page display name
        "profileUrl": "https://www.facebook.com/cern"     // Page URL
      },
      "likes": 1220,                                       // Total reactions count
      "comments": 44,                                      // Comment count
      "shares": 122,                                       // Share count
      "topReactions": [
        { "name": "Like",  "count": 1108 },
        { "name": "Love",  "count": 92 },
        { "name": "Care",  "count": 9 },
        { "name": "Wow",   "count": 8 },
        { "name": "Haha",  "count": 1 },
        { "name": "Sad",   "count": 1 },
        { "name": "Angry", "count": 1 }
      ],
      "topReactionsCount": 1220,                           // Same as likes, total reactions
      "media": {
        "type": "Photo",                                   // "Photo", "Video", or null for text-only
        "id": "photo_id_string",                           // Media asset ID
        "viewsCount": null                                 // Video view count; null for photos
      },
      "feedbackId": "ZmVlZGJhY2s6MTQxNzcw…"               // Base64 feedback ID
    }
  ],
  "pagination": {
    "endCursor": "Cg8Ob3JnYW5pY19jd…",                   // Pass to --cursor for next page
    "hasNextPage": true                                    // false when no more posts
  }
}
```

Error handling: If response contains `"error": true`, check that the target page is open and the user is logged in, then retry once. If the error persists, the `doc_id` may have expired — check experience notes for updates.

## Pagination

**API Pagination**: cursor-based. Pass `pagination.endCursor` from each response as `--cursor` in the next call. Start value: omit `--cursor` (first page). Termination: `pagination.hasNextPage === false`.

## Success Criteria

`posts.length >= 1` AND `posts[0].postId` is non-null AND `posts[0].likes` is non-null

## Known Limitations

- `media.id` is returned but media thumbnail/photo URLs are not included in the API response for this query; only type and ID are available
- `viewsCount` is only populated for Video-type attachments; null for photos
- `feedbackId` is present but detailed reaction dialog data (individual reactor profiles) requires a separate API call not covered by this Skill
- The `doc_id: 27278869228466784` is a Facebook internal query ID that may change when Facebook deploys updates; if all calls return errors, the doc_id may need to be recaptured via HAR recording on the page
- Requires an active Facebook login session; public/unauthenticated access is not supported
- Date filtering (`afterTime`/`beforeTime`) applies to the timeline cursor position, not a strict server-side filter; posts near the boundary may occasionally appear outside the specified range

## Execution Efficiency

- **Batch orchestration**: Write a bash script to loop through the command templates serially within a single session; do not parallelize within one browser (prone to triggering anti-scraping restrictions). Add a 1–2 second delay between paginated calls to avoid rate limiting. To increase throughput, open multiple browser sessions and distribute work across them — each session has an independent fingerprint so rate limits apply per session
- **Test before batch execution**: After writing a batch script, you must first test with 1-2 items to verify the script runs correctly; only then run the full batch. Never skip testing and execute in batch directly
- **Reduce redundant pre-operations**: Run `get-page-id` once per page URL and reuse the result for all paginated calls
- **Error resumption**: Save results page by page during batch processing; on failure, resume from the last successful `endCursor` rather than starting over

## Experience Notes

Path: `{working-directory}/browser-act-skill-forge-memories/facebook-posts-scraper-facebook-page-posts.memory.md`

**Before execution**: If the file exists, read it first — it records unexpected situations encountered during past executions (e.g., a strategy has become ineffective); adjust strategy order accordingly.

**After execution**: If an unexpected situation is encountered (strategy became ineffective, page redesigned, anti-scraping upgraded, better path discovered), append a line:
`{YYYY-MM-DD}: {what happened} → {conclusion}`

Normal execution does not write to the file. Do not record what keywords were used or how many results were returned — those are task outputs, not experience.

© browser-act · MIT · browser-act/skills

Similar skills

All skills for Browser and scraping →

From the same set11

The whole set →
amazon-competitor-analyzer amazon-competitor-analyzer pulls product data from Amazon by ASIN and compares pricing, specs, and reviews across competitors. Identifies weak points in rival strategies and uncovers market gaps for your own product. CX Codex +1 133installs youtube-channel-api-skill youtube-channel-api-skill is a skill that searches YouTube channels through BrowserAct API. Find creators by topic or gather competitor channel data. CX Codex +1 5installs taobao-shop-catalog taobao-shop-catalog pulls a Taobao or Tmall store's product list by shopId, page by page: itemId, title, image link and item link. CX Codex +1 1installs ecommerce-listing ecommerce-listing extracts structured product listings from e-commerce search results and category pages with filters and pagination. CX Codex +1 1installs facebook-page-profile-posts facebook-page-profile-posts reads posts from a public Facebook Page or profile and returns reactions, media, links, and author details. Use it for exports or timeline monitoring. CX Codex +1 1installs social-media-finder-skill social-media-finder-skill looks up public profiles of a person or a brand on Facebook, Twitter, Instagram, LinkedIn, TikTok and hands back a CSV with the links and follower counts. CX Codex +1 1installs facebook-groups-scrape-posts facebook-groups-scrape-posts collects posts from a Facebook group and returns JSON with authors, text, media, reactions, comments, and shares. CX Codex +1 1installs xiaohongshu-auto-posting xiaohongshu-auto-posting runs the whole Xiaohongshu posting cycle: finds topics people complain about, drafts a note in the style of strong posts, publishes, then reports metrics. CX Codex +1 1installs

Project sponsors

Companies that keep this analytics open