SocialKit Meta Auth

通过 Node 脚本走 Meta OAuth 授权流程：查看连接状态、生成登录链接、用用户回传的重定向 URL 换取令牌，并报告可发帖的主页、关联的 Instagram 专业账号或 Threads 用户及有效期。依赖 socialkit-social-core，需自备 Meta 应用凭据。

热度 36.94

最近更新 2026-11-06 14:59:23

安装

发给 Agent

帮我安装这个技能：npx secure-skills-cli add ahmadhussain0335/socialkit-meta-auth

Metadata

name: socialkit-meta-auth
description: Connects the user's own Meta app to their Facebook Pages, linked Instagram professional accounts and Threads profile, and stores the tokens securely. Use before the first Facebook, Instagram or Threads post, when a Meta token expired or was revoked, or to check which Pages and accounts are connected.
license: MIT
metadata: {"author":"Ahmad Hussain","platform":"meta","requires":"socialkit-social-core"}

Setup (app, redirect page, environment): setup.

Check what is connected: node scripts/auth.mjs --platform facebook --status (and --platform threads). Instagram uses the facebook sign-in.
If not connected, run node scripts/auth.mjs --platform <facebook|threads> --start and give the user the signInUrl. Ask them to sign in and paste back the full URL of the page they land on.
Finish: node scripts/auth.mjs --platform <facebook|threads> --finish --url "<pasted URL>"
Report the connected Pages (with canPost), linked Instagram accounts, or the Threads user and expiry.

Never print or paste tokens or the app secret. The pasted redirect URL is single-use.
A Page with canPost: false needs the user to get a content role on that Page.
No Instagram listed under a Page: the Instagram account is personal or not linked.

META_AUTH_STATE: the URL is from an older attempt; start again.
META_AUTH_EXCHANGE: the redirect URI does not exactly match the app settings, or the app ID/secret pair is wrong (Threads has its own pair).
THREADS_TOKEN_EXPIRED: sign in again; expired tokens cannot be refreshed.