facebookFlows
Skill63 starsChanged yesterdayMITView on GitHub
The Facebook part of flow: Facebook's recorded flows, their MCP tools (facebookFlow<Name> and facebookFlow<Name>Live), what each Facebook flow's steps must answer, Facebook's overlays and the profileSetup example. Read with its shared counterpart, skills/flow/SKILL.md (the flows guide), when recording or running a flow on Facebook.
In this repository82 other files it gives its agents.
- AGENTS.mdAGENTS.md
- log-discord-channel-replySkill
- log-discord-forum-postsSkill
- log-discord-group-chat-readSkill
- log-discord-meme-replySkill
- log-discord-server-replySkill
- log-discord-server-searchSkill
- log-facebook-groupsSkill
- log-facebook-marketplace-listingsSkill
- log-inbox-boss-maxxingSkill
- log-inbox-governor-resetSkill
- log-inbox-reactionsSkill
- log-inbox-rea-looksmaxxingSkill
- log-inbox-scope-ajobSkill
- log-inbox-show-meSkill
- log-inbox-sign-inSkill
- log-inbox-triageSkill
- log-inbox-voice-noteSkill
- log-instagram-dm-replySkill
- log-instagram-new-platformSkill
- log-linkedin-networkSkill
- log-linkedin-postsSkill
- log-reddit-contributor-maxxingSkill
- log-slack-dm-replySkill
- log-twitter-affiliate-marketingSkill
- log-twitter-collab-maxxingSkill
- log-twitter-dm-inboxSkill
- log-twitter-engagement-repliesSkill
- log-twitter-engager-dmsSkill
- log-twitter-followersSkill
- log-twitter-follow-upsSkill
- log-twitter-get-the-actionSkill
- log-twitter-manager-maxxingSkill
- log-twitter-network-maxingSkill
- log-twitter-niche-map-regionSkill
- log-twitter-notificationsSkill
- log-twitter-recruitingSkill
- log-twitter-reply-guy-funnelSkill
- log-twitter-topic-repliesSkill
- log-twitter-who-needs-youSkill
- log-web-competitor-trafficSkill
- accountToDryRunSkill
- adsPowerSkill
- agentHooksSkill
- callTimingSkill
- captureRuleSkill
- commitLogSkill
- consoleSkill
- conversationsSkill
- devlogMaxxingSkill
- discordServersSkill
- facebookInspectSkill
- facebookWarmupSkill
- flowSkill
- governorSkill
- hostSkill
- humanMouseSkill
- inspectSkill
- instagramSkill
- knowledgeBaseSkill
- The first 60 shown.
The file
Files
facebookFlows
How every flow is recorded, built and run (inspect, log flow fromInspect,
params, dry run, live run, the machine, confirming requests) is
skills/flow/SKILL.md. This is what only applies on Facebook.
Tools
Each Facebook flow has its own MCP tool, facebookFlow<Name>, and a live
twin, facebookFlow<Name>Live, that runs it on Facebook with
confirmLive: true (profileSetup is facebookFlowProfileSetup and
facebookFlowProfileSetupLive; facebookLanguageEnglish is
facebookFlowLanguageEnglish). The CLI words stay log flow run <name>.
The flows recorded on Facebook (src/browser/flow/definitions/):
deletePost, facebookLanguageEnglish, groupHeaderMenus, groupMembers,
groupPostComments, groupPostDialog, groupTabs,
marketplaceListingDelete, marketplaceListingPublish,
messengerPinCreate, postComment, profilePhotoPost, profilePost,
profileSetup, and the five warm-up activities (warmupCreateAccessCheck,
warmupFeedBrowse, warmupMarketplaceBrowse, warmupMessagesVisit,
warmupSellingVisit; see skills/facebookWarmup/SKILL.md).
What Facebook's flows check
marketplaceListingPublishchecksbuy_location, the set-location answer's city, the create page'smarketplace_new_seller_can_post_itemandsell_location(so it stops before the form when the account may not post), and the listing id in the create answer (noListingId).profileSetup's three saves check their mutations answered 2xx (no saved answers to read fields from yet).deletePost:move_to_trash_story.successtrue;postComment:comment_create.feedback_comment_edge; the posts:story_create.story_id.- A plain endpoint
expect:/profile/picture/upload/isprofilePictureUpload.
The profileSetup example
log inspect start --account <a> --url https://www.facebook.com/me --bypass --now
log inspect do click <ref> --live ... # one step at a time
log inspect do stop
log flow fromInspect ~/.logCli/runs/inspect/<run> --name profileSetup \
--rename text1=firstName --rename text2=lastName --rename file1=profilePhoto --rename file2=coverPhoto
log flow run profileSetup --account <a> --set firstName=Bethlehem --set lastName=Trash \
--set profilePhoto=<path|url> --set coverPhoto=<path|url>
log flow run profileSetup --account <a> ... --live --bypass --nowOver MCP: facebookFlowProfileSetup with account and the params by name;
facebookFlowProfileSetupLive with confirmLive: true.
Controls on Facebook
"Upload Photo" in a recording finds Facebook's "Upload photo": controls
match by role, then name (skills/flow/SKILL.md, Deterministic steps).
Facebook's overlays
| Overlay | Page state | Checked by |
| "To allow or block browser notifications from Facebook…" | browserNotificationsNotice | gone from the page (Escape sends no call) |
"What happened" … "Ended on <date>" | pastNoticeDialog | useAccountStatusClearEnrollmentEntryPointActionMutation answers data.xfb_ixt_gateway_clear_flow: true |
A "What happened" with no "Ended on" is not cleared: it stays unknown, for SubQ to read (rule 73).
Rebuild Facebook's request docs after a run: log capture docs.
Saved flows
| Flow | Recorded | Does |
profileSetup | Lancaster, 2026-10-19; the picture steps checked on Exeter, 2026-10-24 | Profile picture, cover photo, name (13 steps). The picture steps wait on the dialog query, the upload and the set mutation, inside "Choose profile picture". The host runs only the parts Twenty has data for (flowWithParams). |
marketplaceListingDelete | Bethlehem, 2026-10-23 | Delete one Marketplace listing from Selling: More options, Delete listing, Delete, then "No, haven't sold" on Facebook's survey (6 steps). The menu answer must name the listing id given, and so must the delete answer (commerce_for_sale_item_delete.deleted_for_sale_item_id). Run it through log facebook listing remove, which then sets the Twenty row REMOVED. |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

