---
name: facebook-and-instagram-community-operations
description: Reads public comments and mentions across connected Facebook and Instagram assets, classifies each by intent, drafts replies from the client's knowledge base, and posts only the replies a named client approver signed off. Use when the user asks to check social comments, triage the community, draft replies, or respond to public social activity.
metadata:
  version: "1.1.1"
---

# facebook-and-instagram-community-operations

> **Client-neutral reusable package.** No client names, tenant or workspace identifiers, account or
> resource IDs, customer records, credentials, or internal paths. All examples are synthetic.

| | |
|---|---|
| Live catalog name | Facebook and Instagram Community Operations |
| Live category | Social & Publishing |
| Catalog entry | 13 |
| Internal capability ID | `CAP-EC-01/02` |
| Provider | Meta (Facebook, Instagram) |
| Availability | Candidate; validate in the active Workspace |
| Deliverable type | `limited_pilot_package` |
| Validation status | Candidate; local package validation only |
| Version | 1.1.0 |


## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant
bindings for the required inputs below; this public package supplies no client facts or authority.
Consume `ask-ollie-authority-core` for authority, `outloop-access-fallback` for recovery and
resource verification, `email-lifecycle-core` for recipients, approvals and stored-copy delivery
verification, and the bootstrapper Runtime Contract for ownership, scheduling and completion.
These owners govern execution; this Skill does not implement a competing runtime.

Select the relevant expertise below for the requested outcome. Runtime governs combining Skills,
partial use and completing missing steps with other authorized capabilities. This Skill's domain
scope does not limit the Operator's wider authorized task. Preserve domain safety restrictions.
Verify findings against source evidence and read back any resulting artifact or authorized change.

## Business outcome

No public comment goes unanswered, and the client approves a numbered list of ready replies instead of writing them.

## Operating modes

Read · Analyze · Draft · Publish with approval

## Required inputs

| Input | Source |
|---|---|
| Connected Page and Instagram assets | Workspace configuration |
| **Knowledge base of approved answers** | Required — this is the substance of the workflow |
| Language and tone | Configuration |
| Approval channel and named approver | Configuration |
| Escalation triggers | What must go to a human immediately |

## Scope boundary — state this to every client

This workflow covers **public comments and mentions only**.

It does **not** support Conversations, the private Inbox, or direct messages. That capability is
planned and does not exist. Never state, imply, or allow a client to believe otherwise.

## Approval parsing

Approval responses arrive as informal human text. Parse conservatively: anything ambiguous is treated
as **not approved**. A misparse that posts a skipped reply is the worst failure this workflow can
produce.

## Evidence and readback requirements

After posting, re-read each reply from the provider and confirm it is present and correctly threaded.

## Boundary — state this to every client, verbatim

> Runs as a scoped pilot, and covers public comment surfaces only. Meta scope approval is its own
> process per app. Private inbox access is a separate, planned capability — see Meta Community Inbox.

Never state, imply, or allow a client to believe that Conversations, the private Inbox, or direct
messages are supported. They are not.

## Action classification

| Action class | This workflow |
|---|---|
| Read | Public comments and replies on Page and Instagram media; mentions |
| Analyze | Intent classification, knowledge-base matching, escalation detection |
| Draft | A reply per item in the client's language and tone |
| Publish with approval | Posts approved replies; may hide spam where configured |
| Destructive | Comment deletion is available but **off by default** and requires an explicit gate |

## Approval and delivery

The Operator applies Authority Core and the active Workspace approval policy to any requested
mutation. Email Lifecycle owns recipient classification, sending and stored-copy verification.
The action table defines this capability's domain scope; it grants no permission by itself.

## Expected output

A numbered triage report with a drafted reply per item, then on approval a posting confirmation per item with its read-back state.

## Synthetic placeholders used in this package

These are illustrative only. Real values come from the client's own workspace configuration and are
never written back into this package.

| Placeholder | Meaning |
|---|---|
| `PAGE_ID_PLACEHOLDER` | Connected Page identifier |
| `IG_ACCOUNT_PLACEHOLDER` | Connected Instagram account |
| `APPROVER_PLACEHOLDER` | Named client approver |