Facebook Page Engagement Drafter
Draft replies to comments on your Facebook Page's posts, in your Page voice.
How to use it
- Hit Copy the whole skill.
- Claude: ⋯ → Download .md, then Customize → Skills → Add → Upload skill.
ChatGPT: make a Project and paste it into Instructions.
Neither? Paste it at the top of a new chat — it works for that chat. - Describe your job in plain words. The AI follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit sergebulaev/facebook-skills/.codex-marketplace/facebook-skills/skills/fb-engagement-drafter#main ~/.claude/skills/fb-engagement-drafterFor one project only, change the path to .claude/skills/fb-engagement-drafter.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Show the full text113 lines
Facebook Page Engagement Drafter
Drafts replies to the comments on your Page's posts. Replying fast in the first hour is a ranking action on Facebook, not just community management: a Page that keeps the conversation alive gets more reach on that post. This skill drafts the replies; you post them.
The honest limitation
Publora has no Facebook comment endpoint (its comment and reaction endpoints
are LinkedIn-only), and create-post only creates new posts. So this skill
cannot auto-post a reply to a comment. Every draft comes back as a
copy-paste block for you to post in Facebook or Meta Business Suite by hand. This
is a documented limitation of the publish layer, not a missing feature here.
When to use
- User pastes the comments under one of their Page posts and says "reply to these"
- A comment thread needs on-brand responses that keep the conversation going
- A complaint or question needs a careful, human reply
Input
The Page post (for context) and the comments to reply to, pasted by the user, since this bundle has no built-in Page reader. Optionally the Page post URL (for the target link) and the Page's voice samples.
Output
- 1-3 reply variants per comment, each in the Page's voice
- A short note on which template each variant uses and why
- An approval card. On approval, each reply is returned as a copy-paste block with the target post URL.
Reply templates (references/reply-templates.md)
- C1 Answer-the-Question - they asked, you answer plainly plus one real detail
- C2 Thank-Plus-Add-Value - acknowledge, then add a useful extra (not a bare "thanks!")
- C3 Handle-the-Complaint - acknowledge, own it, offer the next step, take it to DM if needed
- C4 Turn-It-Into-a-Share - build on a positive comment so the thread itself becomes shareable
- C5 Invite-the-Spotlight - when a commenter shares a win, invite them to be featured (feeds FB10)
Steps
Voice profile first (all drafts). If ../../references/voice-profile.md has filled: yes, load it and match the user's voice fingerprint, hard rules, and CTA/link style throughout. If it is not filled, mention once that fb-humanizer --mode profile can learn their voice from a few posts, then proceed with the generic voice rules.
- Parse the post URL if given.
lib.url_parser.parse_facebook_url(url)returnspage,post_id,canonical_urlfor the target link. - Read the context. Ask the user to paste the post and the comments. Group the comments (questions, praise, complaints, wins).
- Pick a template per comment using the table above.
- Draft 1-3 variants per comment. Keep them short and human. Answer questions plainly with one real detail. For complaints, acknowledge first, never get defensive, offer a concrete next step.
- Humanizer pass. Scrub 2026 AI vocab by density, cap em dashes (a
reply is short, so at most one, never swapped for a period), strip canned
"Thank you for your feedback!" corporate filler and sincerity openers
("we'll be honest"). Leave the rhythm alone. Keep the Page voice.
Canonical rules:
fb-humanizerV3. - Approval card. Show each comment, its drafted replies, the template used, and the target post URL.
- On approval. Call
lib.publish(kind="comment", draft_text=<approved>, target_url=<canonical_url>). Because Publora has no Facebook comment endpoint, this always returns a copy-paste block. Paste each reply under the comment in Facebook or Meta Business Suite yourself.
Hard rules
Global voice rules: see root SKILL.md Voice rules. Additional skill-specific
rules:
- Reply fast and human. The first hour matters for reach; a fast, real reply beats a slow, polished one.
- Never paste a canned "Thank you for your feedback!". Acknowledge with content or do not reply.
- On a complaint: acknowledge first, never argue in public, offer a next step, move details to DM. Comments are public and screenshot-able.
- Do not hard-sell in a reply. Help first; mention the product only if it genuinely answers the question.
- Keep replies under a few short lines. A Page reply is not a press release.
Example
User: "Reply to these comments on my post: https://www.facebook.com/MyBakery/posts/123. Comments: 'Are you open Sunday?' and 'Best sourdough in town!'"
Skill: parses -> page MyBakery, post 123. Drafts a C1 Answer-the-Question reply to the first ("We are, 8 to 2 on Sundays. Come hungry.") and a C4 Turn-It-Into-a-Share reply to the second ("That means a lot. The Saturday batch is the one to beat, ask for it warm."). Shows the approval card.
User: "post both"
Skill: returns each reply as a copy-paste block with the post URL, since Publora has no Facebook comment endpoint. User pastes them in Facebook.
Files
SKILL.md- this filereferences/reply-templates.md- 5 comment-reply templates with examples
Related skills
fb-post-writer- for a standalone Page post rather than a replyfb-humanizer- scrub a reply before postingfb-content-planner- sets the daily comment-reply target this skill executes
| 1 | |
| 2 | name fb-engagement-drafter |
| 3 | description "Draft replies to comments on your Facebook Page's posts, in your Page voice. Use when the user pastes the comments under one of their Page posts and wants on-brand replies that earn more comments and shares. Drafts 1-3 variants per comment using proven templates (answer, thank plus add value, handle the complaint, turn it into a share). Publora has no Facebook comment endpoint, so every draft returns as a copy-paste block to post yourself. Not for writing top-level posts (use fb-post-writer)." |
| 4 | |
| 5 | |
| 6 | # Facebook Page Engagement Drafter |
| 7 | |
| 8 | Drafts replies to the comments on your Page's posts. Replying fast in the first |
| 9 | hour is a ranking action on Facebook, not just community management: a Page that |
| 10 | keeps the conversation alive gets more reach on that post. This skill drafts the |
| 11 | replies; you post them. |
| 12 | |
| 13 | ## The honest limitation |
| 14 | |
| 15 | Publora has **no Facebook comment endpoint** (its comment and reaction endpoints |
| 16 | are LinkedIn-only), and `create-post` only creates new posts. So this skill |
| 17 | **cannot auto-post** a reply to a comment. Every draft comes back as a |
| 18 | copy-paste block for you to post in Facebook or Meta Business Suite by hand. This |
| 19 | is a documented limitation of the publish layer, not a missing feature here. |
| 20 | |
| 21 | ## When to use |
| 22 | |
| 23 | User pastes the comments under one of their Page posts and says "reply to these" |
| 24 | A comment thread needs on-brand responses that keep the conversation going |
| 25 | A complaint or question needs a careful, human reply |
| 26 | |
| 27 | ## Input |
| 28 | |
| 29 | The Page post (for context) and the comments to reply to, pasted by the user, |
| 30 | since this bundle has no built-in Page reader. Optionally the Page post URL (for |
| 31 | the target link) and the Page's voice samples. |
| 32 | |
| 33 | ## Output |
| 34 | |
| 35 | 1-3 reply variants per comment, each in the Page's voice |
| 36 | A short note on which template each variant uses and why |
| 37 | An approval card. On approval, each reply is returned as a copy-paste block |
| 38 | with the target post URL. |
| 39 | |
| 40 | ## Reply templates (`references/reply-templates.md`) |
| 41 | |
| 42 | **C1 Answer-the-Question** - they asked, you answer plainly plus one real detail |
| 43 | **C2 Thank-Plus-Add-Value** - acknowledge, then add a useful extra (not a bare "thanks!") |
| 44 | **C3 Handle-the-Complaint** - acknowledge, own it, offer the next step, take it to DM if needed |
| 45 | **C4 Turn-It-Into-a-Share** - build on a positive comment so the thread itself becomes shareable |
| 46 | **C5 Invite-the-Spotlight** - when a commenter shares a win, invite them to be featured (feeds FB10) |
| 47 | |
| 48 | ## Steps |
| 49 | |
| 50 | **Voice profile first (all drafts).** If `../../references/voice-profile.md` has `filled: yes`, load it and match the user's voice fingerprint, hard rules, and CTA/link style throughout. If it is not filled, mention once that `fb-humanizer --mode profile` can learn their voice from a few posts, then proceed with the generic voice rules. |
| 51 | |
| 52 | **Parse the post URL** if given. `lib.url_parser.parse_facebook_url(url)` |
| 53 | returns `page`, `post_id`, `canonical_url` for the target link. |
| 54 | **Read the context.** Ask the user to paste the post and the comments. Group |
| 55 | the comments (questions, praise, complaints, wins). |
| 56 | **Pick a template per comment** using the table above. |
| 57 | **Draft 1-3 variants per comment.** Keep them short and human. Answer |
| 58 | questions plainly with one real detail. For complaints, acknowledge first, |
| 59 | never get defensive, offer a concrete next step. |
| 60 | **Humanizer pass.** Scrub 2026 AI vocab by density, cap em dashes (a |
| 61 | reply is short, so at most one, never swapped for a period), strip canned |
| 62 | "Thank you for your feedback!" corporate filler and sincerity openers |
| 63 | ("we'll be honest"). Leave the rhythm alone. Keep the Page voice. |
| 64 | Canonical rules: `fb-humanizer` V3. |
| 65 | **Approval card.** Show each comment, its drafted replies, the template used, |
| 66 | and the target post URL. |
| 67 | **On approval.** Call `lib.publish(kind="comment", draft_text=<approved>, |
| 68 | target_url=<canonical_url>)`. Because Publora has no Facebook comment |
| 69 | endpoint, this always returns a copy-paste block. Paste each reply under the |
| 70 | comment in Facebook or Meta Business Suite yourself. |
| 71 | |
| 72 | ## Hard rules |
| 73 | |
| 74 | Global voice rules: see root `SKILL.md` Voice rules. Additional skill-specific |
| 75 | rules: |
| 76 | |
| 77 | Reply fast and human. The first hour matters for reach; a fast, real reply |
| 78 | beats a slow, polished one. |
| 79 | Never paste a canned "Thank you for your feedback!". Acknowledge with content |
| 80 | or do not reply. |
| 81 | On a complaint: acknowledge first, never argue in public, offer a next step, |
| 82 | move details to DM. Comments are public and screenshot-able. |
| 83 | Do not hard-sell in a reply. Help first; mention the product only if it |
| 84 | genuinely answers the question. |
| 85 | Keep replies under a few short lines. A Page reply is not a press release. |
| 86 | |
| 87 | ## Example |
| 88 | |
| 89 | > User: "Reply to these comments on my post: |
| 90 | > https://www.facebook.com/MyBakery/posts/123. Comments: 'Are you open Sunday?' |
| 91 | > and 'Best sourdough in town!'" |
| 92 | > |
| 93 | > Skill: parses -> page MyBakery, post 123. Drafts a C1 Answer-the-Question reply |
| 94 | > to the first ("We are, 8 to 2 on Sundays. Come hungry.") and a C4 |
| 95 | > Turn-It-Into-a-Share reply to the second ("That means a lot. The Saturday batch |
| 96 | > is the one to beat, ask for it warm."). Shows the approval card. |
| 97 | > |
| 98 | > User: "post both" |
| 99 | > |
| 100 | > Skill: returns each reply as a copy-paste block with the post URL, since |
| 101 | > Publora has no Facebook comment endpoint. User pastes them in Facebook. |
| 102 | |
| 103 | ## Files |
| 104 | |
| 105 | `SKILL.md` - this file |
| 106 | `references/reply-templates.md` - 5 comment-reply templates with examples |
| 107 | |
| 108 | ## Related skills |
| 109 | |
| 110 | `fb-post-writer` - for a standalone Page post rather than a reply |
| 111 | `fb-humanizer` - scrub a reply before posting |
| 112 | `fb-content-planner` - sets the daily comment-reply target this skill executes |
| 113 |
Discussion
Alternatives
Also in Posting & schedulingLinkedin comment drafterDraft a LinkedIn comment on someone else's post from its URL, or reshare (repost) it to your feed with optional commentary. Use when the user pastes a post URL and asks to comment, engage, be first commenter, or repost with their thoughts. Produces 1-3 variants in the user's voice, picks a reaction, and publishes via Publora on approval. Not for replying to existing comments (use linkedin-reply-handler).Linkedin content plannerGenerate a 7-day LinkedIn content plan from a theme, audience, and pillars. Produces per-day post pillar, format, hook type, CTA, posting time, daily comment targets, and a weekly inbound-readiness check. Use when the user wants to plan a week or month of content, not draft a single post (use linkedin-post-writer).Linkedin employee advocacyStand up and run a LinkedIn employee advocacy program for a marketing or sales team. Covers 14-day launch playbook, brand-guideline governance, per-post time budget, cadence benchmarks, and team ROI (reach, engagement, pipeline). Triggers on "employee advocacy", "get the team posting", "scale LinkedIn across team", "advocacy ROI". Not for planning one person's own calendar (use linkedin-content-planner).Instagram Audience InsightsRead your Instagram niche and profile from real data via Apify, no login. Scan a hashtag for the posts traveling now (likes, comments, owner) to see the format and hook that works. Pull profile stats for any handle, yours or a competitor's: followers, posts, bio, category. Instagram hides who liked or commented on other accounts, so this is discovery plus profiles, not engagers. Triggers on "what works in my niche", "scan the hashtag", "competitor stats". Not for writing captions (use ig-caption-writer).