Garden Inbox
paperclipai/paperclip
Scan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections.
Check Facebook page inbox messages via Meta Business Suite browser automation.
$ npx skills add LeoYeAI/openclaw-master-skills --skill meta-fb-inbox -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills meta-fb-inbox --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/meta-fb-inbox .claude/skills/meta-fb-inbox && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "meta-fb-inbox" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/meta-fb-inbox into .claude/skills/meta-fb-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meta-fb-inbox", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/meta-fb-inboxType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill meta-fb-inbox -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills meta-fb-inbox --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/meta-fb-inbox .agents/skills/meta-fb-inbox && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "meta-fb-inbox" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/meta-fb-inbox into .agents/skills/meta-fb-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meta-fb-inbox", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill meta-fb-inbox -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills meta-fb-inbox --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/meta-fb-inbox .cursor/skills/meta-fb-inbox && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "meta-fb-inbox" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/meta-fb-inbox into .cursor/skills/meta-fb-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meta-fb-inbox", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/meta-fb-inbox--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill meta-fb-inbox -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills meta-fb-inbox --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/meta-fb-inbox .gemini/skills/meta-fb-inbox && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "meta-fb-inbox" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/meta-fb-inbox into .gemini/skills/meta-fb-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meta-fb-inbox", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills meta-fb-inboxInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill meta-fb-inbox -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/meta-fb-inbox .github/skills/meta-fb-inbox && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "meta-fb-inbox" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/meta-fb-inbox into .github/skills/meta-fb-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meta-fb-inbox", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill meta-fb-inbox -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills meta-fb-inbox --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/meta-fb-inbox .opencode/skills/meta-fb-inbox && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "meta-fb-inbox" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/meta-fb-inbox into .opencode/skills/meta-fb-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meta-fb-inbox", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
meta-fb-inboxCheck Facebook page inbox messages via Meta Business Suite browser automation.
Meta Fb Inbox is an agent skill from LeoYeAI/openclaw-master-skills. Check Facebook page inbox messages via Meta Business Suite browser automation. Use when asked to check Facebook messages, reply to FB customers, or manage Facebook page inbox. Supports multiple pages with custom aliases.
Its SKILL.md is about 5.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts (for example `README.md`, `_meta.json` and `scripts/list-chats.js`).
It sits in Productivity & Automation, covering Email management. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 3 files in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
curlnodeFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
business.facebook.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Meta Fb Inbox loads about 5.8k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 2,024 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 2,024 words, ~5,818 tokens.
.claude/skills/meta-fb-inbox/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.⚠️ CRITICAL: Always use profile:"openclaw" (isolated browser) for all browser actions. Never use Chrome relay. Keep the same targetId across operations to avoid losing the tab.
⚠️ CONTEXT Management:
snapshot refs:"aria" compact:true to find element refs, then act + click/type with ref.Before first use, check if config.json exists:
read file_path:"skills/meta-fb-inbox/config.json"⚠️ PATH RULE: Always use workspace-relative paths starting from skills/meta-fb-inbox/. Never use ../ or absolute paths.
If missing or empty, help the user run the setup wizard:
cd skills/meta-fb-inbox
node scripts/setup.jsconfig.json contains a pages array. Each page has an alias (display name) and url (Meta Business Suite inbox URL):
{
"pages": [
{
"alias": "fb fanpage",
"url": "https://business.facebook.com/latest/inbox/all/?&asset_id=123456789012345"
},
{
"alias": "fb fanpage 2",
"url": "https://business.facebook.com/latest/inbox/all/?&asset_id=987654321098765"
}
]
}When the user asks to check messages:
config.json → pages.This is the first step for all operations below.
Check and start browser service:
browser action:"status"If "running": false, start the browser service:
browser action:"start" profile:"openclaw"Wait 2-3 seconds for the service to initialize.
Read config to get the target page URL:
read file_path:"skills/meta-fb-inbox/config.json"Resolve the page alias to a URL (see "Resolving a Page" above).
Open browser:
browser action:"open" profile:"openclaw" targetUrl:"<pageUrl>"Capture targetId and url from response.
Wait for page load:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"wait","timeMs":3000}Check login state:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"evaluate","fn":"function(){return window.location.href;}"}business.facebook.com and shows the inbox → logged in, proceed.Proceed with the user's request.
Clean Up Browser Tabs (after all operations):
a. Open a blank tab:
browser action:"open" profile:"openclaw" targetUrl:"about:blank"b. Get all tabs:
browser action:"tabs" profile:"openclaw"c. Close all tabs except the newest one (about:blank):
browser action:"close" profile:"openclaw" targetId:"<your_targetId>"Complete flow: open page → screenshot → report.
read file_path:"skills/meta-fb-inbox/config.json" → resolve page URLbrowser action:"start" profile:"openclaw"browser action:"open" profile:"openclaw" targetUrl:<pageUrl> → get targetIdbrowser action:"act" profile:"openclaw" targetId:<targetId> request:{"kind":"wait","timeMs":4000}browser action:"snapshot" profile:"openclaw" targetId:<targetId> refs:"aria" compact:true<name> (<time>) <preview> [未讀/已讀]If the snapshot is hard to parse (Meta's DOM is complex), fall back to:
browser action:"screenshot" profile:"openclaw" targetId:<targetId>Then describe what you see in the screenshot.
Why get URLs? Having the direct conversation URL lets you jump straight to a chat later without searching for it again. Saves time when replying.
When to get URLs: After listing chats, get URLs for unread conversations or any conversation you might need to access again.
📝 Simple 3-Step Method:
Click into the conversation using the customer name:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"evaluate","fn":"function() { const containers = document.querySelectorAll('div[style*=\"position: absolute\"]'); for (let container of containers) { const nameEl = container.querySelector('div.x1vvvo52.x1fvot60.xxio538'); if (nameEl && nameEl.textContent.trim() === '<customer_name>') { nameEl.click(); return {clicked: true}; } } return {error: 'not found'}; }"}Replace <customer_name> with the actual customer name from your conversation list.
Wait 2 seconds for page to load and URL to update:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"wait","timeMs":2000}Get the current URL - it's automatically updated!
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"evaluate","fn":"function(){return window.location.href;}"}Store the URL alongside the chat info.
✅ Example URL Format:
https://business.facebook.com/latest/inbox/all/?&asset_id=123456789012345&selected_item_id=1234567890&thread_type=FB_MESSAGEOr with optional mailbox_id:
https://business.facebook.com/latest/inbox/all/?&asset_id=123456789012345&mailbox_id=123456789012345&selected_item_id=9876543210&thread_type=FB_MESSAGE🔍 Understanding the URL:
asset_id = Your Facebook page ID (stays the same)selected_item_id = Unique conversation ID (different for each customer)thread_type=FB_MESSAGE = Messenger conversation typemailbox_id = Optional, may appear for some conversations💾 How to Use Later:
Next time you need to access this conversation, skip all the searching:
browser action:"navigate" profile:"openclaw" targetId:"<targetId>" targetUrl:"<saved_conversation_url>"Wait 2 seconds, and you're in the conversation!
💡 Tip: Get URLs for unread messages during your check routine, store them in a file or memory, and reuse them for instant access.
🔄 Getting Multiple URLs:
If you need URLs for multiple conversations:
browser action:"navigate" profile:"openclaw" targetId:"<targetId>" targetUrl:"<pageUrl>"Alternative method (when already in conversation): If you're already viewing a conversation and just need its URL, skip step 1 and directly run step 3 - the URL is already there!
⚡ Fast Path: If you have the conversation URL from "Get URLs for Conversations":
browser action:"navigate" profile:"openclaw" targetId:"<targetId>" targetUrl:"<conversation_url>"Wait 2 seconds, then skip to step 3.
Standard Path:
To programmatically read messages:
Navigate to the conversation (if not already there).
Inject the read-messages script:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"evaluate","fn":"<contents_of_scripts/read-messages.js>"}Read the script file:
read file_path:"skills/meta-fb-inbox/scripts/read-messages.js"And pass its entire contents as the fn parameter (wrapped in parentheses).
Parse the response: The script returns an array of message objects:
[
{"text": "你好", "isCustomer": true, "hasImage": false, "imageUrl": null},
{"text": "[Image]", "isCustomer": true, "hasImage": true, "imageUrl": "https://scontent-..."}
]Download images (if any):
⚠️ Default download location: ~/Downloads (do NOT clutter the workspace).
For each message with hasImage: true:
cd ~/Downloads
curl -O "<imageUrl>"The downloaded file will use the original filename from the URL.
If you want a custom filename:
cd ~/Downloads
curl -o "fb-message-$(date +%Y%m%d-%H%M%S).jpg" "<imageUrl>"⚡ Fast Path (if you have conversation URL):
If you already obtained the conversation URL from "Get URLs for Conversations" section, skip step 1 and go directly:
browser action:"navigate" profile:"openclaw" targetId:"<targetId>" targetUrl:"<conversation_url>"Wait 2 seconds, then proceed to step 2 (Take snapshot to find input box).
Standard Path (when you don't have the URL):
Open the conversation:
Click the customer name in the conversation list:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"evaluate","fn":"function() { const containers = document.querySelectorAll('div[style*=\"position: absolute\"]'); for (let container of containers) { const nameEl = container.querySelector('div.x1vvvo52.x1fvot60.xxio538'); if (nameEl && nameEl.textContent.trim() === '<customer_name>') { nameEl.click(); return {clicked: true}; } } return {error: 'not found'}; }"}Replace <customer_name> with the actual customer name.
Wait 2 seconds for the conversation to load.
Take a snapshot to find the input box:
browser action:"snapshot" profile:"openclaw" targetId:"<targetId>" refs:"aria" compact:trueLook for textbox with [active] attribute.
Type the reply message:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"type","ref":"<input_ref>","text":"<your_message>"}After typing, wait 1 second for the send button to appear.
Take another snapshot to find the send button:
browser action:"snapshot" profile:"openclaw" targetId:"<targetId>" refs:"aria" compact:trueLook for a new button near the textbox. The send button appears after you type text (it replaces the "like" button).
Click the send button:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"click","ref":"<send_button_ref>"}Verify the message was sent:
Wait 2 seconds, then take a screenshot or check the conversation list to confirm the message appears.
⚡ Fast Path: If you have the conversation URL, navigate directly:
browser action:"navigate" profile:"openclaw" targetId:"<targetId>" targetUrl:"<conversation_url>"Wait 2 seconds, then proceed to the label operations.
Open the conversation (if not already open, and you don't have URL).
Take a snapshot to locate the label's remove button:
browser action:"snapshot" profile:"openclaw" targetId:"<targetId>" refs:"aria" compact:trueLook for the Labels section in the right sidebar (appears before Notes section):
heading with level=3 (the Labels heading)button elementbutton with text "clearLabel"Click the clearLabel button:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"click","ref":"<clearLabel_ref>"}Example from snapshot:
- heading [level=3] [ref=eAAA] ← Labels heading
- button [ref=e949]: ← Label button (shows label name)
- button "clearLabel" [ref=e952] ← Remove button (THIS ONE!)Click the clearLabel button (ref=e952) to remove the label.
Wait for the change to apply:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"wait","timeMs":1500}Verify the label was removed (optional): Take a screenshot or snapshot to confirm the label is gone.
- combobox "label" [ref=eXXX]browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"type","ref":"<combobox_ref>","text":"<label_name>","submit":true}⚡ Fast Path: If you have the conversation URL, navigate directly:
browser action:"navigate" profile:"openclaw" targetId:"<targetId>" targetUrl:"<conversation_url>"Wait 2 seconds, then proceed to the note operations.
Question: Do you need to ADD or EDIT a note?
Take a snapshot of the conversation sidebar.
Look for the Notes section (usually appears after Labels section).
Check what you see:
ONLY see a "Add note" type button/link (single button, no existing note text) → Contact has NO note → Use "Add a New Note" section below.
See an "Edit" link + existing note text (usually with timestamp) → Contact has existing note → Use "Edit an Existing Note" section below.
Simple rule:
How to identify in snapshot:
button [ref=eXXX] or link [ref=eXXX] with NO paragraph text nearbylink [ref=eXXX] (edit) + link [ref=eYYY] (delete) + paragraph [ref=eZZZ]: "note text"The Notes section is located below the Labels section in the right sidebar. There are two states:
paragraph element)Best Practice: Keep only one note per contact. Use "Edit" to update existing notes rather than adding multiple notes.
In snapshot, look for these patterns:
No note:
- heading [level=3] [ref=eXXX] ← Notes heading
- button [ref=eYYY] ← Single "add note" buttonHas note:
- heading [level=3] [ref=eXXX] ← Notes heading
- link [ref=eYYY] ← "add note" link
- text: "X minutes ago ·" ← Timestamp
- link [ref=eZZZ] ← Edit link (THIS ONE for editing!)
- text: "·"
- link [ref=eAAA] ← Delete link
- paragraph [ref=eBBB]: "note text" ← Existing note contentWhen to use: Contact already has a note. You will see an Edit link next to existing note text with timestamp.
Step-by-step:
Open the conversation (click customer name in chat list). Wait 2 seconds for it to load.
Take snapshot to find the Edit button:
browser action:"snapshot" profile:"openclaw" targetId:"<targetId>" refs:"aria" compact:trueLook for the pattern (Notes section):
- heading [level=3] [ref=eAAA] ← Notes heading
- link [ref=eBBB] ← "add note" link
- text: "4 hours ago ·" ← Timestamp
- link [ref=eXXX] ← Edit link (THIS ONE!)
- text: "·"
- link [ref=eYYY] ← Delete link
- paragraph [ref=eZZZ]: "Customer note" ← Current noteKey: Find the link that appears AFTER the timestamp text and BEFORE the "·" separator. That's your Edit button.
Click Edit button:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"click","ref":"<edit_button_ref>"}Wait for edit form:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"wait","timeMs":1500}Take snapshot to find the textbox:
browser action:"snapshot" profile:"openclaw" targetId:"<targetId>" refs:"aria" compact:trueLook for:
- textbox [ref=eXXX]: "Customer note" ← Current text (contains existing note)
- button [ref=eYYY] ← Cancel button
- button [ref=eZZZ] ← Delete button
- button [disabled] [ref=eAAA] ← Save button (disabled until you change text)Key: The textbox will have the current note text. The Save button will show [disabled] attribute.
Click textbox to focus:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"click","ref":"<textbox_ref>"}Select all existing text (Cmd+A):
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"press","key":"Meta+a"}Type new text (replaces selected text):
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"type","ref":"<textbox_ref>","text":"Customer ID: 12345 ✅"}Wait for Save button to enable:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"wait","timeMs":500}Take snapshot to find enabled Save button:
browser action:"snapshot" profile:"openclaw" targetId:"<targetId>" refs:"aria" compact:trueLook for:
- button [ref=eXXX] [cursor=pointer]: ← Now enabled! (no [disabled] attribute)Key: The Save button will now show [cursor=pointer] and will NOT have [disabled] attribute.
Click Save:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"click","ref":"<save_button_ref>"}Wait and verify:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"wait","timeMs":2000}Take screenshot to confirm update.
Common mistakes to avoid:
When to use: Contact has NO existing note. You will see ONLY a single button/link (no existing note text).
Step-by-step:
Open the conversation (click customer name in chat list). Wait 2 seconds for it to load.
Take snapshot to find the "add note" button:
browser action:"snapshot" profile:"openclaw" targetId:"<targetId>" refs:"aria" compact:trueLook for the pattern (Notes section with NO existing note):
- heading [level=3] [ref=eAAA] ← Notes heading
- button [ref=eXXX] ← Single "add note" button (THIS ONE!)Key: You should see ONLY one button/link under the Notes heading, with NO paragraph element containing note text.
Click "add note" button:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"click","ref":"<button_ref>"}Wait for the textbox:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"wait","timeMs":1500}Take snapshot to find the textbox:
browser action:"snapshot" profile:"openclaw" targetId:"<targetId>" refs:"aria" compact:trueLook for:
- textbox [ref=eXXX]: ← Input field (may show "Hidden Label")
/placeholder: ... ← Placeholder text
- button [ref=eYYY] ← Cancel button
- button [disabled] [ref=eZZZ] ← Save button (disabled at first)Key: The textbox might be labeled "Hidden Label" or similar. Look for [disabled] attribute on the Save button.
Type the note text:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"type","ref":"<textbox_ref>","text":"Customer note text here"}Wait for Save button to become enabled:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"wait","timeMs":500}Take snapshot to find the enabled Save button:
browser action:"snapshot" profile:"openclaw" targetId:"<targetId>" refs:"aria" compact:trueLook for:
- button [ref=eXXX] [cursor=pointer]: ← Now enabled (no [disabled] attribute!)Click Save button:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"click","ref":"<save_button_ref>"}Wait and verify:
browser action:"act" profile:"openclaw" targetId:"<targetId>" request:{"kind":"wait","timeMs":2000}Take a screenshot to confirm the note appears in the sidebar.
Common mistakes to avoid:
In snapshot:
- link [ref=eXXX] ← Edit link
- text: "·"
- link [ref=eYYY] ← Delete link (THIS ONE!)If multiple pages are configured:
browser action:"navigate" profile:"openclaw" targetId:"<targetId>" targetUrl:"<newPageUrl>"https://business.facebook.com/latest/inbox/all/?&asset_id=<PAGE_ID>© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 5 other files (scripts) in skills/meta-fb-inbox of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Meta Fb Inbox next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Meta Fb Inbox this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~5.8k | Automated safety check: Pass | MIT | |
| Garden Inboxpaperclipai/paperclip | 100k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Continuetelegramdesktop/tdesktop | 33k | 2 repos | ~9.4k | Automated safety check: Pass | GPL-3.0 | |
| Process Inboxtelegramdesktop/tdesktop | 33k | 1 repos | ~5.4k | Automated safety check: Pass | GPL-3.0 | |
| Process InboxTDesktop-x64/tdesktop | 3k | — | ~4.3k | Automated safety check: Pass | GPL-3.0 | |
| Career-Ops Gmail Lead Plugincareer-ops-hq/career-ops | 74k | — | ~233 | Automated safety check: Notes | MIT |
paperclipai/paperclip
Scan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections.
telegramdesktop/tdesktop
Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.
telegramdesktop/tdesktop
Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.
TDesktop-x64/tdesktop
Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.
career-ops-hq/career-ops
Pulls job leads from a Gmail label into the career-ops pipeline, extracting job URLs from DMARC-passing emails and de-duplicating against existing leads.
Atomic-Mail/atomic-mail-agentic
Read and write email through the Atomic Mail from an AI agent.
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Categories
Check Facebook page inbox messages via Meta Business Suite browser automation. Meta Fb Inbox is an agent skill from LeoYeAI/openclaw-master-skills. Check Facebook page inbox messages via Meta Business Suite browser automation.
Meta Fb Inbox fits situations like: asked to check Facebook messages; reply to FB customers; manage Facebook page inbox.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill meta-fb-inbox -a claude-code`. Or copy the skill folder (skills/meta-fb-inbox in LeoYeAI/openclaw-master-skills) into .claude/skills/meta-fb-inbox in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill meta-fb-inbox -a codex`. Or copy the skill folder (skills/meta-fb-inbox in LeoYeAI/openclaw-master-skills) into .agents/skills/meta-fb-inbox in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill meta-fb-inbox -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/meta-fb-inbox, .gemini/skills/meta-fb-inbox, .github/skills/meta-fb-inbox and .opencode/skills/meta-fb-inbox in your project.
Going by SKILL.md and its folder, Meta Fb Inbox needs JavaScript for the scripts in its folder and the command-line tools its instructions call (curl and node). Our summary lists: Node.js.
SKILL.md names 1 domain. In commands or code: business.facebook.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Meta Fb Inbox is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.8k tokens (SKILL.md is roughly 23k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Meta Fb Inbox: Garden Inbox (paperclipai/paperclip, 100k stars), Continue (telegramdesktop/tdesktop, 33k stars), Process Inbox (telegramdesktop/tdesktop, 33k stars) and Process Inbox (TDesktop-x64/tdesktop, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.